Website IP checker:
who owns the number?
Enter a domain and we resolve both address families (A + AAAA), walk reverse DNS there and back, and name the network owner from the routing registries. The map dot is the only guess on the page, and it is labeled as one. Checking your own connection instead? What is my IP →
Right answer, wrong conclusion
The lookup itself rarely fails. The conclusions drawn from it fail constantly, and these four are avoidable once the answer arrives with its labels on.
The dot on the map
IP geolocation places the ISP’s registration, not a street. Country: dependable. City: a guess. Address: never — that myth belongs to television.
city-level, at bestThe doorman’s address
Behind a CDN, the IP belongs to the proxy network. You’ve located Cloudflare — the origin server is deliberately unlisted. The lookup worked; the conclusion would be wrong.
proxy ≠ originThe missing half
No AAAA record in 2026 means IPv6-only users reach you through carrier translators. Those networks are common on mobile, and your v6 blind spot never shows up in your own tests.
AAAA: noneThe silent swap
An A record changes with zero fanfare. Sometimes it’s your migration. Sometimes it isn’t. Either way, nothing emails you — resolvers just start handing out the new number.
hijacks look like editsSix shapes the answer can take
Same question, very different stories — what each pattern in an IP lookup actually means.
Dual-stack: one name answering on both address families. The modern default — v6-only paths reach you natively, no translators involved.
The reverse name resolves back to the same IP: forward-confirmed reverse DNS. Anyone can point a PTR anywhere; only the zone owner can make both directions agree.
Five-minute TTL plus a CDN’s autonomous system: the address is the network’s, not the site’s — and built to rotate. Pinning it in a firewall rule is a scheduled outage.
A PTR named by the hosting company’s VM inventory. Fine for a website; a red flag the moment this box sends mail — receivers read it as “nobody claimed this machine”.
IPv4-only in 2026: reachable everywhere today, invisible to the v6-only paths of tomorrow — and to IPv6 monitoring right now, because there’s nothing to monitor.
A private range. If a lookup handed you this, you asked your own router. RFC 1918 addresses never route on the public internet — every office in the world has this one.
One IP lookup, four registries
“The IP of a website” sounds like one fact. It’s four, from four different sources with four different reliability grades — and we show each with its grade attached.
- A + AAAA from the domain’s DNS zone — the site’s own claim about where it lives, in both address families.
- PTR from the reverse zones — the address block owner’s counter-claim about the same machine. We walk it both directions; a PTR that doesn’t forward-confirm is a decoration.
- ASN + prefix from the routing registries — who actually announces this address space to the internet. Hetzner, Cloudflare, your ISP: the fact that doesn’t lie.
- City from a geolocation database — the only guess of the four, and the page says so right next to it.
What an IP can and can’t prove
the no-overclaim tableWhat you can check yourself
Each lookup is one command away. Cross-checking them, and labeling which answer is a guess, is the part worth automating.
Common website IP questions
Type the domain above. We resolve its A record (IPv4) and AAAA record (IPv6), then fetch the reverse-DNS name for each address and confirm it resolves back. We identify the autonomous system that announces the address block, which names the actual hosting provider. Then we add a city-level geolocation, labeled as the estimate it is. Free, no signup.
All four common reasons are benign. Round-robin DNS returns a rotating list. Geo-DNS answers with a server near the asker, so Vilnius and São Paulo legitimately get different numbers. CDNs do both at once. And short TTLs mean the answer is allowed to change every few minutes. A different answer isn’t evidence of a problem — a changed answer on a record you own and didn’t touch is, which is exactly what DNS monitoring watches for.
Because the site sits behind a reverse proxy. The DNS answer points at the CDN’s edge. Traffic terminates there and is forwarded privately to the origin, whose address is kept out of DNS on purpose. This is the product working as intended — DDoS protection depends on the origin being unreachable directly. Three things are still readable: which provider fronts the site, whether the edge is dual-stack, and (from the ASN) that any “server location” a map shows you is the network’s registration, not the site’s.
Think of three tiers. Country: reliable — it follows the address block’s registration, which is public record. City: a hint — databases map address blocks to the ISP’s registration city, which may be where the users are, or the regional hub 100 km away. Street: not a thing — no public database has it, full stop. Mobile carriers and CGNAT make city-level worse; corporate VPNs can teleport an office to another country entirely. We show the city because it’s useful; we label it a guess because it is one.
Home connections lease addresses rather than own them: DHCP renewals, router reboots and ISP pool rotation all mint a new one. Mobile networks go further with carrier-grade NAT, where thousands of subscribers share one public address that shifts as you move. None of it is a malfunction. Need an address that holds still, for a firewall allowlist, say? That’s a static IP, purchased from your ISP; no website setting can grant it. Check what you have right now on What is my IP.
Today: mostly invisible, which is the trap. IPv6-only networks, common on mobile, reach IPv4-only sites through the carrier’s NAT64 translators, so nothing looks broken. But you’re one middlebox further from those users, you can’t see that path failing, and no IPv6 monitoring can exist for a site with no AAAA. Publishing one is usually a hosting-panel checkbox plus a DNS record. Worth doing on a calm Tuesday rather than during whatever incident finally makes it urgent.
From public data: no. A stranger with your IP gets your ISP’s name and a city-level estimate — the same things this tool shows. Mapping an address to a household requires the ISP’s subscriber logs, which are released through legal process, not lookups. The realistic privacy notes are smaller: your IP does reveal your ISP and rough region, it links your activity across sites that log it, and on CGNAT you share it with strangers whose behavior can get it blocklisted. A VPN swaps all of that for the exit node’s identity — which is the entire product.
Free tools are just the start.
Uptimia keeps your sites healthy.
Uptime, SSL, domain expiry, page speed, transactions — monitored from 171+ locations worldwide. Free for 30 days.