Overview
See the IP address and network details that websites actually observe when you visit them: your public IPv4, an IPv6-or-fallback address, and geolocation context such as country, city, ISP, timezone, and approximate coordinates. Results load automatically and a Refresh button re-queries.
How It Works
The tool queries two public IP echo services and a geolocation API the moment the page opens. Three result groups appear: your IPv4 address, an IPv6-or-fallback address, and location details including country with flag, city and region, ISP, timezone, and latitude and longitude. Click Refresh to re-run all three lookups; a spinner shows while they are in flight. If the services cannot be reached, an inline error explains that the lookups failed.
Step-by-Step Usage Guide
- Open the tool; the lookups run automatically.
- Read the IPv4 and IPv6-or-fallback cards for the addresses websites see.
- Review the country, city, ISP, timezone, and coordinate cards for the geolocation view.
- Click Refresh to re-run the lookups, for example after toggling a VPN.
Technical Specifications & Standards
Three separate endpoints are involved. The IPv4 card calls api.ipify.org, which only answers over IPv4, so it shows your public v4 address. The second card calls api64.ipify.org, which prefers IPv6 when your connection has one and otherwise returns the v4 address, which is why the label mentions the fallback. Geolocation comes from ipwho.is, which resolves the address to country, region, city, timezone, coordinates, connection owner, and flag, and the tool checks its success flag before displaying anything. Unlike every other tool on this site, this one deliberately touches the network, because the entire point is to show what external servers see; the three services receive your IP address as part of any web request, and no other data is collected or sent. If you browse through a VPN or proxy, the displayed address and location belong to that exit node, not your physical connection. Mobile networks with carrier-grade NAT can make the city and region approximate.
Targeted Use Cases
- Checking whether a VPN or proxy is active by comparing the visible address with your expectation.
- Collecting your public IP to share with support or to whitelist in a firewall.
- Verifying that IPv6 is actually being used on your connection.
- Seeing which country and city geolocation places you in when testing localization behavior.
Notes & Gotchas
- Treat the location fields as approximate; geolocation databases are best-effort and often off by city or region.
- Refresh after changing networks or VPN settings to see the updated address.
- Compare the IPv4 card with the IPv6-or-fallback card to tell whether you have native v6 connectivity.
- Expect the coordinate values to be coarse; they come from an IP database, not your device.
Frequently Asked Questions
Why do the two address cards differ?
The first service only returns IPv4. The second prefers IPv6 and falls back to IPv4 when your connection has none, so a difference between the two cards usually means you are connecting over IPv6.
Does this tool leak personal data?
It reveals your public IP address to the two lookup services, which any website you visit already sees. Nothing else is collected, and the requests carry no identifiers beyond the lookup itself.
Why is my city wrong?
Geolocation comes from an IP database, which is often inaccurate at city level, and VPNs, corporate proxies, and carrier-grade NAT all shift the apparent location. Coordinates are approximate by nature.
What does the error message mean?
It appears when none of the lookup services could be reached, usually because the network is down, a firewall blocks the requests, or an extension interfered. Check connectivity and press Refresh.