The domain has no IPv6 address
What this check looks for
The domain is reachable over IPv4 only. Everything works today, but visitors on IPv6-only mobile networks reach you through their carrier's translation layer rather than directly.
Why it matters
A growing share of mobile traffic is IPv6-only and reaches IPv4 sites through carrier-grade NAT64. That adds latency, hides the visitor's real address from your logs, and puts a third party in the path of every connection.
When the check passes, your report says: “The domain is reachable over IPv6 as well as IPv4”.
What it costs your score
This check never deducts. It reports a fact — or reports that something could not be verified — and is shown on the report without moving the score.
- Severity
- info
- Default confidence
- confirmed
- Status when triggered
- info
- Deduction
- 0 points
- Family cap
- none
- Category
- DNS
- Module
- Dns records
- Fix owned by
- dns host
- In the ruleset since
- 2026.09
How to fix it
Add an AAAA record once your host answers on IPv6.
Direct IPv6 removes the carrier translation layer for a large share of mobile visitors.
Check whether your hosting platform has assigned an IPv6 address to the service.
Confirm the service is listening on it before publishing anything.
Add the AAAA record alongside the existing A record; both are used.
How to confirm it worked
dig +short AAAA ‹domain› — expect the address you published
{{domain}}. 3600 IN AAAA {{ipv6}}A named slot like ‹domain› — and the braces left in the configuration below — is filled in with your own values when this rule appears on a report.
Technical detail
No AAAA record was found at ‹domain›. This is reported for information: an IPv4-only domain is reachable by everyone today and adding IPv6 is a deliberate choice, not a repair. It deducts nothing from the score. Add an AAAA record only when the server or platform behind the name actually answers on IPv6 — publishing one that does not is worse than publishing none, because clients try it first.
Standards and references
- RFC 1035 §3.4.1 — A RDATA format § 3.4.1
Test this on your domain
Run the check that produces this finding, on its own, against any domain.
Other dns records checks
- The domain apex is a CNAME, which the DNS does not allow
- A CAA record marked critical uses a tag no authority understands
- CAA forbids every authority from issuing a certificate
- The CAA reporting address is not a usable URL
- No CAA record says which authorities may issue certificates
- Two TXT records of the same kind are published at one name
- The domain has no A or AAAA record
- Records are published with a very long TTL
- Records are published with a very short TTL
- A TXT record looks cut off at the 255-character limit
- A wildcard record answers for every subdomain