Can I find someone's exact address from their IP?

No. The most precise thing a lookup gives you is the ISP routing location for the block, which is a region or a city and frequently the wrong one. The link between an address, a timestamp, and a subscriber exists only in the ISP records, and obtaining it takes a court order or a law enforcement request.

Why does the lookup show the wrong city for my own address?

Geolocation databases infer location from registry data, routing, latency measurements, and self-reported ranges. Any of those can be stale. Mobile carriers and CGNAT anchor many subscribers to one gateway, so the location shown is the gateway. See the guide on why sites think you are somewhere else.

What happens if I look up a private address like 192.168.1.1?

You get an explanation, not a lookup. RFC 1918 ranges, loopback, link-local, CGNAT space (100.64.0.0/10), and documentation ranges are not globally routable and have no owner to find. The page tells you what the range is for and links to the relevant guide.

Can I look up a whole CIDR block?

Yes. Enter it as a prefix, for example 203.0.113.0/24, and the result describes the block: the covering announcement, the ASN, the registry entry, and the size. Individual addresses within the block are not enumerated.

Are lookup results indexed by search engines?

Shareable result URLs are marked noindex. Only curated well-known addresses, such as public DNS resolvers, get indexable pages with written editorial. We do not generate a page per address.

IP Address Lookup

Look up any IPv4, IPv6, CIDR block or hostname: location, ISP, ASN, registry, reverse DNS and reputation.

Block arithmetic

Calculated locally

Block: 203.0.113.0/24
Family: IPv4
First address: 203.0.113.0
Last address: 203.0.113.255
Addresses: 256
Host bits: 8

The registry data below describes the network that covers the first address in the block. Open the subnet calculator for masks, wildcards and host counts.

documentation203.0.113.0

Documentation address. It exists so examples do not point at real hosts.

Documentation address. It exists so examples do not point at real hosts. TEST-NET-3. Reserved for documentation and examples. Defined in RFC 5737.

There is no registry entry, no operator and no geography to report, so we do not query anything for it. If you reached this address from your own network, the device answering is on your side of the router.

Identity

From the address itself

Address: 203.0.113.0
Family: IPv4
Classification: documentation (RFC 5737)
Reverse DNS: Not queried for a reserved address

Shareable result: /ip-lookup/203.0.113.0_24 noindex

What the result URL does

A completed lookup produces a shareable URL at /ip-lookup/{target}. Those pages are rendered on request and carry a noindex directive, so sharing one with a colleague works while search engines stay out of it. Well-known addresses with written editorial, such as 8.8.8.8, live at their own permanent URLs instead and are indexable.

Ranges that return an explanation

Range	RFC	What it is
10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16	RFC 1918	Private networks, not routable on the internet
100.64.0.0/10	RFC 6598	Shared address space for carrier-grade NAT
127.0.0.0/8	RFC 1122	Loopback, your own machine
169.254.0.0/16	RFC 3927	Link-local, assigned when DHCP fails
192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24	RFC 5737	Documentation examples, including the ones on this site
2001:db8::/32	RFC 3849	IPv6 documentation prefix
fe80::/10	RFC 4291	IPv6 link-local
fc00::/7	RFC 4193	IPv6 unique local addresses

Rate limits and acceptable use

Lookups are limited to 200 per day and 20 per minute per address, with a bot challenge after 50 in a day. This is a lookup tool, not a bulk enumeration service. If you need volume, use the API at /api/v1/lookup/{target} and read the limits on /api first.

About this tool

Enter an IPv4 address, an IPv6 address, a CIDR block, or a hostname. A hostname is resolved to its A and AAAA records first, and you pick which address to inspect. The result gives approximate location, ISP, ASN and AS type, RIR and allocation details, reverse DNS, and network classification. Privacy and reputation flags sit behind a separate button, and reserved ranges get an explanation instead of a lookup.

How to read the result

Approximate location: The city, region, and country a commercial database associates with the prefix, which reflects where the operator routes the block rather than a street address. Country accuracy is high, city accuracy is not guaranteed, and the coordinate is a region centroid.
ISP and organisation: The organisation that registry data associates with the address. For a consumer address that is the ISP, and for a hosting address it is the hosting company rather than their customer.
ASN and AS type: The autonomous system announcing the covering prefix, from BGP data, plus a classification of isp, hosting, business, education, or government. AS type is the most reliable single signal for telling a home connection from a datacenter one.
RIR and allocation: The Regional Internet Registry that allocated the block, the netname, the allocation date where it is published, and the covering prefix length. Registry region is not usage region, so a RIPE-allocated block can be routed anywhere.
Reverse DNS (PTR): The name the operator attached to this address, if they set one. A PTR is a claim by the operator rather than a verified fact, so use /reverse-dns for a forward-confirmed check.
Privacy and reputation flags: An optional check on whether the address belongs to a vpn, proxy, tor, hosting, or relay network. It sits behind a button because each query spends a metered credit, and the answers are probabilistic classifications made by an outside company, cached for 24 hours with a source and a timestamp.

Questions people ask

Can I find someone's exact address from their IP?: No. The most precise thing a lookup gives you is the ISP routing location for the block, which is a region or a city and frequently the wrong one. The link between an address, a timestamp, and a subscriber exists only in the ISP records, and obtaining it takes a court order or a law enforcement request.
Why does the lookup show the wrong city for my own address?: Geolocation databases infer location from registry data, routing, latency measurements, and self-reported ranges. Any of those can be stale. Mobile carriers and CGNAT anchor many subscribers to one gateway, so the location shown is the gateway. See the guide on why sites think you are somewhere else.
What happens if I look up a private address like 192.168.1.1?: You get an explanation, not a lookup. RFC 1918 ranges, loopback, link-local, CGNAT space (100.64.0.0/10), and documentation ranges are not globally routable and have no owner to find. The page tells you what the range is for and links to the relevant guide.
Can I look up a whole CIDR block?: Yes. Enter it as a prefix, for example 203.0.113.0/24, and the result describes the block: the covering announcement, the ASN, the registry entry, and the size. Individual addresses within the block are not enumerated.
Are lookup results indexed by search engines?: Shareable result URLs are marked noindex. Only curated well-known addresses, such as public DNS resolvers, get indexable pages with written editorial. We do not generate a page per address.

Last reviewed 2026-09-05.