Domain to IP — Find the IP Address of Any Website
Every IPv4 and IPv6 address of a domain with TTL, reverse DNS, ASN, owner, country and CDN detection for each IP.
How to find the IP address of a website
The tool queries the domain's A and AAAA records and lists every IPv4 and IPv6 address, not just the first one. For each IP you get the TTL, reverse DNS (PTR), the autonomous system number and its owner, the country and a CDN/proxy flag: if the site is behind Cloudflare, you see the proxy address, not the server.
How to Use
- Enter a domain or page URL — the tool strips the path and https:// itself
- Review every IPv4 and IPv6 address and its TTL
- Check the CDN column: behind a proxy you see an edge node, not the server
FAQ
How to find the IP address of a website — and what the result means
Before a browser can load a site, it asks DNS which IP address sits behind the domain. The answer lives in two record types: A for IPv4 and AAAA for IPv6. This domain to IP lookup runs the same query and lists every record, not just the single address you get from ping.
For each address the table shows:
- TTL — how many seconds resolvers cache the record. It counts down between queries, so two checks rarely show the same number.
- Reverse DNS (PTR) — the name the network owner assigned to the IP. It often reveals the host:
*.your-server.deis Hetzner,*.1e100.netis Google,*.cloudfront.netis Amazon CloudFront. - ASN and owner — the autonomous system that announces the address on the internet and the organisation it is registered to.
- Country — from a geolocation database. For CDN addresses the city is approximate: one anycast IP answers from dozens of data centres.
- CDN / proxy — a flag that you are looking at a delivery or protection network, not at the site's own server.
Why one website has several IP addresses
Getting more than one address back is normal, not a misconfiguration. There are usually four reasons:
- Load balancing. Several A records point to different servers and the browser picks any of them (DNS round robin). If one server is down, the client tries the next address.
- CDN. Cloudflare, Fastly, Akamai and others return two to four addresses from their network, all routed to the edge node nearest the visitor.
- IPv4 plus IPv6. A site that supports IPv6 has both A and AAAA records, and IPv6-capable devices usually prefer the latter.
- GeoDNS. Large sites answer different regions with different addresses. A lookup from Europe and one from the US can return different IPs, and both are correct.
Sites behind Cloudflare or a CDN: why you don't see the real server
When a domain is proxied through Cloudflare, DNS returns Cloudflare addresses (ranges 104.16.0.0/13, 172.64.0.0/13, 2606:4700::/32, ASN 13335). Visitors connect to a Cloudflare edge, and Cloudflare fetches the page from the origin server. The origin IP is hidden on purpose — it keeps the server out of reach of DDoS traffic and of attacks that would bypass the proxy's filters.
| What the report shows | What it means |
|---|---|
| AS13335, Cloudflare | Reverse proxy. The origin server cannot be found through DNS. |
| AS54113, Fastly | Fastly CDN; 151.101.x.x addresses are shared by thousands of sites. |
Akamai, PTR *.akamaitechnologies.com | Akamai CDN, often reached through a CNAME to edgekey.net. |
| Organisation “AWS CloudFront” | Amazon's CDN. ASN 16509 alone does not mean a CDN — it covers all of AWS. |
| Vercel, Netlify, GitHub Pages | A hosting platform; the address belongs to its shared network. |
| No CDN detected | Most likely the server itself or the host's load balancer. |
If the site is yours, you don't need DNS to find the origin IP. It is listed in your hosting control panel (under “Servers”, “VPS” or “Account information”) and in your Cloudflare DNS tab — the proxied A record (orange cloud) contains the origin address. On the server itself, curl -4 ifconfig.me or ip addr prints it. Trying to uncover the origin of someone else's site is not something this tool does: the owner hid it deliberately.
One IP, many websites: shared hosting
On shared hosting dozens or hundreds of sites live on one IP, and the web server tells them apart by the domain name in each request. That is why typing the IP into a browser usually doesn't open the site you looked up. To see the neighbours, use a reverse IP lookup. For SEO a shared IP is not a problem in itself — Google has said many times that sharing an address with other sites doesn't affect rankings. What matters more is whether the IP is on spam lists, which an IP blacklist check will tell you.
IPv6: what an AAAA record — or its absence — means
An AAAA record holds an IPv6 address such as 2606:4700::6810:84e5. Without one, the site is reachable over IPv4 only, which most visitors never notice because their providers support both. The opposite case is worse: an AAAA record exists but the server doesn't answer over IPv6, so some users get slow loads or timeouts. After moving hosts, check that no AAAA record is left pointing at the old server.
How to look up a domain's IP from the command line
The same data is available without a browser:
nslookup example.com dig example.com A +short dig example.com AAAA +short host example.com Resolve-DnsName example.com # PowerShell on Windows
dig shows the TTL and lets you query a specific resolver: dig example.com @1.1.1.1. ping example.com also prints an IP, but only one, and if ICMP is blocked you get no reply even though the site works fine.
The IP changed but the old server still answers
After a hosting move, resolvers keep returning the old address until the cached TTL runs out — up to an hour with a TTL of 3600, sometimes longer with providers that ignore it. To see which address resolvers in different countries return, run a DNS propagation check; to see which company hosts an IP, use the hosting checker.