ip telemetry
Your public identity as the network sees it — the address, the network behind it, and whether you're anonymised right now. Measured live, nothing stored.
public address
·
copied·
All three run in your browser — nothing is sent anywhere by this page.
$audit --timezone
running…
$webrtc --stun-scan
running…
$ip --dual-stack
running…
The timezone audit compares your device clock to your IP's region; the WebRTC scan asks a public STUN server whether your real address peeks through the tunnel; the dual-stack probe asks ipify.org which address each protocol family exits from.
A DNS leak is when your device still asks your ISP's name servers to look up websites even while the rest of your traffic goes through a VPN — quietly handing your browsing history back to your ISP.
Want to know whether your DNS is actually being filtered by the node or leaking to your ISP? The full suite checks exactly that — plus a live WebRTC scan:
Open the DNS & WebRTC leak suite →on the network
On the full-tunnel VPN, every lookup should resolve through AdGuard Home on the exit node. The definitive check is the AdGuard Query Log — if your device appears there while browsing, DNS isn't leaking. External resolvers showing up there is the tell.
That's you, above. Run any other IP, domain or ASN through the same engine — try 1.1.1.1, itzgee.com or AS13335. Nothing is logged.
The plain-English version of what's on this page — read as much or as little as you like.
Your IP address is the return address for your internet traffic — the number websites reply to, the way a postal address is how a letter finds its way back.
The one shown above is your public IP: what the whole internet sees. It usually belongs to your internet provider and hints at your rough location, which is exactly what a VPN swaps out for you.
An ASN (Autonomous System Number) is an ID for a whole network on the internet — every ISP, cloud host and big company owns one, like an area code for a chunk of the map.
Yours reveals who runs the network your IP sits on. A home ISP's ASN looks residential; a data-centre or VPN ASN looks like hosting — which is how tools tell the two apart.
A VPN encrypts everything and routes it through one server elsewhere, replacing your IP. A proxy reroutes just one app, often without encryption.
Tor bounces your traffic through several volunteer relays so no single hop knows both who you are and where you're going — strong anonymity, slower speed.
WebRTC is the technology that lets browsers run voice calls, video and file transfers directly between devices, with no plugin. To connect two peers it has to discover their real network addresses — and a web page is allowed to ask for them.
So a script can sometimes read your true local or public IP even while a VPN is active. Modern browsers mask this behind mDNS .local names, but if a VPN is your privacy line it's worth blocking WebRTC outright.
An IP address is not a GPS pin. There's no satellite fix behind it — the "location" is simply wherever your ISP registered that block of addresses.
That's why it so often lands on a neighbouring city, the middle of the country, or a data-centre town rather than your street. Fine for "roughly which country", misleading for anything more precise.
Hiding your IP doesn't make you invisible. Sites can still single you out through browser fingerprinting — stitching your screen size, operating system, fonts, time zone and graphics quirks into a signature that's often unique, with no cookie required.
A VPN changes the address you arrive from. It does nothing about the fingerprint you bring with you.