How to find the IP real location? Multiple locations online ping websites for wrong GeoIP location
Sometimes you get an IP address and search for it's location via website, it will shows wrong information. this is because the database of GeoIP location is wrong or not update to the newest data.
eg. 184.82.47.1 GeoIP location shows it located on Pennsylvania, USA, but is it real?? Because I can confirm the server located on Los Angeles.
How to find the IP real location?
The best reliable way is ask your server/vps provider to confirm the real location. But your can also find out the real location by yourself.
Way #1: Use website multiple location online ping tools to find out which location's ping result is the smallest, this means the ip's real location is the nearest of that checkpoint/node.
Example:
Let's test ip 184.82.47.1, which we know the server was located on Los Angeles and GeoIP shows Pennsylvania
Multiple locations online ping result:
http://cloudmonitor.ca.com/en/ping.php?vtt=1386123084&varghost=184.82.47.1&vhost=_&vaction=ping&ping=start
Then we check the ping result and will find out the Los Angeles checkpoint has the smallest ping result, normally less than 20ms
So we are pretty sure that this ip's real location will be Los Angeles or nearby.
Some useful multiple locations online ping websites:
http://cloudmonitor.ca.com/en/ping.php
Way #2: Use traceroute command via ssh or via website online traceroute tool (eg. http://lg.he.net/ )
SSH traceroute command example:
[root @ comfortvps.com ~]# traceroute 184.82.47.1
traceroute to 184.82.47.1 (184.82.47.1), 30 hops max, 40 byte packets
1 63.223.127.1 (63.223.127.1) 0.783 ms 0.940 ms 1.199 ms
2 agg1-sea-g1-33.bb.spectrumnet.us (208.76.184.209) 6.031 ms 6.024 ms 6.117 ms
3 sesix.r1.se.hwng.net (206.81.80.194) 1.955 ms 2.809 ms 3.075 ms
4 unknown.hwng.net (209.197.0.253) 27.659 ms 27.986 ms 28.042 ms
5 209.197.4.114 (209.197.4.114) 31.494 ms 31.549 ms 31.654 ms
6 209.197.4.118 (209.197.4.118) 26.888 ms 26.775 ms 28.175 ms
7 ec0-64.1a0201.laca02.hostnoc.net (64.120.243.142) 30.887 ms * *
[root @ comfortvps.com ~]#
You can see the nearest traceroute record is ec0-64.1a0201.laca02.hostnoc.net (64.120.243.142) , in most of case, the name ec0-64.1a0201.laca02.hostnoc.net will shows the real location. the la in laca02, means Los Angeles.
Let's test another ip 184.22.152.3, which we know the server was located on Dallas and GeoIP shows Pennsylvania
[root @ comfortvps.com ~]# traceroute 184.22.152.3
traceroute to 184.22.152.3 (184.22.152.3), 30 hops max, 40 byte packets
1 63.223.127.1 (63.223.127.1) 3.395 ms 3.567 ms 3.811 ms
2 agg1-sea-g1-33.bb.spectrumnet.us (208.76.184.209) 1.318 ms 1.447 ms 1.534 ms
3 ae2-417.cr1.sea1.us.nlayer.net (63.141.219.69) 1.105 ms 1.126 ms 1.178 ms
4 xe-2-3-0.cr1.ord1.us.nlayer.net (69.22.142.149) 45.585 ms 45.643 ms 45.544 ms
5 ae0-60g.cr2.ord1.us.nlayer.net (69.31.111.154) 45.624 ms 45.692 ms 45.567 ms
6 * * *
7 xe-0-0-0.cr1.phl1.us.nlayer.net (69.22.142.163) 71.408 ms 71.409 ms 71.384 ms
8 198.47.110.30 (198.47.110.30) 75.090 ms 75.753 ms 75.383 ms
9 tn1-02.cor01.dupa01.hostnoc.net (96.9.191.2) 75.381 ms 75.462 ms 75.337 ms
10 tn1-03.gwy03.dupa01.hostnoc.net (96.9.191.9) 75.613 ms 75.404 ms 75.593 ms
11 vl3804.gwy01.datx01.hostnoc.net (64.120.184.106) 186.661 ms 186.431 ms 186.527 ms
12 ec0-10.1a0102.datx01.hostnoc.net (64.120.184.50) 93.927 ms 93.541 ms 94.063 ms
13 rev.dailyessay.info (184.22.152.3) 95.863 ms 95.805 ms 95.806 ms
[root @ comfortvps.com ~]#
You can see the nearest traceroute record is ec0-10.1a0102.datx01.hostnoc.net (64.120.184.50) , in most of case, the name ec0-10.1a0102.datx01.hostnoc.net will shows the real location. the da or tx in datx01, means Dallas,Texas.