IP check
The address below is what this site's own server saw when your browser asked it. It is the same address any website reads to know where a request came from.
First-party only. We read the address from the request headers you already send and hand it straight back. No third-party geolocation lookup, and we keep no record of it.
Your public address, as this server saw it
reading…
What this address is, and what a VPN does to it
Every connection to a website carries a source address so the reply knows where to go. Without a VPN that address is the one your internet provider assigned you, tied to your account, and a rough pointer to your location. It is the value shown above.
A VPN changes it by relaying your traffic through its own server first. The website then sees the server's address instead of yours: run this check on the VPN and the number should be the provider's, in the country you chose, not the one your ISP gave you. If it still shows your real address, traffic is reaching us outside the tunnel.
This only tells you the address in the request path. A browser can leak a different address underneath it, which is exactly what the WebRTC leak test checks.
Related checks
- WebRTC leak test , whether the browser hands out an address behind the tunnel.
- DNS leak , what a DNS leak is, and why the resolver test isn't built yet.