Resolve any domain name to its IP addresses. This tool queries both A (IPv4) and AAAA (IPv6) records using Google Public DNS, showing all IP addresses a website resolves to along with TTL values.

A website IP lookup resolves a domain name to its corresponding IP addresses using the Domain Name System (DNS). Every website is hosted on a server identified by an IP address — either IPv4 (like 104.21.32.1) or IPv6 (like 2606:4700:3030::ac43:8f01). When you type a URL into your browser, a DNS resolver performs this translation automatically before your browser can connect.
This tool queries both A records (IPv4) and AAAA records (IPv6) to give you a complete picture of where a website's servers are located. This is useful for troubleshooting, security analysis, and understanding your network's DNS configuration.
There are several practical reasons to resolve a domain to its IP address:
Pro Tip: If a domain returns multiple IP addresses, it typically means the site uses a CDN or load balancer. The actual origin server IP is hidden behind these services for security and performance. To find your own public IP address, use our What Is My IP tool. To learn more about IP addresses in general, see our guide on what an IP address is.
DNS uses different record types for IPv4 and IPv6 addresses:
| Record Type | IP Version | Address Format | Example |
|---|---|---|---|
| A | IPv4 | 32-bit dotted decimal | 104.21.32.1 |
| AAAA | IPv6 | 128-bit colon hexadecimal | 2606:4700:3030::6815:2001 |
Most websites have A records for IPv4 compatibility. Increasingly, sites also publish AAAA records for IPv6 connectivity. Large providers like Cloudflare, Google, and Facebook fully support IPv6. You can use our Subnet Calculator to analyze IPv4 address ranges or the IP Lookup tool for geolocation information.
When your browser needs to connect to a website, the DNS resolution process follows these steps:
This entire process typically takes 10-100 ms. The DNS resolver you use greatly affects performance — run our DNS Speed Benchmark to compare providers. For encrypted queries, try our DNS over HTTPS Tester.
You can resolve domain names using built-in command-line tools on any operating system:
nslookup example.com
nslookup -type=AAAA example.com
ping example.com
dig example.com A +short
dig example.com AAAA +short
host example.com
nslookup example.com 1.1.1.1
# Query Cloudflare DNS
dig @1.1.1.1 example.com A
# Query Google DNS
dig @8.8.8.8 example.com AAAA
If you're getting different results from different DNS servers, it may be due to CDN geo-routing or DNS caching. Compare results from your ISP DNS vs custom DNS to identify discrepancies.
Recognizing IP address ranges helps identify which service hosts a website:
| Provider | IPv4 Ranges (examples) | How to Identify |
|---|---|---|
| Cloudflare | 104.16.0.0/12, 172.67.0.0/16 | Usually 2 IPs, fast TTL changes |
| AWS | 52.x.x.x, 54.x.x.x, 3.x.x.x | Varies by region, check WHOIS |
| Google Cloud | 35.x.x.x, 34.x.x.x | Often static IPs for GCE instances |
| Microsoft Azure | 13.x.x.x, 20.x.x.x, 40.x.x.x | Regional allocation, check WHOIS |
| GitHub Pages | 185.199.108-111.x | Always 4 IPs in this range |
| Netlify | 75.2.60.5 | Load balancer IP with CNAME |
Use our IP Address Lookup tool for detailed geolocation and WHOIS information about any IP address.
If a domain isn't resolving correctly, try these steps:
Multiple IP addresses indicate load balancing or CDN usage. Traffic is distributed across several servers for reliability and performance. If one server fails, others continue serving the website.
Sometimes. If the server is configured with a default virtual host, entering the IP in your browser will load the site. However, most modern hosting uses name-based virtual hosting, where multiple domains share one IP. In that case, the server needs the domain name (via the HTTP Host header) to serve the correct site.
This is geo-DNS or anycast routing. CDNs and large providers direct users to the nearest data center by returning location-specific IP addresses. This reduces latency and improves loading speed for users worldwide.
Cloudflare intentionally hides origin server IPs for DDoS protection. You generally cannot find the real IP through DNS. Historical DNS records, SSL certificate transparency logs, or misconfigured subdomains may occasionally reveal the origin IP, but this is a security concern rather than a feature.
It means the website doesn't have IPv6 connectivity. The site is only accessible over IPv4. While IPv6 adoption is growing, many websites still operate on IPv4 only. This doesn't cause issues for most users since ISPs support both protocols.
Not necessarily. IP geolocation is approximate and identifies the data center location, not the website owner's physical location. CDN IPs resolve to the nearest edge server, which may be in a different country from the origin server.
Dynamic IPs are common with CDNs, cloud providers, and load balancers. Cloudflare regularly rotates IPs for security. If you use a dynamic IP for your home server, set up DDNS to keep your domain pointed at the correct address.
About Tommy N.
Tommy is the founder of RouterHax and a network engineer with 10+ years of experience in home and enterprise networking. He specializes in router configuration, WiFi optimization, and network security. When not writing guides, he's testing the latest mesh WiFi systems and helping readers troubleshoot their home networks.
![]() |
![]() |
![]() |
![]() |
Promotion for FREE Gifts. Moreover, Free Items here. Disable Ad Blocker to get them all.
Once done, hit any button as below
![]() |
![]() |
![]() |
![]() |