Free DNS tool

Website IP Address Lookup

Find every IPv4 and IPv6 address behind a domain, with reverse DNS, the CDN in front of it, and where each address is registered.

Try , ,

Resolves over DNS-over-HTTPS in your browser. Country is the registry the address block is registered to, which is not always where the server physically sits.

Knowing the address is one thing, knowing it still answers is another. Pulsetic checks your site from 15 locations worldwide and tells you the moment one of them cannot reach it.

What a website IP lookup actually shows you

Every domain name has to resolve to a number before anything can connect to it. That translation is what DNS does, and an IP lookup is simply asking for the answer directly instead of letting the browser do it quietly in the background.

The A record holds the IPv4 address, the familiar four-number form. The AAAA record holds the IPv6 address, and a well-configured site usually publishes both. If a domain returns several addresses, that is normal: it can mean multiple servers sharing the load, or an anycast network announcing one address from many places at once.

Why the address is often not the server

This is the part that surprises people. If a site sits behind Cloudflare, Fastly, CloudFront or Akamai, the address DNS hands back belongs to the CDN, not to the machine running the site. The origin server sits behind it, and public DNS has no way to reveal it. That is the entire point of the arrangement, and no lookup tool can work around it.

The same caution applies to location. The country shown here comes from the regional internet registry that allocated the address block. It is accurate about who holds the block, and only loosely indicative of where any particular machine is. A block registered in the United States can quite legitimately be routed to hardware in Frankfurt.

When the address behind a domain matters

Usually during a migration. You have repointed a record and want to confirm the change took, or you are chasing a report that the site works for some people and not others and you need to know whether they are being sent to the same place. A lookup answers the first question; comparing several resolvers with the DNS propagation checker answers the second.

It also matters for allowlists. Firewall rules and API allowlists are written against addresses, and cloud providers change those addresses without notice, so a rule that worked last quarter can quietly stop matching. If your site sits behind a firewall, our domain monitoring checks it from outside that boundary, which is where your visitors are.

Frequently asked questions

  • How do I find the IP address of a website?

    Enter the domain above. The tool resolves its A records (IPv4) and AAAA records (IPv6) through public DNS, then looks up the reverse DNS name and registration country for each address it finds. It is the same query your browser makes before it loads a page.

  • Why does one site return several IP addresses?

    Most large sites do. A domain can carry many A records so traffic spreads across servers, and anycast networks announce the same address from data centres worldwide. Several addresses is a sign of a healthy setup, not a misconfiguration.

  • Does the IP address tell me where a website is hosted?

    Roughly, and less often than people expect. The country shown here is where the address block is registered with its regional internet registry, which is not always where the machine physically sits. If a CDN sits in front of the site, the address belongs to the CDN and the real server could be anywhere.

  • What is reverse DNS?

    The PTR record, which maps an address back to a host name. Providers use it to label their infrastructure, so a reverse lookup often names the host or CDN even when nothing else does. Plenty of addresses have no PTR record at all, and that is normal rather than a fault.

  • Why does the tool say the site is behind a CDN?

    Because the address it resolves to belongs to one. When a site runs behind Cloudflare, Fastly, CloudFront or Akamai, DNS hands out the CDN edge address rather than the origin server, so that is what any lookup can see. Finding the origin behind a CDN is deliberately not possible from public DNS.

  • What is the difference between an A record and an AAAA record?

    An A record holds an IPv4 address such as 93.184.216.34. An AAAA record holds an IPv6 address such as 2606:2800:220:1::. A domain can have both, and modern clients will usually prefer IPv6 when it is offered.

  • Can I look up the IP of any website?

    Yes. DNS records are public by design, since every resolver on the internet has to be able to read them. Nothing here touches the site itself: the tool only asks public DNS resolvers what the domain points to.

  • The IP changed since I last checked. Why?

    Cloud hosts and CDNs reassign addresses routinely, and many domains rotate through a pool by design. If you need to know when the address behind a domain changes, that is worth monitoring rather than spot-checking.

Trusted by teams at companies around the world