AAAA (IPv6) Lookup

Find the 128-bit IPv6 addresses associated with any domain name.

About AAAA Records & IPv6

An AAAA record (also known as "quad A") functions exactly like an A record, but it points to a 128-bit IPv6 address instead of a 32-bit IPv4 address.

Because the world has officially run out of available IPv4 address space, IPv6 is the future of the internet protocol. Modern websites should configure both A and AAAA records (known as "Dual Stack" implementation) to ensure all users can connect optimally.

Our AAAA Record Lookup queries authoritative DNS servers for the IPv6 addresses assigned to any domain. Results include every AAAA record, its TTL, and an assessment of IPv6 readiness — returned in under a second with no signup required.

What is an AAAA Record?

An AAAA record (pronounced "quad-A") is a DNS record that maps a domain name to an IPv6 address. It is the IPv6 equivalent of the A record, which maps to IPv4.

Where an A record stores a 32-bit address like 93.184.216.34, an AAAA record stores a 128-bit address like 2606:2800:220:1:248:1893:25c8:1946. The name comes from the size difference — an IPv6 address is four times larger than an IPv4 address, hence four As.

When a browser or mail server resolves a domain, it queries for both A and AAAA records. On a dual-stack network, most modern clients prefer the AAAA result using the Happy Eyeballs algorithm defined in RFC 8305.

Maps a hostname to a 128-bit IPv6 address
Defined in RFC 3596 — the IPv6 counterpart of the A record
Modern clients prefer AAAA over A on dual-stack networks
Required for your site to be reachable on IPv6-only networks
A domain can publish multiple AAAA records for redundancy

Why IPv6 AAAA Records Matter

IPv4 address space has been exhausted since 2011. Mobile carriers, large ISPs and cloud providers increasingly run IPv6-only networks with NAT64 gateways for legacy IPv4 traffic. Without an AAAA record, visitors on those networks reach you through a translation layer — adding latency, breaking some protocols, and hiding real client IPs from your logs.

Google, Cloudflare and major CDNs report that over 40% of their traffic now arrives over IPv6. Publishing AAAA records removes an unnecessary hop for all of that traffic.

Over 40% of global traffic to major providers now arrives over IPv6
IPv6-only mobile networks reach IPv4-only sites through slower NAT64 translation
Direct IPv6 connectivity preserves accurate client IP data in your logs
Some government and enterprise procurement rules mandate IPv6 support
A missing AAAA record is invisible to most owners until users complain

How This AAAA Record Lookup Works

The tool performs a live DNS query for the AAAA record type against public resolvers and parses every result returned.

Validates the domain input against format and SSRF safety checks
Issues a DNS query of type AAAA for the supplied hostname
Collects every returned IPv6 address along with its TTL value
Normalises each address to its canonical compressed form
Flags domains with no AAAA record as not IPv6-ready

How to Use the AAAA Record Lookup

Enter a domain name such as example.com in the input field
Click the lookup button to run a live DNS query
Review every IPv6 address returned along with its TTL
If no record is returned, your domain is not reachable over IPv6
Cross-check with the A Record Lookup to confirm a dual-stack setup

Understanding Your AAAA Record Results

Each AAAA record returns an IPv6 address and a time-to-live value. Here is what each field means:

Field / Value	Meaning
`IPv6 Address`	The 128-bit address your domain resolves to, written as eight groups of four hexadecimal digits. Consecutive zero groups are compressed to :: which may appear only once per address.
`TTL`	Time to live in seconds. How long resolvers cache this record before querying again. 300 seconds suits frequently changing records; 3600 or higher suits stable ones.
`Multiple records`	More than one AAAA record means the domain is served from several IPv6 endpoints. Clients receive all of them and pick one, usually round-robin, giving basic load distribution and failover.
`No record found`	The domain has no IPv6 presence. Visitors on IPv6-only networks can reach you only through their provider NAT64 gateway, or not at all.
`2001:db8:: prefix`	This range is reserved for documentation only under RFC 3849. If it appears in a live record it is a configuration mistake and traffic will not route.

Common Problems & How to Fix Them

Your domain has no IPv6 address published, so it is unreachable directly over IPv6.

Ask your hosting provider or CDN for an IPv6 address, then add a DNS record:
Type: AAAA
Name: @ (or the subdomain label)
Value: your IPv6 address

Most major CDNs such as Cloudflare, Fastly and CloudFront provide IPv6 automatically once enabled in their dashboard.

The DNS record is published but the server is not actually listening on that address, or a firewall is blocking IPv6 traffic.

Confirm your web server binds to the IPv6 address — for nginx that means listen [::]:443 ssl; — and that your firewall has matching ip6tables or nftables rules. A published AAAA record pointing at a dead endpoint is worse than no record at all, because clients try IPv6 first and wait for a timeout.

IPv6 addresses are long and easy to mistype. Compare the published record against the server actual address, and remember that :: can appear only once in an address.

Lower the TTL to 300 seconds before any planned migration so corrections propagate quickly.

This is the classic symptom of a broken IPv6 path. Dual-stack clients try the AAAA address first, wait for a timeout, then fall back to IPv4 — adding seconds to the first connection.

Either fix the IPv6 route end to end or remove the AAAA record entirely until the path works.

Best Practices

Publish AAAA records alongside A records so every client can reach you natively
Verify the server actually listens on IPv6 before publishing the record
Use a TTL of 3600 seconds for stable records and 300 seconds during a migration
Keep IPv4 and IPv6 endpoints serving identical content and certificates
Test from a real IPv6-only network, not just a dual-stack connection
Ensure firewall rules cover IPv6 separately — IPv4 rules do not apply to it
Add AAAA records for mail servers too, not only the web host

Security Recommendations

Never publish an AAAA record for a host you have not firewalled for IPv6 — many servers ship with permissive IPv6 defaults
Audit ip6tables or nftables rules separately from IPv4; a locked-down IPv4 firewall says nothing about IPv6 exposure
Check that internal-only services are not accidentally reachable on their IPv6 address
Watch for AAAA records pointing at decommissioned addresses — reassigned IPv6 space can be claimed by someone else
Apply the same rate limiting and WAF rules to IPv6 traffic as you do to IPv4

Frequently Asked Questions

An AAAA record is a DNS record that maps a domain name to an IPv6 address. It works exactly like an A record but stores a 128-bit IPv6 address instead of a 32-bit IPv4 address. It is defined in RFC 3596.

An A record maps a domain to an IPv4 address such as 93.184.216.34. An AAAA record maps the same domain to an IPv6 address such as 2606:2800:220:1:248:1893:25c8:1946. Most domains publish both so that clients on either network can connect.

You do not strictly need one, but without it your site is unreachable directly from IPv6-only networks, which are increasingly common on mobile carriers. Those users reach you through a NAT64 translation gateway, which adds latency and can break some protocols. Publishing an AAAA record is recommended for any public-facing site.

Yes. Multiple AAAA records provide redundancy and basic round-robin load distribution. Clients receive all addresses and pick one, falling back to another if the first fails to connect.

This usually means the IPv6 path is broken. Dual-stack clients prefer IPv6, so they attempt the AAAA address first and only fall back to IPv4 after a timeout. Either fix the IPv6 connectivity or remove the AAAA record until it works.

Log in to your DNS provider, add a record of type AAAA, set the name to @ for the root domain or to the subdomain label, and paste your IPv6 address as the value. Confirm your server is actually listening on that address before publishing.

Propagation depends on the TTL of the previous record. Most resolvers pick up changes within the old TTL window, typically 5 minutes to an hour, though full worldwide propagation can take up to 48 hours.