A hostname should resolve over IPv6 and you need to confirm the live AAAA answer.
AAAA Record Lookup
Check live IPv6 AAAA records for a domain or hostname.
Use AAAA Record Lookup to inspect the public IPv6 addresses currently returned for a hostname, compare them with the values you expected to publish, and decide what to check next if the answer looks wrong.
Check AAAA records before moving to propagation, nameserver, or IPv6 service troubleshooting.
Lookup result
example.com
NOERROR
Type Value TTL
No AAAA records were returned for this hostname by the resolver.
What this AAAA Record Lookup tool does
AAAA Record Lookup queries the public AAAA records for a domain or hostname and returns the IPv6 answers currently visible from the resolver used by this page.
Use it to confirm whether a hostname resolves over IPv6, inspect the returned addresses, and compare the live answer with the configuration you intended to publish.
It does not confirm whether the website or service behind that IPv6 address is healthy. It only confirms the DNS AAAA-record layer.
When to use this tool
A dual-stack site works on IPv4 but fails for IPv6 users and you want to inspect the published AAAA record first.
A recent IPv6 DNS change was made and you need to see whether public resolvers are returning the new address.
A hostname is expected to be IPv6-enabled, but clients are not connecting the way you expected.
You need to compare the public AAAA answer against the IPv6 address configured in DNS.
You want a focused IPv6 lookup before moving to propagation, nameserver, or service-level checks.
How to use AAAA Record Lookup
- Enter the domain or hostname you want to check.
- Run the lookup to request public IPv6 AAAA answers from a recursive resolver.
- Review the returned IPv6 address or addresses, TTL, and response status.
- Compare the live result with the AAAA record you expected to publish.
- If the result is wrong or missing, continue to nameserver, propagation, or service checks.
How to interpret AAAA record results
AAAA record found
Likely meaning: Public DNS returned one or more IPv6 addresses for the hostname.
Common causes: This usually means the hostname resolves publicly over IPv6 from the resolver used by this page.
Next action: Compare the returned IPv6 address or addresses with the values you intended to publish.
No AAAA record found
Likely meaning: The hostname exists, but no IPv6 AAAA record was returned.
Common causes: The host may only have A or CNAME data, IPv6 may not be enabled yet, or the record may be missing from the published zone.
Next action: Check DNS Lookup for other record types, then verify nameservers and propagation.
Unexpected IPv6 address
Likely meaning: The lookup returned IPv6 addresses, but not the ones you expected.
Common causes: Common causes are stale DNS, edits in the wrong provider, partial migration, proxy edge addresses, or old records left behind.
Next action: Compare the live answer with your DNS provider configuration, then check propagation and proxy behavior.
Multiple AAAA records returned
Likely meaning: More than one IPv6 address exists for the same hostname.
Common causes: This can be valid for load balancing, failover, or proxy behavior, but it can also show stale or conflicting IPv6 data.
Next action: Confirm whether multiple public IPv6 answers are expected. If not, remove outdated or conflicting records.
NXDOMAIN
Likely meaning: The queried hostname does not exist in public DNS.
Common causes: Typos, missing subdomains, unpublished records, or the wrong zone are common causes.
Next action: Verify the exact hostname, then check nameservers and the zone where the record was created.
SERVFAIL
Likely meaning: The recursive resolver could not complete the lookup successfully.
Common causes: This often points to DNSSEC failure, broken delegation, or upstream nameserver issues.
Next action: Run NS Lookup and DNSSEC Check next, then compare with propagation results.
Common DNS issues this tool helps uncover
AAAA record published in the wrong DNS provider or wrong zone
Public DNS still returning an old IPv6 address after a migration
The hostname is dual-stack in theory but only IPv4 is actually published
Proxy or edge addresses are being returned instead of the expected IPv6 target
Nameserver delegation mismatch after DNS changes
Resolver differences during propagation or caching windows
Split-horizon DNS where internal and public IPv6 answers differ
Next steps after AAAA Record Lookup
Check DNS propagation
If you changed the AAAA record recently, compare how recursive resolvers are seeing it.
Verify nameservers
Use NS Lookup if the live AAAA record looks wrong and you need to confirm which provider is authoritative.
Inspect other DNS records
If no AAAA record appears, check for A, CNAME, or other related DNS answers.
Move to service checks
If the AAAA record looks correct, continue to Ping, HTTP Check, or HTTPS Check.
Related tools
DNS Lookup
Query A, AAAA, CNAME, TXT, and other DNS records for a domain.
DNS Propagation Check
Verify whether recent DNS changes are visible across resolvers.
NS Lookup
Check authoritative name servers and delegation for a domain.
Ping
Check whether a host responds and measure round-trip latency.
HTTP Check
Review HTTP response status, headers, and redirect behavior.
HTTPS Check
Verify HTTPS availability, response chain, and TLS handshake basics.
AAAA Record Lookup FAQ
What does AAAA Record Lookup check?
It checks the live public AAAA records for a domain or hostname and returns the IPv6 answers currently visible from the resolver used by the page.
What input should I enter?
Enter a domain or hostname such as example.com, app.example.com, or www.example.com. Do not enter a full URL.
Why is there no AAAA record even though the site works?
The site may only be published over IPv4, may be using a CNAME without direct IPv6 answers at that label, or IPv6 may not be enabled on the public DNS record.
Why are multiple AAAA records returned?
Multiple AAAA records can be normal for load balancing, failover, or proxy networks, but they can also indicate stale or duplicated IPv6 records.
What should I check after AAAA Record Lookup?
Usually DNS propagation, nameservers, and then service-level checks like Ping, HTTP Check, or HTTPS Check.
How is AAAA Record Lookup different from DNS Lookup?
AAAA Record Lookup is focused only on IPv6 AAAA answers. DNS Lookup is broader and can inspect A, AAAA, MX, TXT, NS, CNAME, and other record types.