IP Geolocation Lookup
Look up an IP's country, city, ISP and ASN.
IP Geolocation Lookup shows the approximate registered location and network details for an IPv4 or IPv6 address. Alongside country, city and region it reveals the ISP, organization, and ASN that operate the IP, plus its timezone and coordinates. It's handy for figuring out where an unfamiliar IP in your access logs comes from and which carrier or cloud it belongs to.
Lookups match the IP against registration databases, so results are always an estimate. They do not pinpoint a person's physical location and are especially imprecise for VPNs, proxies and mobile networks. Enter an IP address, not a domain. If you only have a domain, find its IP with the Website IP Lookup first, then paste that IP here.
How to read the results
- Country / City / Region: the IP's approximate registered location; city level can be off.
- ISP: the internet service provider (carrier, hosting company, etc.) that assigned the IP.
- Organization: the entity or company that holds the IP block.
- ASN: Autonomous System Number (starts with AS), identifying the network operator.
- Timezone / Coordinates: time zone and lat/long of the registered location (rough, for map search).
Why the location can be wrong
IP geolocation is inferred from registration and routing data, not GPS. Carriers often assign IPs across wide regions, so the result can be hundreds of kilometers off, and cloud/CDN IPs point to a data center. A VPN shows the VPN server's location, and mobile networks may report a carrier gateway rather than the cell tower.
Good uses
Identifying the carrier behind an IP in logs or mail headers, getting a rough country for a suspicious connection, or checking which cloud/region a server lives in. For the exact ASN and advertised prefix, pair it with IP ASN Lookup. Don't rely on it for legal identification or precise tracking.
Accuracy by IP type
The same lookup gives wildly different trust levels depending on what kind of IP you feed it. City-level accuracy is the exception, not the rule — for most IPs, stop at the country.
| IP type | Trustworthy granularity | Caveat |
|---|---|---|
| Residential broadband (ISP) | Country / metro (usually good) | City can drift to the ISP's regional office |
| Mobile (LTE/5G) | Country only (city ~useless) | Shows the CGNAT gateway, often a single hub city |
Cloud/hosting (AWS, GCP) | Data-center region | Server location, not a user; a bot/scraper signal |
CDN (Cloudflare, etc.) | Edge PoP location | Anycast: the same IP lives in many cities at once |
| VPN/proxy | Exit-server location (not the user) | The real user's country is unknowable |
Reading a real lookup
Enter 8.8.8.8 (Google Public DNS) and you'll see roughly the result below. The trick is to read ORG/ASN first and city last.
| Field | Value | Interpretation |
|---|---|---|
| Country / City | United States / Mountain View | Registered to Google HQ; the actual responder is anycast worldwide |
| Org / ISP | Google LLC | Not a consumer carrier → unlikely to be an ordinary user |
| ASN | AS15169 | Google's Autonomous System — far more reliable than the city |
So don't read "Mountain View" as a user's city; reading AS15169 / Google LLCas "a Google infrastructure IP" is the correct takeaway.
Common pitfall
- Treating the city or lat/long as a precise user location. Coordinates are usually a default centroid for the country or region, so many different IPs land on the exact same point (often the geographic middle of the country).
- Seeing a data-center/CDN city and concluding "someone broke in from abroad" — it may just be traffic routed through a cloud. Trust the ORG and ASN over the country.
Frequently asked questions
Can I enter a domain?
The location doesn't match reality.
Can it look up my own IP?
Is the IP I enter sent anywhere?
Does it support IPv6?
Related guides
- Public vs Private IP: The Difference and How to CheckWhat separates public and private IPs, how NAT and port forwarding relate, and how to check yours.