Networking · Network & IP
What an IP lookup actually tells you (and what it doesn't)
You paste an IP address into a tool and get back a country, region, city, ISP name, and an ASN. That feels precise, but the precision varies wildly by record type and where the IP sits. This post explains what each piece of data means, how accurate it is, and where it tends to be wrong.
TL;DR
Your public IP reveals a city, an ISP, and an ASN. It does not reveal your home address. Here is what is actually being shown when you run an IP lookup.
What the database actually knows
Every IP belongs to an organization. The five regional Internet registries — ARIN (North America), RIPE (Europe + Middle East + Central Asia), APNIC (Asia-Pacific), LACNIC (Latin America), AfriNIC (Africa) — publish WHOIS records that map each allocated block to its owner. That is the foundation. On top of it, commercial databases (MaxMind, IPinfo, IP2Location, DB-IP) layer BGP routing observations, latency triangulation, and user-reported corrections. The output you see is a best-guess aggregation of all of those, cached and refreshed on different schedules.
Country vs region vs city accuracy
Country-level accuracy is close to 100 percent — IP blocks map cleanly to countries. Region-level (state, province) is roughly 80–90 percent accurate. City-level is where it gets unreliable: 60–80 percent for residential IPs, far worse for mobile and VPN. The reason is allocation: large ISPs like Comcast, Deutsche Telekom, or Orange allocate IP blocks by region, not by city, and the database can only narrow to whatever block the ISP owns.
Three failure modes you will see in the wild
Carrier-Grade NAT (CGNAT) is the first — mobile carriers share a small pool of public IPs across thousands of subscribers, so the IP's registered city is the carrier's main office, not the actual subscriber's location. Anycast is the second — Cloudflare, AWS, and many large providers announce the same IP from dozens of cities worldwide, so the geolocation picks whichever city is geographically closest to the requesting server, not to the user. VPN endpoints are the third — the IP resolves to the VPN provider's data center, which can be a thousand kilometers from where the user actually sits.
Why the city is wrong sometimes
If the IP shows "Kansas City" and you are in Miami, the most likely explanation is one of the three above. Don't panic. The IP does not lie about the country — it does not know enough to lie about the city. If the country is wrong, that is worth investigating (the data may be stale, or your traffic is exiting through a foreign VPN server). And remember that the same IP can geolocate to different cities for different services, because each one uses a different database with different sources.
Try it →
Run the IP lookup tool on sitetrace.it.com — paste a value and get an instant answer.
Open IP lookup