🌐 Domain to IP: Find the IP Address of Any Domain

What is the Domain to IP?

Every website lives on a server, and every server on the internet is reached through a numeric IP address. People remember names like example.com, but computers route traffic using numbers such as 93.184.216.34. A domain to IP lookup is the bridge between the two: it asks the Domain Name System (DNS), the internet's global address book, which IP address a given domain currently maps to. When you type a domain into this tool and run it, you are performing the same first step your browser performs every time you open a site.

DNS stores several kinds of records for a domain, and two of them carry IP addresses. The A record holds the IPv4 address, the familiar four-number format like 192.0.2.10. The AAAA record (read as "quad-A") holds the IPv6 address, the newer and much longer format like 2606:2800:220:1:248:1893:25c8:1946 that exists because the world ran out of free IPv4 addresses. A single domain can have several A and AAAA records at once, which is normal for large sites that spread traffic across many servers or sit behind a content delivery network. This domain to IP tool lists every address it receives so you see the full picture, not just the first one.

It is worth understanding that a domain and an IP address are not always a tidy one-to-one pair. Many domains share a single IP through virtual hosting, where one server answers for hundreds of sites and uses the requested hostname to decide which one to serve. Conversely, one busy domain may rotate through dozens of IPs for load balancing. If the site sits behind a service like Cloudflare, the IP you see belongs to that provider's edge network rather than the origin server, which is by design and helps hide and protect the real host. So the IP returned by any domain to IP lookup is the publicly published answer, which is exactly what you usually want, but it is not always the physical machine the content lives on.

DNS answers are also cached. Each record carries a TTL (time to live) value, measured in seconds, that tells resolvers how long they may reuse the answer before checking again. That is why a freshly changed domain can still resolve to an old IP for a while: somewhere along the chain a cached copy has not yet expired. A TTL of 300 means five minutes, 3600 means one hour, and 86400 means a full day. This tool queries a public resolver directly and shows the TTL alongside each record, so you can judge how fresh the answer is and roughly how long it will be reused.

Under the hood, this domain to IP converter uses DNS over HTTPS (DoH) against Google Public DNS. Instead of the traditional plain UDP query on port 53, the lookup is sent as an ordinary HTTPS request to dns.google and the answer comes back as JSON. DoH is encrypted, works from inside the browser without any plugin, and is supported with permissive cross-origin headers so a static page like this one can call it directly. That is what lets the whole tool run client-side, for free, with no server of our own and no key to manage. Because the query goes to the same resolver millions of people use, the answer reflects the public, authoritative view of the domain.

Knowing a domain's IP address is useful far beyond curiosity. Network administrators use it to confirm that a DNS change has propagated, to add a firewall rule, or to check that a domain points where it should after a migration. Security analysts map suspicious domains to their hosting to spot patterns and shared infrastructure. Developers verify that staging and production point to the right servers. Anyone troubleshooting a site that "works for me but not for you" can compare the IP each person resolves to and quickly tell whether the problem is DNS, caching, or the server itself. In every one of these cases, a fast domain to IP lookup is the quickest way to turn a name into an actionable address.

When to use it

• Confirming a DNS change has taken effect after moving a site to a new host, by checking the domain now resolves to the new IP address.
• Finding the IPv4 and IPv6 addresses of a website before adding a firewall, allowlist, or hosts-file entry.
• Troubleshooting a site that loads for some visitors but not others, by comparing the IP each location resolves to.
• Checking whether a domain sits behind a CDN such as Cloudflare, since the returned IP belongs to the provider rather than the origin.
• Verifying that staging and production domains point to the correct servers during a deployment or migration.
• Quickly mapping a domain to its hosting IP for a security or due-diligence review without installing command-line tools.

How to use the Domain to IP

1. Type or paste the domain you want to check into the box, for example example.com. A full URL is fine; the protocol, www and path are removed automatically.
2. Press the Find IP address button (or hit Enter). The tool does not run on page load, so nothing is queried until you ask for it.
3. Wait for the brief loading message while the live DNS lookup runs against Google Public DNS over HTTPS.
4. Read the results: IPv4 addresses from the A record appear on the left, IPv6 addresses from the AAAA record on the right, each with its TTL.
5. Use the Copy button next to any address to copy that exact IP to your clipboard.
6. If you see a friendly "no records" message, double-check the spelling, as the domain may be unregistered or have no public IP.

Formula & method

Worked examples

DNS record types involved in a domain to IP lookup

IPv4 versus IPv6 at a glance

Common TTL values and what they mean

Common mistakes to avoid

• Assuming the returned IP is the real origin server. If a domain uses a CDN or reverse proxy such as Cloudflare, Fastly or Akamai, the IP you get back belongs to that provider's edge, not the machine hosting the files. This is intentional and protects the origin, so do not treat the visible IP as the physical host.
• Expecting one domain to have exactly one IP. Large sites publish several A and AAAA records for load balancing and redundancy. Seeing multiple addresses is normal and healthy, not an error. This tool lists all of them rather than only the first.
• Forgetting that DNS answers are cached. A recent DNS change may not appear everywhere immediately because resolvers reuse cached answers until the TTL expires. If an IP looks out of date, the TTL value shown tells you how long the old answer may still be served.
• Including the protocol or path in the domain. A DNS query needs a hostname, not a URL. Entering https://example.com/page works here because the tool cleans it, but a raw DNS command would fail. Always resolve the bare domain such as example.com.
• Confusing no IPv6 record with the site being down. Plenty of perfectly working domains have no AAAA record yet. An empty IPv6 panel simply means the domain is not published over IPv6, not that it is broken.
• Trying to resolve a subdomain that does not exist. A typo in the subdomain (such as wwww instead of www, or an internal-only host) returns no records. Check the exact hostname before concluding the domain has no IP address.

Glossary

Domain to IP

The process of looking up which IP address a given domain name currently points to, using DNS.

IP address

A numeric label that identifies a device or server on a network so traffic can be routed to it.

DNS

The Domain Name System, the internet's distributed directory that translates domain names into IP addresses.

A record

A DNS record that maps a domain name to its IPv4 address.

AAAA record

A DNS record that maps a domain name to its IPv6 address, read aloud as "quad-A".

TTL

Time to live, the number of seconds a DNS answer may be cached and reused before being looked up again.

DNS over HTTPS (DoH)

A method of sending DNS queries inside encrypted HTTPS requests, which lets this tool resolve domains directly from the browser.

CDN

A content delivery network of edge servers; when a domain uses one, the resolved IP usually belongs to the CDN rather than the origin host.

CNAME

A DNS alias record that points one name at another name, which is then resolved onward to an A or AAAA record.

DNS propagation

The time it takes for a DNS change to be seen everywhere as old cached answers expire across the world's resolvers.

Frequently asked questions