GeoIP, or IP geolocation, is the method of estimating a user or device’s geographic location from its IP address alone. A lookup can reveal the country, region, city, latitude/longitude, ZIP/postal code, time zone, and currency associated with an address, along with network details such as the ISP, Autonomous System, and connection type. Every request that reaches your server already carries an IP address, so GeoIP works without asking the user for anything. There is no permission prompt, no JavaScript, and no GPS involved.
How GeoIP actually works
No central registry maps IP addresses to places. GeoIP providers assemble the mapping from several independent sources and reconcile them:
- Registry allocations. The five regional Internet registries (ARIN, RIPE NCC, APNIC, LACNIC, AFRINIC) record which organization holds each address block and in which country it was allocated. This anchors country-level accuracy but says nothing about where a block is actually deployed.
- BGP routing data. The Autonomous System announcing a prefix reveals the operating network. When an ISP from Lyon announces a block, that block most likely serves France, whatever its registration says.
- Operator geofeeds. Network operators increasingly publish RFC 8805 geofeeds, CSV files stating where each of their ranges is used. Self-published data resolves most disputes about relocated blocks.
- Active measurement. Latency from distributed probes bounds how far an address can physically be. Light in fiber travels about 100 km per millisecond, so a 5 ms round trip rules out another continent.
- Corrections. Users and operators report mislocated ranges, and good providers fold verified reports back into the data quickly.
Ipregistry refreshes its dataset daily from these sources. You can see the result for your own connection on the home page or look up any address directly, for example 8.8.8.8.
How accurate is it?
Accuracy depends on the level you ask for and the network you ask about. At the country level, expect about 99% accuracy for ordinary consumer and business traffic. Errors concentrate in address blocks that were transferred between regions or leased across borders.
City-level results are usable but not exact. For fixed-line broadband in well-covered countries you will usually get the right metropolitan area, with less precision in rural areas. Returned coordinates are the center of an area, never a street address.
Mobile networks are coarser. Carrier-grade NAT concentrates whole regions of subscribers behind a few gateway IPs, so a mobile IP often locates the gateway city rather than the user.
Finally, VPNs, proxies, and Tor produce intentionally wrong results, because the lookup sees the exit node instead of the user. This is why serious GeoIP providers pair location data with VPN and proxy detection. Knowing that a location is unreliable is nearly as valuable as the location itself.
What GeoIP is used for
The most common application remains content localization: serving the right currency, language, units, and time zone from the first request, before any user interaction. Fraud teams cross-check where a login or payment comes from against the account’s history and flag anonymized traffic. Compliance teams use it to enforce regional restrictions on content, gambling, or data processing, since regulators accept country-level IP checks as reasonable measures. Data teams turn raw server logs or CRM records into per-region insight with batch datasets instead of per-request lookups, and ad platforms weight traffic quality by origin network and connection type.
Adding GeoIP to an application
A REST call is the fastest way in:
curl "https://api.ipregistry.co/8.8.8.8?key=YOUR_API_KEY"The JSON response bundles location, network, company, carrier, currency, time zone, and threat signals in one payload. The full field list is in the documentation, with client libraries for the major languages. For offline scoring or air-gapped systems, the same data ships as downloadable CSV and MMDB datasets refreshed daily.
Test GeoIP with your own IP address here.
Frequently asked questions
How accurate is GeoIP?
Country-level GeoIP is about 99% accurate for typical consumer traffic. City-level accuracy is lower and varies by country and network type. Expect the right metropolitan area rather than an exact address. Mobile carrier networks and VPN or proxy traffic are the least precise.
Can GeoIP find someone's exact address?
No. GeoIP resolves an IP address to the area where its network operates, typically a city or region. The coordinates returned are the center of that area, not the location of the device, so it cannot identify a street address or a person.
What is the difference between GeoIP and GPS geolocation?
GPS reads a device's position from satellites and is accurate to a few meters, but it requires the user's permission and hardware access. GeoIP needs only the IP address of an incoming request, works server-side with no prompt, and is accurate to the city or region level.
Does a VPN change GeoIP results?
Yes. A VPN routes traffic through another server, so GeoIP sees the location of the VPN exit node instead of the user. Providers like Ipregistry flag VPN, proxy, and Tor addresses so applications can treat that traffic differently.
Keep users in the loop Ship release notes that get read. Try Noticeable