Find a Domain's IPv4 & IPv6 Addresses
Quickly look up a domain's IPv4 and IPv6 DNS records using Google Public DNS.
What is a Domain to IP Lookup?
Forward DNS resolution — translating a human-readable domain name into the IP address returned by DNS.
The Internet's Phonebook
Websites and online services are reachable through IP addresses. DNS maps human-readable domain names to the IP addresses returned for those names. Since humans can't easily remember long sequences of numbers, we use domains like google.com. When you enter a domain, your device queries the Domain Name System (DNS) to find the corresponding IP addresses — just like looking up a phone number in a directory.
A Records & AAAA Records
DNS stores IP addresses in two types of records: A records hold IPv4 addresses (the traditional 32-bit format like 192.0.2.1) and AAAA records hold IPv6 addresses (the modern 128-bit format). Many domains have both, and large sites often have multiple A/AAAA records for load balancing.
Why Multiple IPs?
Popular websites run on many servers simultaneously. DNS can return multiple IP addresses for one domain, and the client/network stack selects an address to attempt. This distributes traffic, provides redundancy, and improves performance through CDNs and geo-routing.
How This Tool Works
Enter a public domain name and our server queries Google Public DNS for both A records (IPv4) and AAAA records (IPv6) . You get a clean list of the A and AAAA addresses returned by Google's Public DNS — with one-click copy for each .
Domain to IP Converter
Enter the domain (e.g., google.com or www.google.com) or the full URL. We'll strip the protocol automatically and resolve both IPv4 and IPv6 addresses.
IPv4 vs IPv6 — What's the Difference?
The internet is transitioning from IPv4 to IPv6. Here's how they compare.
| Feature | IPv4 (A Record) | IPv6 (AAAA Record) | Why It Matters |
|---|---|---|---|
| Format | 4 numbers (0–255) separated by dots | 8 groups of 4 hex digits separated by colons | IPv4 is easier for humans to read; IPv6 is much longer but more systematic. |
| Example | 142.250.185.206 | 2607:f8b0:4009:818::200e | IPv6 can use :: shorthand to compress consecutive zero groups. |
| Address Space | 32 bits = ~4.3 billion addresses | 128 bits = 340 undecillion addresses | IPv4 addresses are exhausted. IPv6 provides effectively unlimited addresses. |
| Adoption | Universal — every device supports it | Global integration growing steadily | IPv6 adoption continues to grow, but availability varies by network, region, and service. |
| DNS Record Type | A | AAAA | Our tool queries both automatically. |
| Performance | Comparable | Comparable | Performance depends on the network, routing, connectivity, and implementation. IPv6 can avoid some IPv4 NAT scenarios, but it is not inherently faster. |
| Security | Security depends on protocols and configuration | Security depends on protocols and configuration | Neither address format automatically makes an application secure. |
What Happens Behind the Scenes
The journey from a domain name to a DNS answer.
Your Browser Asks
What happens: You type google.com and hit Enter.
Behind the scenes: Browser checks local DNS cache first. If not cached, asks the OS resolver.
Recursive Resolver
What happens: Your ISP or a public DNS resolver receives the query.
Behind the scenes: The resolver doesn't know the answer, so it starts asking the root servers.
Root → TLD → Authoritative
What happens: Chain of referrals: root servers point to .com servers, which point to google.com's name servers.
Behind the scenes: Each step narrows down until the authoritative server is found.
Authoritative Answer
What happens: The domain's authoritative nameservers provide the DNS answer.
Behind the scenes: The recursive resolver caches the answer according to its TTL and returns it to the requester.
Connection Established
What happens: Your browser connects to the IP address.
Behind the scenes: TCP handshake + TLS handshake (if HTTPS), then HTTP request is sent to the server.
Typical DNS Resolution Time
Reality: DNS resolution time varies by resolver, cache state, network conditions, and the domain. Cached responses can be much faster than uncached lookups. This tool performs the same lookup server-side using Google's Public DNS.
Master Domain to IP Conversion — Step-by-Step
A detailed guide explaining how domains connect to IP addresses, how DNS resolution works, what happens behind the scenes when you open a website, and how to convert a domain name to its DNS-resolved IP addresses.
📘 Read Full Domain to IP Guide →Honest by Design — What This Tool Does and Doesn't Do
This tool performs forward DNS resolution. Here is exactly what it does and does not do:
- ✓ Resolves A (IPv4) and AAAA (IPv6) records using Google Public DNS.
- ✓ Shows the IP addresses returned in the DNS response.
- ✓ Performs the DNS request server-side, preventing the target domain from seeing your browser's IP address.
- ✓ Does not intentionally store submitted domains in our application database.
- ✓ Uses temporary rate-limit data to help prevent abuse.
- ✓ Provides one-click copying for individual IP addresses and the full result.
- ✕ Does not perform reverse DNS.
- ✕ Does not reveal an origin server hidden behind a CDN.
- ✕ Does not query MX, TXT, or other DNS record types.
- ✕ Does not resolve private/internal DNS zones.
This tool does
- Query Google Public DNS for A (IPv4) records
- Query Google Public DNS for AAAA (IPv6) records
- Show multiple IPs when returned in the DNS response
- Work for public domains resolved by Google DNS
- Copy individual IPs or full report
- Keep your browser IP private from the target host
This tool does not
- Perform reverse DNS (IP → domain)
- Show IP geographic location
- Query MX, TXT, or other record types
- Resolve private/internal domains
- Store the domains you convert in our database
- Guarantee the IP is the hidden origin behind a CDN
How to Use This Converter
Four simple steps from domain to IP addresses.
Enter domain
Type or paste a public domain — google.com, github.com, etc.
Click Find IP
Our server queries Google DNS for A and AAAA records.
View results
See the IPv4 and IPv6 addresses returned by Google Public DNS.
Copy & use
Copy individual IPs or the full report for your needs.
Resolution Problems and Fixes
Why a domain might not resolve, or show unexpected IPs.
"No records found"
The domain has no A or AAAA records configured.
Fix: The domain may be new, parked, or only used for email (MX records). Check if the domain actually hosts a website.
CDN IP Instead of Origin
Resolved IPs belong to Cloudflare, CloudFront, Akamai instead of the actual server.
Reality: This is normal — the domain uses a CDN. The origin server IP is hidden by design. Use hosting lookup tools to identify the CDN provider.
Different IPs Each Time
Resolving the same domain gives different IP addresses on different checks.
Reality: These are valid IP addresses returned in the DNS response.
Old IP After DNS Change
You changed DNS records but the tool still shows the old IP.
Fix: After a DNS change, cached answers may continue to appear until their TTL expires. Different resolvers may update at different times.
Geo-DNS Returns Different IPs
Users in different countries see different IPs for the same domain.
Reality: Our tool shows the answer returned by Google Public DNS, which may differ from answers returned by other DNS resolvers or from users in different locations.
Private / Local Domains
Internal domains (e.g., server.local, dev.internal) don't resolve.
Reality: These only exist on your local network. This tool only works with public DNS. Use your local DNS server or nslookup command for private domains.
When to Use This Converter
Use the tool for these common scenarios.
Domain to IP Converter FAQs
Answers based on what this tool does and how DNS resolution works.
Why does a domain have multiple IP addresses?
Large websites use multiple servers to handle traffic — a practice called load balancing. Each server has its own IP. DNS can return all of them, and your browser picks one to connect to. This provides redundancy (if one server fails, others still work) and distributes load for better performance.
What's the difference between IPv4 and IPv6?
IPv4 uses 32-bit addresses (e.g., 142.250.185.206) — only 4.3 billion possible addresses, now exhausted. IPv6 uses 128-bit addresses (e.g., 2607:f8b0:4009:818::200e). IPv6 adoption continues to grow globally, but availability varies by network, region, and service.
Is this tool free?
Yes, free to use. We apply rate limits (30/hour, 200/24h per IP) to protect server resources and prevent abuse.
Why does the IP change when I check again?
This is normal for load-balanced sites — DNS round-robin returns different IPs from a pool. Also, if the domain changed DNS records recently, you might see the old IP until the previous TTL expires.
Can I find the IP of a private/internal domain?
No — this tool only resolves public domains via Google's Public DNS. Private domains (like server.local or dev.internal) only exist on your local network. Use your local DNS server, the nslookup command, or dig for private domains.
Why does the IP belong to Cloudflare/CloudFront?
The domain is using a CDN (Content Delivery Network). The CDN's IP is what visitors actually connect to — the origin server IP is hidden behind it. This is by design. Our tool shows the CDN IP, which is the DNS answer returned for that domain through the queried resolver.
Can I find which domain an IP belongs to?
This tool does forward resolution (domain → IP). For reverse resolution (IP → domain), use a reverse DNS lookup or our Whois Lookup tool. Note: many IPs don't have reverse DNS configured, so IP → domain may return nothing.
Are the domains I convert stored?
The tool does not intentionally store submitted domains in its application database. Temporary rate-limit data is used for abuse prevention. DNS resolution queries happen server-side, preventing the target domain from receiving your browser's IP .