Your real public IPv4 and IPv6 addresses, detected live from your own connection - plus your approximate location, ISP, ASN and timezone on a real map.
—
📍 Approximate location based on how your IP address's network block is registered - not GPS, and not a precise device or residential address.
Your IPv4 and IPv6 addresses are two separate addresses on two separate networks. They often belong to different network blocks - and sometimes to entirely different providers - so their registered location and ISP genuinely can differ. Neither one is "wrong".
| Field | IPv4 | IPv6 |
|---|
Your browser detects your address directly, while our server separately sees whatever address actually reaches it. Comparing the two is what reveals a proxy, CDN or corporate gateway sitting in between.
Jump straight into a deeper check - your detected IP address carries over automatically.
This page runs two different detections at once. First, your browser asks a public IP echo service directly over IPv4 and again over IPv6 - because those are two separate requests over two separate protocols, it can report both addresses independently, and an unreachable one is reported as genuinely unavailable rather than guessed. Second, our own .NET backend reports the address it actually observes your request arriving from. Those two answers are then compared: when they match, your connection is direct; when they differ, something (a VPN, corporate proxy, or CDN) sits in between - which the Connection & Privacy Analysis section states plainly instead of hiding. Each detected address is then looked up separately through the same geolocation provider used by IP Geolocation Lookup - so the IPv4 and IPv6 tabs show that protocol's own city, region, country, postal code, timezone, ISP, organization and ASN, each on its own OpenStreetMap map, rather than assuming one answer covers both. Any field the provider genuinely doesn't know is shown as "Not returned" rather than a guess.
These tools all work on the same connection and address data — pick whichever question you actually have.
Because your connection genuinely didn't complete an IPv6 request. Plenty of home, mobile and corporate networks are still IPv4-only, and some have IPv6 configured but not actually routable. Rather than guess, this page reports exactly what each protocol returned.
Because they're two genuinely separate addresses on two separate network blocks, and those blocks are registered independently - sometimes even to different companies. It's very common for one protocol to travel a different network path than the other (mobile tethering, dual-WAN routers, carrier-grade NAT, or an IPv6 tunnel will all do this). The "IPv4 vs IPv6 Side By Side" section highlights exactly which fields differ and explains the most likely reason. Neither address is wrong.
Whichever protocol your device and that site negotiate for the connection. If both support IPv6 it's usually preferred; otherwise IPv4 is used. That's why it's worth knowing both - a site's geolocation of you may match one tab and not the other.
IP geolocation reflects how your IP address's network block is registered, not GPS. It's commonly accurate at country level and often at city level, but ISPs, mobile carriers, satellite providers and VPNs frequently register addresses far from where you actually are.
It's the address the public internet sees you as - which is your real public-facing address unless you're behind a VPN, proxy or corporate gateway, in which case it's that service's address. This page tells you which of those situations applies rather than leaving you guessing.
It means the address your browser reported and the address our server observed don't match, so at least one intermediary is relaying your traffic. That's completely normal on corporate networks, VPNs and CDN-fronted sites - it isn't a security warning by itself.
No. The lookup happens live on each page load and is never written to a database - the same approach used by every other checker on this site.