IP address

IP geolocation comparison

Compare the country, city, coordinates and network details that different databases assign to a public IP address.

Compare before and after

Run the same test on the same device and save a baseline. Activate your VPN or change one relevant setting, rerun under the same conditions and save the next result.

Save a before result and an after result to compare them.

What this test tells you

Use this comparison when an IP location seems unexpected or different services place you in different cities. The useful question is how the sources agree, not which map pin looks most convincing. Coordinates can mark an operator's point of presence or a regional centre rather than your device.

How to run the test

  1. Enter a public IP address, or use the address observed by the website when available.
  2. Run the comparison and check the status of each configured provider.
  3. Read country and city agreement separately, then inspect coordinates, distances and network details where supplied.

How the measurement works

The server sends the same validated address to several IP databases, normalises their responses and compares fields. It calculates distances only when usable coordinate pairs exist.

IP queries go to the configured external providers and may use a temporary cache. A source that supplies only country and ASN cannot contribute city-level evidence.

Understanding your results

Broad agreement
The comparable location fields align across available sources. This is agreement between databases, not confirmation of a person's whereabouts.
Partial or country-only agreement
Sources may agree on country but differ on city, or lack enough detail to compare further. Country agreement should not be read as overall agreement.
Disagreement or missing evidence
Different countries or large coordinate gaps warrant checking the individual records. Failed sources and absent coordinates remain unknown rather than matching automatically.

Compare before and after

  1. Save the IP, address family, provider names and location fields before changing anything.
  2. Change one connection route and rerun on the same device with the same sources.
  3. Compare the IP change with each provider's response. Allow for cached records and database updates when explaining differences.

Limits of the test

  • Provider estimates may be inaccurate for mobile gateways, corporate networks, VPN exits and reassigned addresses.
  • Several time zones listed for a country do not identify the time zone of this particular IP.

What to change, if needed

The IP is correct but one location record looks outdated
Check the provider's correction process; changing your device's location settings will not repair that database.
A location-sensitive service behaves unexpectedly
Compare its behaviour with the reported country and your actual route, then contact that service or use an appropriate authorised connection.

Frequently asked questions

Is the map showing GPS?

No. It plots coordinates supplied by an IP database, without asking your device for its position.

Why do databases disagree?

They use different evidence, update schedules and assumptions about where a network block operates.

Sources and technical references