Providers used
- Provider details appear after a lookup.
Look up approximate country, city, timezone, ISP, organization, and ASN fields for any public IP address.
IP geolocation is network context, not exact location. VPN, proxy, CDN, hosting, and mobile carrier IPs may show provider infrastructure.
Lookup
Current IP: Loading...
Direct answer
IP geolocation estimates where an address is used from third-party databases; it is usually right about the country and often wrong about the city. This lookup asks the RIPEstat Data API first: its maxmind-geo-lite endpoint, which serves the MaxMind GeoLite2 database, for country, region and city, and its prefix-overview endpoint for the network that announces the address. Only if RIPEstat gives no usable answer does it fall back to ipapi.co, then ipwho.is, then ipwhois.app; time zone comes only from those fallbacks. The result locates a network, not a person.
Results
Checked at: Not checked yet
Combine IP, WebRTC, IPv6, DNS leak, fingerprint, user-agent, and related privacy signals in one report.
Related tools
Check my browser/privacy
Visible browser/session signals such as public route, DNS/WebRTC/IPv6 behavior, fingerprint traits, user-agent, or public IP context.
Limits
It cannot certify anonymity, inspect every app, or prove that a VPN, ISP, device, or account is safe.
Read results
Treat results as review signals for this browser/session or public target. Re-test after one change, then use Safe Copy or notes that avoid raw identifiers.
Checks approximate geolocation for a public IP address.
Country, region, city, timezone and network owner are read from third-party IP databases. Those databases record where a provider says a block is used, which is an approximation of a network, not a position of a person.
The country is usually right; the town is an estimate. In our own check, eight geolocation sources placed one Ukrainian address in three different towns, 34 to 273 km from where the connection really was; all of them agreed on the country. Accuracy is lower for mobile IPs (which are assigned by carrier network infrastructure rather than the user's location), VPN/proxy IPs (which show the server location), and ISPs that centralise their address blocks in one city. See our IP Geolocation Accuracy guide for details.
The most common reasons: 1) Your ISP routes all traffic through a regional hub in a different city. 2) You are on a mobile/cellular IP — these are assigned by the carrier's infrastructure, not your physical location. 3) Your IP block was registered in a different city years ago and the database has not updated. 4) You are using a VPN — it shows the VPN server's location. None of these are errors — they are inherent limits of IP-to-location mapping.
IP geolocation maps a network address to an approximate location using regional routing data — it is accurate to city level at best, and can be wrong by hundreds of kilometres. GPS uses satellite signals and is accurate to within a few metres. Websites that ask for your GPS location (via the browser Geolocation API) get your real location — but only if you grant permission. IP geolocation happens silently without any permission request.
Yes — enter any public IPv4 or IPv6 address to look up its approximate location, ISP, ASN, and connection type. You can look up your own IP to see what websites see, a VPN server's IP to verify its location, or any other public IP. Private IPs (192.168.x.x, 10.x.x.x, 172.16-31.x.x) cannot be geolocated — they are not routable on the public internet.