GeoIP City Labels Are Hints Not Proof

GeoIP City Labels Are Hints Not Proof

World map with location pins on a travel desk

TL;DR: City-level GeoIP is an educated guess built from registries and routing data—not a GPS fix. Use it for coarse fraud signals and content localization, not for accusing a user of lying about their suburb. Pair any map pin with ASN context from a careful IP inquiry.

How city labels get invented

GeoIP databases map address blocks to locations using RIR records, ISP self-reporting, latency research, and user-submitted corrections. Mobile carriers and large NATs often collapse thousands of subscribers into one city centroid—sometimes the ISP headquarters, not the handset.

When a lookup says “Dallas” and the customer says “Fort Worth,” both can be acting in good faith. The database rounded to a metro hub.

Accuracy tiers you should expect

  • Country: usually reliable enough for licensing geo-gates.
  • Region / state: decent for many fixed-line ISPs; weaker on mobile.
  • City: directional; treat as a metro hint.
  • Postcode / coordinates: marketing precision, not forensic proof.

VPN and proxy exits intentionally break the chain: the city is where the egress lives, not where the human sits.

Hosting ASNs versus residential ASNs

If the ASN belongs to a cloud provider, the city is a data-center market. That is useful for bot scoring and terrible for shipping-address verification. Always read ASN/org beside the city string.

Product decisions that overfit GeoIP

Hard-blocking checkout because city ≠ billing city generates false declines, especially for travelers and remote workers on cellular. Softer patterns work better: step-up authentication when country flips, velocity rules when ASN type changes from residential to hosting, manual review queues for high-value orders.

Content licensing should prefer country fields. Showing a “wrong” regional homepage based on a city miss is an avoidable support ticket.

How to read a lookup during an incident

When fraud or account-takeover review lands on your desk:

  • Capture the IP and timestamp from the event log.
  • Look up country, region, city, and ASN together.
  • Compare with the user’s historical IPs—not with a single pin on a map.
  • Ask whether a corporate proxy or VPN is expected for that account.

A sudden jump from a residential ASN in one country to a hosting ASN in another is a stronger story than “city changed within the same metro.”

Communicating uncertainty to non-technical stakeholders

Replace “the user was in City X” with “the egress IP geolocates to the City X area in vendor DB Y as of date Z.” That wording keeps legal and trust-and-safety teams from over-claiming. Refresh databases periodically; stale city data causes embarrassing mismatches after ISP renumbering.

Using inquiry tools without false confidence

IP pages that show a map are engaging; they are still secondary sources. Cross-check two databases if a decision is irreversible. Keep screenshots with the IP visible so later auditors know which address was mapped.

For everyday checks, www.myipinquire.com is a fast way to see how the world currently labels your egress—useful for verifying a VPN region claim or a CDN PoP surprise. Believe the country more than the street-level pin.

GeoIP is a flashlight, not a witness statement. Aim it wisely, and write conclusions that match the light you actually have.

Similar Posts