DNS Check
Delegation and zone health for a domain: what the parent zone says, and what every nameserver answers when asked directly.
Scope Each nameserver was asked directly, once, from one network location. A nameserver reached through anycast can answer differently from elsewhere; to compare resolvers around the world, use DNS Propagation Check.
What this checks
A domain works only if two sets of servers agree. The parent zone (for example the .com registry)
holds a list of the domain's nameservers, and those nameservers hold the domain's actual records. When the two
lists drift apart, or one nameserver falls behind the others, some visitors get stale or failed answers while
others see nothing wrong.
DNS Check reads the delegation from the parent zone's own servers, then asks every nameserver address the same
questions over both UDP and TCP and compares the answers. It reports nameservers that do not respond or are not
authoritative, NS and SOA records that disagree, open recursion, and mail and www records that
point somewhere unusable. A public resolver cannot show any of this, because it returns one cached answer from
whichever nameserver it happened to ask. DNSSEC and CAA records are checked by
Security Headers Check.
For registration, certificate, and email-authentication checks on the same domain, run Domain Check.