When running a traceroute to the IP address, we get the following result: $ traceroute 45.142.38.20
Address ip locator windows#
Within Windows there is the tool tracert, and for Linux and macOS the tool traceroute can be run. By investigating the traffic, and paying attention to the IP addresses it passes, we can map out a route and even plot it on a map. This is a technique where several data packets are being sent towards a target, while mapping the route this internet traffic takes. Tracerouteīesides using a IP2Geo service, there’s a different way of finding a possible location of an IP address, by running a traceroute. And it’s possible those three locations are all mentioned in a Whois answer, thus making it very difficult to scrape and parse automatically. And it’s even possible that an American company is the owner of a set of IP addresses, a UK company currently uses some, but they have their network operations center in Germany. They have old data, they process the results incorrectly, or they do not take into consideration that the IP address is of a company that has a physical presence in multiple countries.
There are several reasons for this, but they usually go back to how the IP2Geo provider uses the data that they fetched from the Whois information. After querying them manually the following result came back: Country: UNITED STATES (US)Īs you can see, there are a lot of different answers on where this IP address should actually be.
In this post we’ll talk about IP addresses, what dangers there are when trying to tie them to a location, and what are proper ways to determine a geographic area.
The topic of finding the location of an IP address has been addressed multiple times in blog posts, Twitter threads and even in one of our webcasts.