🔷 DNS AAAA Record Lookup

Query DNS AAAA records to find the IPv6 addresses associated with any domain name. AAAA records are essential for modern IPv6-enabled websites and networks.

💡 Tip: Enter a domain name and click "Lookup AAAA Record" to retrieve all IPv6 addresses associated with that domain.
Enter a domain name and click "Lookup AAAA Record" to view results.

What the lookup actually does

The domain is sent to SimpleMoney's API, which runs the AAAA query on a server in AWS us-east-1 and returns the IPv6 addresses it was given. Nothing is resolved in your browser, and that matters more for AAAA than for any other record type: this server has working IPv6, and a great many home and office networks still do not.

So a result here says the domain publishes an IPv6 address. It does not say you can reach it. If the address appears on this page but your own ping6 times out, the record is fine and your connectivity is the thing to check.

Reading an IPv6 address

An AAAA record holds one 128-bit address, written as eight groups of four hex digits, such as 2606:2800:220:1:248:1893:25c8:1946. Runs of zero groups collapse to ::, which may appear only once in an address, so 2001:db8::1 and 2001:0db8:0000:0000:0000:0000:0000:0001 are the same address written two ways.

Publishing an AAAA record before the IPv6 side of the server really works is the classic way to make a site feel slow: dual-stack clients try IPv6 first and wait for it to fail before falling back.

Frequently asked questions

Why does my domain have no AAAA record?

Because nobody added one. IPv6 is opt-in on nearly every host, so a domain gets an AAAA record only when you or your provider publishes it. The site works perfectly well over IPv4 without it.

Should I add an AAAA record?

Add one when the server genuinely answers on IPv6, and test that first. Mobile networks in particular are heavily IPv6, so a correct record helps them; a wrong one costs every dual-stack visitor a timeout.

Why can I not connect to the address shown?

Most likely your network has no IPv6 route at all. The query here ran from a server that does, which is exactly why the two results disagree.