A Record Lookup
Find the IPv4 address a domain points to. Enter a domain and this tool queries its A records live and lists every IPv4 address it resolves to, with TTLs. If the name is a CNAME alias rather than a direct address, the tool shows that too. This is the fastest way to answer "what IP does this domain resolve to right now?".
Runs in your browser over DNS-over-HTTPS (Google / Cloudflare). Nothing is sent to our server and nothing is stored.
How to use the A Record Lookup
Enter a domain or hostname and press Look up A records. The tool reports:
- Every IPv4 address the name resolves to, with its TTL.
- A flag when the name returns multiple A records (round-robin or a multi-homed setup).
- The CNAME chain instead, if the name is an alias rather than a direct address record.
This queries IPv4 (A) records specifically. For the IPv6 equivalent, look up the AAAA record; for the reverse direction (IP back to a hostname) use the Reverse DNS Lookup.
What an A record is
An A record is the most fundamental record in DNS: it maps a hostname to an IPv4 address. When you type a domain into a browser, the resolver looks up its A record to find the numeric address to actually connect to. The "A" stands for Address, and it is the link between the human-friendly name and the machine the name lives on.
A few things the A record can tell you:
- Multiple A records for one name spread traffic across servers. Resolvers hand out the addresses in rotating order — classic DNS round-robin — or the addresses front a load balancer. Seeing several A records is normal for a busy site.
- A shared IP often means the site sits behind a CDN or reverse proxy (Cloudflare, Fastly) or on shared hosting, where one address serves many domains and the right site is chosen by the Host header or SNI.
- A CNAME instead of an A means the name is an alias. Subdomains like
wwwfrequently CNAME to a CDN or platform hostname, and the real A record lives on that target. This tool surfaces the alias so you know to look at the target for the address.
The TTL on an A record matters whenever you plan to move a site to a new server. Resolvers cache the address for the TTL, so visitors keep hitting the old IP until it expires. The standard practice is to lower the TTL a day or two before a migration (to a few minutes), make the switch, confirm the new A record here, then raise the TTL again once everything is stable. Note that A records are not allowed to coexist with a CNAME at the same name, and the zone apex (the bare domain) must use an A record or an address-style alias rather than a plain CNAME.
Common use cases
- Finding a domain's IP — get the IPv4 address a site currently resolves to.
- Verifying a server move — confirm the A record now points at the new host after a migration.
- Spotting a CDN or proxy — a shared or anycast IP usually signals Cloudflare, a CDN or shared hosting.
- Checking round-robin — see whether a name publishes several A records for load spreading.
- Debugging "wrong site loads" — confirm the name resolves where you expect, not to a stale or parked IP.
A records, AAAA, and CNAME — which is which
Three record types answer "where does this name point", and it helps to keep them straight:
- A — maps a name to an IPv4 address (this tool). The classic
93.184.x.xform. - AAAA — maps a name to an IPv6 address (the
2606:…form). A modern host often publishes both A and AAAA so it is reachable over either protocol. - CNAME — makes a name an alias for another name, which then provides the addresses. Common on subdomains pointing at a CDN or SaaS host.
If an A lookup comes back empty, check AAAA (the host may be IPv6-only) and CNAME (the name may be an alias). To inspect any of these in one place, use the general DNS Lookup; to go from an IP back to a name, use the Reverse DNS Lookup.