What is IP Geolocation?

IP geolocation is the mapping of an IP address to the geographic location of the internet from the connected device. By geographically mapping the IP address, it provides you with location information such as the country, state, city, zip code, latitude/longitude, ISP, area code, and other information.

What is it for?

Various systems use geolocation databases for IPs, the reasons for this are various, but it is mainly used for deducting user's location, so that the system could give more personal offers (products, services, etc.). 

Examples

In this case we will deduct the geolocation for IP: 185.141.165.74.
The easiest way to do that is to use free online tools like iplocation.net (google ip geolocation tools).

Paste the IP in the IP Location Finder textbox and press IP Lookup button. In this case, the result you get is this:

In the picture above we can see that the tool found the IP record on three databases: IP2Location, ipinfo.io and DB-IP. The text in the brackets denotes where the information was taken from and when it was last updated (e.g. IP2location (Product: DB6, ...) means that the geolocation record for the IP was taken from DB6 database).

Wrong Geolocation

Sometimes you might see that geolocation data varies from database to database. One system might deduct that your IP is from Germany, other state that it is from France. How is it possible? 

There are many reasons why this might happen, yet it is basically due to the difference in database records.

Changing the records  

If you find your geolocation wrong and you would like to change it, you need to request for a correction for a record. The means of doing this varies depending on the database, for example, DB-IP handles the requests via support email, where you should state the IP (with the subnet) and the location information (City, State, Country, Postal Code). Other databases like MaxMind use data correction web forms so that all requests had the same standard and could be handled by API. 

So to change the records, you need to find the way the database handles the requests. 

You might be contacted by some person, who supervises the database system, asking you to provide traceroutes (to at least one IP of the subnet range). To do that using Windows OS, press Start, type cmd, hit Enter then type:
tracert your_ip
and type the IP you would like to trace instead of your_ip.
For our example IP: 185.141.165.74 the result looks like this: 

Take notice, that the traceroute will be different if it is done from other locations, that is due to the fact that the utility checks the connection from one PoP to the other, mapping the route. The first column denotes the number of the Hop, second, third and fourth denotes the latency between hops (checked three times) and the last one denotes the address of the Hop. Take notice that latency between some PoPs is marked  like * - that is because for security purposes (DDoS) some PoPs are configured not to handle ICMP requests. Find more information about tracert here.

So if you are asked for a traceroute, copy the result from cmd to a text document and send it to them, in most cases that is enough.

 

Still wrong?  

You have requested for data correction yet you still see the same results? Some databases refresh their records once in a month, others - once in a week. Depending on the database, it may have not updated your records yet. 

You can see that utilities see your IP correctly, but some site (system) still states that you are from wrong location?  Most probably a system like that uses the database which holds a wrong record. In this case, you would have to find out what database it is and then ask its support for correction. 

Did this answer your question?