DNSSEC Validation Check
See whether a domain publishes DNSSEC keys and whether the resolver could authenticate its answers.
What it checks
- Requests DS, DNSKEY and A records through Cloudflare's resolver with DNSSEC data requested
- Marks the zone as signed only if it publishes both DS and DNSKEY records
- Reads the AD (authenticated data) flag on the A answer as the validation result
- Lists the DS key tag, algorithm and digest, and the DNSKEY flags and algorithm
How to read the result
- Signed and authenticated is the healthy state. Signed but not authenticated points to a validation problem, and the tool warns of a possible chain break.
- Unsigned means the zone publishes no DNSSEC keys, so resolvers cannot validate its answers.
- An authenticated result reflects Cloudflare's validation at the time of the check. It is not an independent walk of the chain from the root.
What it does not tell you
The tool does not validate signatures itself and does not check key rollover or NSEC and NSEC3 denial of existence. Its result depends on one resolver's AD flag. This is not a penetration test.
Data sources
DS, DNSKEY and A records are requested over DNS-over-HTTPS from Cloudflare's resolver with the DNSSEC OK bit set; the AD flag in the response is the validation result.
No login · 30 calls / hour / IP · Data stored in the EU
FAQ
What should I do if the tool warns of a chain break?
Compare the DS record at your registrar with the DNSKEY your DNS host publishes. A DS record that does not match the published DNSKEY is one possible cause. Your DNS provider can confirm the signing status.
Why might another validator give a different result?
Other validators use other resolvers and may check at a different time. Each lookup here is a single snapshot.
Go deeper: Email Security engine (includes DNSSEC checks for mail domains)