Address lookup
Enter any IPv4 or IPv6 address and see what is known about it: country, city, reverse DNS record and the kind of range it belongs to.
1.1.1.1
Geolocation comes from a local database on our server — looking up an address sends nothing outside.
For any IPv4 or IPv6 address the lookup returns the country, the city and region where one is recorded, the reverse DNS record (the PTR name the address resolves back to), and the kind of range it falls into — public, private, loopback, link-local or reserved.
They are not equally trustworthy, and the tool does not pretend otherwise. The country is derived from registry allocations and is right the overwhelming majority of the time. The city is an estimate and is frequently the location of the operator's equipment rather than the user's; on mobile networks it can be a different region entirely. The reverse DNS record is often the most informative line on the page, because hosting providers name their machines systematically — a PTR containing dyn or pppoe says residential, one naming a datacentre says server.
It is a server-rendered page with a plain GET form, which has a consequence worth knowing: the result lives at its own address (?ip=8.8.8.8), so it can be linked, bookmarked and shared, and the page works with JavaScript disabled. Geolocation comes from a database on our own server. That database has no ASN or organisation data, and the tool says so rather than inventing a plausible-looking owner.
Checking where a proxy's exit address actually is, rather than where it was sold as being.
Investigating an address from a server log or a suspicious login notification.
Telling a residential connection from a datacentre one by its reverse DNS name.
Verifying that a crawler claiming to be Googlebot has a reverse record that supports the claim.
To look up your own address instead, use what is my IP; to check whether an address is on a mail blocklist, use the blacklist check.
Country-level accuracy is high — well above 95% for ordinary addresses. City-level accuracy is much weaker, because the data maps allocations and routing to places, not devices. Mobile and satellite connections are the least reliable of all.
No. The link between an address and a subscriber is held by the operator and released only to a lawful request. Public lookups see the operator and an approximate region, nothing more.
A PTR record mapping an address back to a hostname. It is set by whoever controls the address block, so it often reveals the hosting provider or the type of connection — and its absence is normal for many residential addresses.
Because the local geolocation database we use does not contain that data, and filling the field with a guess would be worse than leaving it out. The reverse DNS record usually answers the same question in practice.
Yes. The address is part of the URL, so the result page can be copied, bookmarked or sent to someone else and it will show the same lookup.
That the address is not routable on the public internet: private ranges live inside local networks, loopback means the machine itself, and reserved ranges are set aside by standards. Such an address cannot be geolocated because it exists in many networks at once.