Website IP Address Lookup

Website IP Address Lookup shows the IPv4 (A) and IPv6 (AAAA) addresses a domain actually points to, in real time. Enter a domain and you'll see every public IP configured for that host — making it easy to tell where a server lives, whether it sits behind a CDN, and whether it supports IPv6.

The lookup queries A and AAAA records in parallel against a trusted public resolver over DNS over HTTPS. Results are briefly cached for speed, and each address can be copied with one click. Just enter the domain — no protocol or path needed. To see the region or carrier behind an IP you find, follow up with IP Geolocation.

A records vs. AAAA records

The IP a domain points to is stored in DNS as A records (IPv4) and AAAA records (IPv6). An A record holds a 4-byte address like 203.0.113.10, while an AAAA record holds a 16-byte address like 2001:db8::1. Many sites only set an A record, but modern infrastructure usually serves both IPv4 and IPv6.

Why a domain has multiple IPs (CDN, load balancing)

• CDN / load balancing: with Cloudflare, CloudFront and similar, you get the IP of a nearby edge node, so the value varies by location and time.
• Multiple A records: a domain may list several IPs to spread traffic across servers.
• Shared IPs: one IP can host many domains, so an IP alone doesn't identify a single site.

How domains and IPs relate

A domain is a human-friendly name; an IP is the numeric address that identifies a real server. DNS connects the two. For a site behind a CDN, the IP shown here may be an edge node rather than the origin server. To find which network (ASN) an IP belongs to, use IP ASN Lookup.

How to tell if an IP is a CDN (common ranges)

If a returned IP falls inside one of the ranges below, the address you see is almost certainly a CDN or cloud edge rather than the origin server. With Cloudflare in particular, nearly every site collapses onto the same 104.16.0.0/13 family, so that IP tells you nothing about the real backend.

Reading a real example

Say a lookup returns two A records, 104.18.22.45 and 104.18.23.45, plus an AAAA of2606:4700::6812:162d. Both IPv4s sit inside 104.16.0.0/13 and the IPv6 starts with2606:4700::, so the site is behind Cloudflare and what you see are edge nodes — this result alone can't tell you which data center actually hosts the server. Conversely, a single 185.199.110.153strongly suggests a static site served from GitHub Pages.

Common pitfall

• Don't ping, block, or report the IP shown here as-is. If it's a CDN edge, tens of thousands of unrelated sites share that address, so you'd be hitting the wrong target.
• A single IP doesn't mean a single server. Anycast (Cloudflare and others) advertises the same IP from many physical machines worldwide, so one address can sit in front of dozens of data centers.
• Results can differ with or without www. example.com and www.example.com are separate records, and it's common for only one of them to be CNAME'd onto a CDN.