Network
IP Geolocation
Get IP location information
Input
Terminal
Console ready. Execute a command to see output...
About IP Geolocation
Mapping the Digital to the Physical
IP Geolocation is not magic, it's data science. The tool queries massive databases that map IP blocks to ISPs and registered physical locations.
Precision Levels
- Country/Region: 99.8% Accurate. The country of an IP is almost always right.
- City: ~80% Accurate. Mobile IPs often show the location of the nearest cell tower or switching center, not the phone itself.
- Coordinates: These are usually the center of the city or zip code region, not the user's front door.
Context is King
Along with location, knowing the ASN (Autonomous System Number) tells you the type of actor.
- Residential ISP: Likely a human user.
- Datacenter/Cloud: Likely a VPN, Proxy, or Bot.
A VPN changes the IP but not the browser's timezone or language, and sites compare the three. That is why a VPN alone does not move your browser to another country.
Anycast (The Ghost in the Machine)
Sometimes, an IP address exists in 50 cities simultaneously. This is Anycast.
- Who uses it: Cloudflare, Google, AWS (CDNs and DNS).
- Why: To route you to the nearest server for speed.
- Impact: Geolocation tools might show you different location of the same IP, because it has no single home.
How to use IP Geolocation
- Enter an IPIPv4 (1.2.3.4) or IPv6. For a domain, run DNS Lookup first and bring the result here.
- Run the lookupHit Lookup. Country, region, city, coordinates, timezone, ISP, ASN, postal code and currency populate the terminal panel.
- Check the mapAn embedded map appears under the panel with a pin at the returned coordinates. Coordinates are approximate, usually the center of the city or the ISP's POP, not the actual user.
- Read the risk flagsIf the IP is flagged as datacenter, VPN, or Tor, treat it as a server or proxy rather than a residential user. For full anonymizer analysis on YOUR own current IP visit /whoami.
Frequently Asked Questions
- A local IP-to-geo database with weekly updates, plus a cached external lookup as fallback for addresses the local DB doesn't cover. Country accuracy is around 99%, city accuracy is around 70 to 80% (varies by region and ISP).
- Common, not a bug. ISPs and mobile carriers often register a whole block at a regional HQ, so a mobile IP can geolocate to the carrier's switching center rather than the user's actual city. Country and region (state/province) are reliable, city is approximate.
- Geo databases are rebuilt weekly. If the ISP reassigned the netblock, the city or country shifts in the next update. Anycast IPs (Cloudflare, Google DNS, Akamai) live in many cities at once, and the answer you get is wherever the DB last placed that prefix.
- The tool checks the IP against public lists of Tor exits and of VPN and datacenter ranges, and against the networks of hosting providers. A datacenter flag means the IP belongs to a cloud or hosting provider (AWS, DigitalOcean, OVH, etc.), so it's almost certainly a server, VPN exit, or bot, not a home connection. Tor exits and hosting networks are flagged for IPv4 and IPv6 alike. The VPN range list covers IPv4 only, so a VPN's IPv6 address shows up as datacenter rather than VPN. No flag is not proof of a clean address: the lists cover known services, not every server. For a full anonymizer analysis of your own connection see the Privacy & Trust Index on /whoami.
- IPs only (IPv4 or IPv6). To convert a domain to an IP first run DNS Lookup and bring the resolved address back here. A domain can map to several IPs across CDNs, so it's clearer to geolocate one IP at a time.
- Free, no signup, rate-limited. Private IPs (RFC 1918, localhost) are refused for security.