- Public address
- Waiting for response…
- Network
- —
- Approximate location
- —
- Recent Tor exit use
- —
- Tor relay address
- —
Tools · Privacy
Check your public IPv4 and IPv6 addresses
A focused connection check for the addresses a website can see, the networks behind them, recent Tor exit evidence, and exact matches in the public Tor relay directory.
Visible to websites
Your public IP addresses
- Public address
- Waiting for response…
- Network
- —
- Approximate location
- —
- Recent Tor exit use
- —
- Tor relay address
- —
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.
- Onionoo snapshot
- Waiting for probe…
- Cache checked
- Waiting for probe…
Separate deyw.de endpoints test IPv4 and IPv6 independently.
Automatic network activity: this page sends one credential-free request to the A-only ipv4.deyw.de endpoint and one to the AAAA-only ipv6.deyw.de endpoint. There is no retry, periodic refresh, analytics request, or third-party endpoint.
Interpretation and privacy
How to read the result
Both address families are tested
The A-only and AAAA-only hostnames prevent the browser from silently falling back from one IP family to the other.
A VPN can expose different paths
Some VPNs carry both families; others cover IPv4 while IPv6 uses another route or is unavailable. The two cards make that visible.
Location is approximate
The city, country, ASN, and operator are database estimates—not GPS data—and may identify a provider location instead of your device.
Two different Tor signals
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.
No browser fingerprinting
This page does not read Canvas, WebGL, fonts, audio, device characteristics, storage, or precise location.
Logging boundary
The page and probe routes are excluded from HTTP access logs. The shared TLS router retains connection metadata for up to seven days but cannot see the requested URL or result content.