Collecting the one-time results…
The summary will appear after the IPv4, IPv6, browser, permission, and fingerprintability checks finish.
Tools · Privacy
This page shows the network metadata received by deyw.de and the signals readable locally through standard browser APIs. It does not create a combined fingerprint, assign an identifier, or save the report.
Plain-language interpretation
This summary is generated locally from the results below using fixed rules.
The summary will appear after the IPv4, IPv6, browser, permission, and fingerprintability checks finish.
Not tested — browser permission is required. Use the separate check below when you want to reveal it.
These signals do not reveal your name, identity, nationality, exact home address, or exact computer model by themselves.
Visible to this server
Automatic dual-stack check
This page automatically tests IPv4 and IPv6 connectivity using separate deyw.de endpoints. Results are combined only in your browser and are not stored. Each hostname has only one DNS address family; a failed test means the family is unavailable, blocked, or did not respond within five seconds.
Onionoo publishes actively observed recent exit-use addresses only for IPv4. For both IP families, this tool also checks whether the exact address is published as a relay onion-routing address. A relay-address match does not prove that this request used Tor, and no IPv6 match does not rule Tor out.
These requests carry no cookies or credentials. Because they arrive close together from the same page, the server could theoretically correlate their timing; the application does not assign an identifier, join the requests, or save either result.
Visible in the page request
These values arrived with the initial request. The page shows them back to you, but does not store them in an application database.
Readable locally without prompting
JavaScript reads these values after the page loads. They remain in this tab and are never submitted to deyw.de.
Automatic local test
A browser fingerprint combines many small differences. This demo automatically inspects eleven potentially identifying surfaces: Canvas, WebGL renderer and capabilities, Audio, bounded font matches, detailed Client Hints, media codecs, speech voices, internationalization settings, storage quota class, and WebGPU capabilities.
Optional clipboard access
Websites cannot normally read your clipboard silently. If you press the button and your browser allows it, this page can inspect the available clipboard formats locally.
Optional browser permission
If you choose to continue, your browser will ask for permission. The coordinates are rendered only in this tab and are not transmitted to deyw.de. Your browser or operating system may contact its own location provider to calculate them.
Opening the map sends these coordinates directly to Google. deyw.de does not receive or store this action, and the link opens without a referrer.
The initial request and two one-time deyw.de probes show the connection paths your browser can use.
Automatic network activity: after loading the page and its same-origin assets, the browser sends one credential-free HTTPS request to each of ipv4.deyw.de and ipv6.deyw.de. There is no retry, refresh tick, analytics request, or third-party endpoint.
Interpretation and privacy
The initial page shows the route your browser preferred. The one-time IPv4-only and IPv6-only probes then test whether each separate path is usable.
City, country, and ASN come from a local database. VPNs, mobile networks, carrier NAT, and database errors can move the estimate far from your real position.
Recent exit-use evidence is an active IPv4 observation. A Tor relay-address match means the address is published for onion routing; it does not prove this browser request exited through Tor.
Use a privacy-focused browser, resist installing uncommon fonts and extensions, review site permissions, and use Tor Browser when you need stronger anti-fingerprinting and network separation.
The automatic local demo reports individual surfaces only. It never joins them into a stable identifier, compares them with other visitors, or writes them to browser storage.
The page and probe routes are excluded from HTTP access logs. The shared TLS router still retains connection metadata—source IP, time, byte counts, and duration—for up to seven days; it cannot see the requested URL or report content.