What this check looks at
DNSSEC adds signatures to DNS answers, so a resolver can check that an answer came from your nameservers and wasn't changed on the way. It only works when every link holds: the registry publishes a DS record for your domain, that record matches a key your nameservers serve, that key signs the zone's keys, and fresh signatures cover your records. One broken link and validating resolvers reject your whole domain.
The same check also tests the nameservers themselves, because DNSSEC problems and nameserver problems look alike from the outside: some visitors can't reach the site, others can. We ask your registry which nameservers it has on file, ask each of those servers directly, and compare what every one of them says.
How the check works
We start where every resolver starts: with your registry. One of the parent zone's own servers tells us which nameservers are listed for your domain, the glue addresses if any, and the DS records. We ask our validating resolver for its verdict at the same time, which is what most of your visitors' resolvers will see.
Then we probe every nameserver address in parallel. Each one gets the same questions over UDP and over TCP: the zone's SOA record with its serial and signature, its NS records, its DNSSEC keys, and a lookup for a name outside your zone to see whether it answers recursive questions for anyone. Results show up row by row as each server answers, so a slow server never holds up the rest.
Finally we put it together. We recompute each DS digest and check it against the served keys, verify every signature we collected with real cryptography, compare the key sets and serials across servers, and read how the zone proves that a name doesn't exist (NSEC, NSEC3 or compact denial). Signatures are judged against the current time, so an expired signature or one that only starts tomorrow is reported as such.
Reading the result
The verdict at the top comes from our validating resolver: signed and valid, not signed, failing validation, or undetermined when it gave no answer. Below it, three panels show the details.
The delegation panel lists the nameservers your registry has on file next to the ones your zone lists in its own NS records. They should be the same set. It also shows the chain of trust from the top-level domain down to yours, link by link.
The nameserver table has one row per server: whether it answers authoritatively, its addresses, the serial it serves, and whether UDP and TCP both work. A server that answers for other domains as well is flagged, because open resolvers are abused in attacks.
The DNSSEC panel lists the DS records and whether each matches a served key, the keys themselves with their role and size, every signature with its expiry date and state, and the denial method.
Every problem comes with a finding that says what's wrong in plain words, and most link to a step-by-step guide. The most common ones after a change of DNS provider are a DS record that no longer matches any key, and nameservers at the registrar that differ from the ones in the zone.
When to run it
Run it after any change to your nameservers or to DNSSEC, before and after moving DNS providers, and whenever a domain fails to resolve for some people but not for others. If you're about to switch providers, the migration checker compares your records at the old and new nameservers first, including whether the switch would break DNSSEC.
What we don't do
We don't try zone transfers, which would hand anyone a copy of your whole zone. IPv6 addresses are probed only while our IPv6 connection is on; otherwise they are listed and marked as not checked. Queries to each registry and nameserver are rate limited, so a check is never a burden on anyone's servers.