See the public IP address you are connecting from, and look up any address you are curious about. Location, network operator, reverse DNS and the technical breakdown on one screen. Nothing you type is stored.
Location and operator data is provided by ipinfo.io; registry records come from the RDAP service of the regional internet registries.
The public address you are connecting from appears at the top the moment the page opens. You do not have to look anything up.
Paste an IPv4 or IPv6 address into the box. Not a domain name — the address itself, like 8.8.8.8 or 2001:4860:4860::8888.
Country, city, time zone and the organisation operating the address are listed. The estimate is reliable at country level and approximate at city level.
Address class, decimal and binary forms, the reverse DNS record and the block it is registered in all sit on the same page, from one lookup.
An IP address is the number every device on the internet carries so it can be found on the network. A letter needs an address to arrive; so does a packet of data. Two versions are in use: 32-bit IPv4 (like 8.8.8.8) and 128-bit IPv6 (like 2001:4860:4860::8888), designed to solve the shortage of the first.
The address your own devices see (something like 192.168.1.20) is not the address the internet sees you at. Your router gathers every device in the house behind a single public address, and that public one is what this page shows at the top. It is the number a website sees when you visit it.
The honest answer: nearly always right at country level, approximate at city level. IP addresses carry no geographic coordinates. The estimate is built from which operator a block was allocated to and where that operator uses it.
So on a mobile connection the city you see may be where the operator's exit point sits, and it is perfectly ordinary for that to be hundreds of kilometres from where you are. On a corporate connection you tend to see the head office. On a VPN you see the VPN server, which is the whole point of one.
The coordinates shown point at the rough centre of the estimated area, not at a building. No IP lookup tool can give you someone's home address, and any tool claiming otherwise is not worth trusting.
Not every IP address is routed on the internet. Some blocks are set aside for private networks, others for technical purposes. This tool tells you which class an address falls into, and for the reserved blocks it asks no outside source at all.
| Block | Class | Where you meet it |
|---|---|---|
| 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 |
Private network | Home and office networks. The addresses your router hands out come from these blocks. |
| 100.64.0.0/10 | Carrier-grade NAT | The pool an operator uses to gather subscribers behind one public address. Common on mobile connections. |
| 127.0.0.0/8 | Loopback | The device itself. This is where localhost takes you. |
| 169.254.0.0/16 | Link-local | What a device assigns itself when it cannot get an address from the router. Usually a sign something is wrong. |
| 192.0.2.0/24 2001:db8::/32 |
Documentation | Set aside for use in documentation and examples. It belongs to no real device. |
| fc00::/7 | Unique local | The IPv6 counterpart of private networks. |
The public address you are connecting from appears at the top as soon as the page opens. One click copies it, one click looks it up.
Both versions are supported. IPv6 addresses are shown both compressed and fully expanded.
Address class, decimal and binary forms, the reverse pointer record — the details anyone working on the network side actually needs.
Who the block belongs to, when it was allocated and where to report abuse — straight from the regional registry.
The address you look up is not tied to an account or written to a database. Private network addresses are never sent to any outside source.
This tool never connects to the address: no port scan, no ping, no traceroute. It only asks registries and databases about it.
The public address you are connecting from appears at the top of this page the moment you open it; you do not have to do anything else. Your internet provider assigns it to your router, and it is the number websites see you at.
Most home connections use a dynamic address: every time your router restarts, or the provider's lease expires, you get a new one from the pool. If you need a fixed address you have to ask your provider for a static IP, which usually costs extra.
No. An IP address belongs to a connection, not to a person. Only the internet provider knows who was using it, and they disclose that only on a lawful request. An IP lookup produces no name, no phone number and no home address.
Nearly always right at country level, approximate at city level. The estimate comes from which operator an address block was allocated to. On mobile connections you may see the city of the operator's exit point, which can be hundreds of kilometres from where you are.
It shows the VPN server's address and location, not yours — which is exactly what a VPN is for. You can test whether yours is actually working by opening this page with the VPN on and again with it off, and comparing the two.
IPv4 is a 32-bit address written like 8.8.8.8. The supply ran out, which is why IPv6 was designed: 128 bits, written like 2001:4860:4860::8888, with more addresses than will ever be needed. The two run side by side today, and this tool looks up both.
The blocks 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 are set aside for local networks and are not routed on the internet. They are the addresses your own devices use to reach each other. Look one up here and the tool shows only the offline breakdown — it sends the address to no outside source.
It tells you which domain name an IP address points back to — the opposite of ordinary DNS. It matters most for mail servers: receiving servers expect the sending address to have a valid PTR record, and mail from servers without one often lands in spam.
No. A lookup is not tied to an account and is not written to a database. Location comes from a public provider and registry data from the regional internet registry; those answers are cached for a day and are never associated with whoever asked.
No. There is no port scan, no ping and no traceroute; the tool never contacts the address itself. It only asks registries and public databases about it.
