Find the IP Address of a Website
Enter a domain and PureIP resolves it to its IP addresses, then shows which network each address belongs to — hosting provider, ASN, and whether it is fronted by a CDN.
Who this is for: People verifying where a site is really hosted, and whether a CDN or WAF is hiding the origin.
The short answer
Every website is served from an IP address, and you can read it in a couple of seconds. The complications are that a domain usually resolves to more than one address, those addresses change without warning, and for most popular sites they belong to a CDN rather than to the website's own servers.
How to find a website's IP
1. Resolve the domain. A DNS lookup returns the A records (IPv4) and AAAA records (IPv6) the domain currently points at. That is the address your browser will actually connect to.
2. Look past the first answer. Domains routinely return several addresses for load balancing or redundancy, and the set differs by region because DNS answers are served from wherever the resolver is.
3. Check who owns the address. Run the IP through a WHOIS lookup to see the organisation, netblock and ASN. This is how you tell whether the site runs on its own hardware, on a cloud provider, or behind a CDN.
4. Re-check if the answer looks wrong. If the address belongs to Cloudflare, Fastly, Akamai or AWS CloudFront, you have found the front door, not the origin server. The site's real server is hidden behind it, and no lookup can reveal it from the outside.
Why the answer changes
Anycast and global load balancing mean the same hostname resolves differently depending on where you ask. CDNs also rotate addresses as capacity changes. And any migration — new host, new CDN, failover — rewrites the records within minutes.
This is why a website's IP is not a stable identifier of the website. If you need something stable to allowlist or block, use the hostname, or accept that you will be maintaining the list.
What people actually use this for
- Checking where a site is hosted before you rely on it, or before you complain to the wrong provider.
- Confirming a migration actually moved. A DNS change is the whole migration from the outside, and a stale resolver cache is why some users still see the old host.
- Security and abuse work. Mapping a domain to a netblock is the first step in figuring out who to contact.
- Building allowlists. If your firewall or scraper has to permit a partner's service, you need the addresses — and a plan for when they change.
- Curiosity with a purpose: seeing which of the big CDNs a site picked tells you a lot about how it is operated.
Frequently asked questions
Can I find the IP of any website?
Yes. DNS resolution is public, so the address a domain points at is readable by anyone with a lookup tool. What you cannot see from outside is the origin server behind a CDN.
Why does a website have multiple IP addresses?
For redundancy and load balancing, and because CDNs answer from many locations. Multiple A records mean your client can pick a reachable address if one fails.
The IP I found belongs to Cloudflare. Is that the real server?
No. It is the CDN edge that proxies the site. The origin server is protected by the CDN and is not discoverable through DNS.
Will the IP change?
Probably. CDNs rotate addresses and any hosting or DNS change rewrites them. If you depend on a specific address, monitor it rather than assuming it will stay.
Related tools
PureIP — free IP lookup and network diagnostics: IP location, WHOIS, reverse DNS, reputation, blacklists, AI service reachability and global ping.