DNSSEC Checker (DS, DNSKEY, RRSIG, AD flag)

Check whether a domain is DNSSEC signed and validating: see the DS records at the parent, the DNSKEY set, key tags, DS digest matches, RRSIG validity dates and the resolver AD flag, with plain explanations of algorithm numbers and digest types.

What the result means

What this tool checks (and what it doesn't)

It checks:

It doesn't verify RRSIG signatures cryptographically itself; for that it relies on Cloudflare's validation (the AD flag and SERVFAIL). It doesn't walk the chain above the parent zone, check NSEC or NSEC3 denial proofs, or query each authoritative name server separately, so a problem on only one of your name servers can be missed. Answers can come from Cloudflare's cache.

DNSSEC algorithm numbers

The number in DNSKEY, RRSIG and DS records names the signing algorithm. The signing and validation columns are the current recommendations in the IANA registry. RFC 9904 (November 2025) obsoleted RFC 8624 and moved these recommendations into the IANA registries.

NumberMnemonicAlgorithmUse for signingUse for validationNotes
0DELETEDelete DS––Only valid in CDS and CDNSKEY records, where it asks the parent to remove the DS records (RFC 8078). Not a signing algorithm.
1RSAMD5RSA/MD5 (deprecated)MUST NOTMUST NOT
3DSADSA/SHA1MUST NOTMUST NOT
5RSASHA1RSA/SHA-1MUST NOTRECOMMENDEDRFC 9905: MUST NOT be used for new DNSKEY, RRSIG or DS records. Validator software must still support it, but resolver operators must treat it as unsupported, so a zone signed only with it can be treated as insecure.
6DSA-NSEC3-SHA1DSA-NSEC3-SHA1MUST NOTMUST NOT
7RSASHA1-NSEC3-SHA1RSASHA1-NSEC3-SHA1MUST NOTRECOMMENDEDRFC 9905: MUST NOT be used for new DNSKEY, RRSIG or DS records. Validator software must still support it, but resolver operators must treat it as unsupported, so a zone signed only with it can be treated as insecure.
8RSASHA256RSA/SHA-256RECOMMENDEDRECOMMENDED
10RSASHA512RSA/SHA-512NOT RECOMMENDEDRECOMMENDED
12ECC-GOSTGOST R 34.10-2001 (deprecated)MUST NOTMUST NOTRetired by RFC 9906.
13ECDSAP256SHA256ECDSA Curve P-256 with SHA-256RECOMMENDEDRECOMMENDEDCloudflare calls algorithm 13 its preferred choice.
14ECDSAP384SHA384ECDSA Curve P-384 with SHA-384MAYRECOMMENDED
15ED25519Ed25519RECOMMENDEDRECOMMENDED
16ED448Ed448MAYRECOMMENDED
17SM2SM3SM2 signing algorithm with SM3 hashing algorithmMAYMAY
18MLDSA44ML-DSA-44MAYMAY
23ECC-GOST12GOST R 34.10-2012MAYMAY
253PRIVATEDNSprivate algorithmMAYMAY
254PRIVATEOIDprivate algorithm OIDMAYMAY

Numbers 4, 9, 11, 123–251 and 255 are reserved; 2 (Diffie-Hellman) and 252 (indirect keys) are not used for zone signing; 19–22 and 24–122 are unassigned.

DS digest types

The digest type in a DS record says which hash of the child's DNSKEY it holds. RFC 6840 section 5.2 says validators ignore DS records with digest types they don't support, the same way they ignore unsupported algorithms.

NumberDigestUse for DS recordsUse for validationNotes
0ReservedMUST NOTMUST NOT
1SHA-1MUST NOTRECOMMENDEDRFC 9905 updated this entry: MUST NOT be used when creating DS records.
2SHA-256RECOMMENDEDRECOMMENDED
3GOST R 34.11-94 (deprecated)MUST NOTMUST NOTRetired by RFC 9906.
4SHA-384MAYRECOMMENDED
5GOST R 34.11-2012MAYMAY
6SM3MAYMAY

DNSKEY flags: 256 means the zone key bit is set; 257 means zone key plus the Secure Entry Point (SEP) bit, which DNS hosts such as Cloudflare use for the key signing key (KSK) that the DS record points to. RFC 4034 says validators must not treat the SEP bit differently; it is only a hint.

How to use it

  1. Enter a domain and click Check DNSSEC. The page sends DS, DNSKEY and SOA queries from your browser to Cloudflare DNS-over-HTTPS with the DNSSEC OK (do=1) flag.
  2. Read the result line first, then the DS table: each DS should say digest MATCHES DNSKEY for at least one key. A DS with NO DNSKEY with this key tag usually means the registrar still has the DS for an old key or an old DNS host.
  3. If the result is BROKEN, either add the DS for your current DNS host's key at your registrar, or remove the DS there to turn DNSSEC off, then wait for the DS TTL to expire and check again.

Related guides

Related tools and guides

Read why a domain returns SERVFAIL after a DNS host or registrar change in Fix DNSSEC SERVFAIL (broken chain of trust), and set up inbound SMTP DANE with DNSSEC for Microsoft 365 with DNSSEC and SMTP DANE in Exchange Online. Look up any other record type with DNS Lookup, compare resolvers with the DNS Propagation Checker and check mail records with the MX Record Lookup and MTA-STS Checker.

FAQ

What does the AD flag mean?

AD stands for Authenticated Data. A validating resolver sets it only when it considers every record in the answer authentic (RFC 4035 section 3.2.3), and RFC 6840 says it should only set it when the query asked for DNSSEC data or the AD bit. This tool asks Cloudflare with the DNSSEC OK flag, so AD=1 means Cloudflare validated the answer.

Why does my domain return SERVFAIL only on some resolvers?

Validating resolvers such as Cloudflare's 1.1.1.1 return SERVFAIL when DNSSEC validation fails, while resolvers that do not validate still return the records. If a query works with checking disabled (dig +cd) but fails without it, DNSSEC is misconfigured, most often because the DS at the registrar no longer matches the keys of the current DNS host.

What is the difference between DS and DNSKEY?

DNSKEY records hold the zone's public keys and are published by your DNS host in your zone. The DS record is a hash of one of those keys and is published in the parent zone (for example .com) through your registrar. The DS is what links your zone into the chain of trust.

Does this tool verify the RRSIG signatures?

Not by itself. It recomputes DS digests in your browser and checks RRSIG dates and key tags, but the cryptographic signature checks are done by Cloudflare's validating resolver, which this tool reports through the AD flag and SERVFAIL responses.

Is SHA-1 or algorithm 5 still OK?

No, plan to move off it. RFC 9905 says RSASHA1 (5) and RSASHA1-NSEC3-SHA1 (7) must not be used for new DNSKEY, RRSIG or DS records, and that operators of validating resolvers must treat them as unsupported, which can make a zone signed only with them insecure. The IANA registry lists algorithms 8 (RSASHA256), 13 (ECDSAP256SHA256) and 15 (ED25519) and DS digest type 2 (SHA-256) as RECOMMENDED.

Want the full kit?

Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.