Free DNSSEC Checker

Enter a domain to read its DS record at the registry and its DNSKEY set, match one to the other, and ask a validating resolver whether the chain holds.

Parts checked
DS · DNSKEY · Validation

Following the chain...

What a DNSSEC Checker Tells You

DNSSEC signs a zone's records so a resolver can prove an answer came from the zone and was not altered. The proof runs as a chain: the parent zone publishes a DS record naming your key, and your zone publishes the DNSKEY it names.

This DNSSEC checker reads both halves, matches the DS to a key by key tag and algorithm, and asks a public validating resolver whether it accepts the zone. The signatures themselves are checked by that resolver, and we report what it says. To see who answers for the zone, use the nameserver lookup.

How to test DNSSEC
  1. Enter the domain, without "www".
  2. We read the DS set from the parent zone and the DNSKEY set from the zone.
  3. We match each DS to a key by key tag and algorithm.
  4. We ask a validating resolver for the zone's SOA and read whether it authenticated the answer.

What this check settles

  • Whether the domain is signed: no DS at the registry means resolvers treat the zone as unsigned, whatever the zone publishes.
  • Whether the chain matches: a DS that names no published key breaks resolution for every validating resolver.
  • Whether resolvers accept it: a validating resolver either authenticates the answer or refuses to return it.

DNSSEC Validation States Explained

A validating resolver puts every answer in one of three states, and only one of them breaks resolution.

State Resolver does What it means Effect
Secure Answers, AD flag set An unbroken chain of signatures from the root to the answer. Protected
Insecure Answers, no AD flag The parent proves the zone is not signed, so there is nothing to check. Unprotected
Bogus Returns SERVFAIL The chain should validate and does not. The resolver withholds the answer. Unreachable

How to Read the Result

The verdict comes first, then the chain from the parent down.

The verdict

The headline

Signed and valid, not signed, or signed but broken, with the reason it is broken.

DS records

The anchor

Published by the registry for your zone. Each names a key by key tag and algorithm, with a digest of it.

DNSKEY records

The keys

The keys your zone publishes, each marked as a key signing or zone signing key, with its key tag and whether a DS names it.

Whether a public validating resolver authenticated the zone's answer, its response code, and any extended error it gave.

What Is DNSSEC?

DNSSEC, the DNS Security Extensions, adds signatures to DNS records so resolvers can check that an answer is genuine. Each zone signs its own records, and its parent vouches for its key with a DS record, forming a chain of trust that starts at the root.

How the DNSSEC Chain Works

A resolver starts from the root key it already trusts and works down one zone at a time.

For each zone:

  • The parent publishes a DS record holding a digest of the child's key signing key.
  • The child publishes its DNSKEY set, signed by that key signing key.
  • The zone signing key in that set signs every other record in the zone.
  • A break at any step makes every name below it fail validation.

How Do I Test if DNSSEC Is Working?

Check three things: that the parent zone publishes a DS record, that the DS names a DNSKEY your zone actually publishes, and that a validating resolver sets the AD flag on an answer from the zone. This DNSSEC test runs all three and reports the first one that fails.

How Do I Enable DNSSEC?

Turn on signing at your DNS host, which creates the keys and signs the zone. Then copy the DS record it gives you into your registrar's DNSSEC settings, or let the registrar fetch it if your DNS host and registrar support that. Check here once the DS appears.

Where DNSSEC Goes Wrong

Almost every outage comes from the two halves of the chain changing at different times:

  • Moving to a new DNS host and leaving the old DS at the registrar, so it names a key that no longer exists.
  • Turning off signing at the DNS host before removing the DS, which leaves a DS with no DNSKEY.
  • Rolling the key signing key and updating the DS before the new key is published.
  • Signatures that expire because the zone stopped being re-signed.
  • Assuming the zone is protected because it is signed, when no DS was ever added at the registrar.

Why Test DNSSEC

01

Avoid a silent outage

A broken chain makes your domain unreachable for users of validating resolvers, while it still works for everyone else.

02

Stop forged answers

A signed zone lets resolvers reject a forged record instead of caching it and sending users to the wrong place.

03

Plan a DNS move

Check the DS before and after changing DNS host, the moment the chain most often breaks.

04

Enable DANE

DANE publishes certificate details in DNS for mail servers, and it only works on a signed zone.

Who Tests DNSSEC

The same read answers a different question depending on who runs it.

DNS Admins

Confirm the chain after a key roll or a move to a new DNS host.

For DNS monitoring

Security Teams

Check which domains are signed and which only appear to be.

For brand protection

Compliance Leads

Record DNSSEC status for an audit or a security questionnaire.

For enterprise

Agencies

Catch a stale DS when taking over a client's DNS, before it takes the site down.

For agencies

Related DNS Tools

DNSSEC depends on the delegation above it. These check the rest of it.

01

Check the nameservers

See who answers for the zone and whether each server responds.

Nameserver lookup
02

Check propagation

Compare answers across public resolvers after a DNS change.

DNS propagation checker
03

Check the registration

The registry record shows whether the delegation is signed.

WHOIS lookup
04

Detect DNS changes

Get an alert when your nameservers or records change.

DNS change detection
Start Today

Start Monitoring & Catching Domains Today

Join founders, agencies, and domainers already protecting their portfolio. Your first 3 domains are free.

Create Free Account

No credit card required • Cancel anytime

Frequently Asked Questions

Common questions about DNSSEC and how to test it.

What does a DNSSEC checker do?

It reads the DS record at the parent zone and the DNSKEY records in your zone, checks that the DS names one of your keys, and asks a validating resolver whether it accepts the zone. Together these show whether DNSSEC is on and whether it works.

How do I check if DNSSEC is enabled?

Enter your domain above. If there is no DS record at the parent, DNSSEC is not enabled, even if your DNS host has signed the zone. If there is a DS and the resolver authenticates the answer, it is enabled and working.

What is a DS record?

A Delegation Signer record, published in the parent zone by your registry. It holds a digest of your zone's key signing key, so resolvers can trust that key. You add it through your registrar.

What is the difference between a KSK and a ZSK?

The key signing key, flag 257, signs only the DNSKEY set and is the key the DS points to. The zone signing key, flag 256, signs every other record. Some zones use one key for both roles.

What does the AD flag mean?

Authenticated Data. A validating resolver sets it on an answer it has verified through an unbroken chain of signatures. No AD flag on a normal answer means the zone is unsigned or the chain above it is.

What happens if DNSSEC is broken?

Validating resolvers return SERVFAIL instead of an answer, so your site and mail stop working for their users. Resolvers that do not validate keep answering, which is why a broken chain can go unnoticed for a while.

Why does my DS record not match?

The DS at the registrar names a key your zone no longer publishes. This usually follows a change of DNS host or a key rollover. Replace the DS with the one your current DNS host gives you.

Does this tool validate the signatures itself?

No. It matches DS to DNSKEY by key tag and algorithm, and relies on a public validating resolver to check the signatures. It reports that resolver's verdict, its response code and any extended error it returns.

Should every domain use DNSSEC?

It protects against forged DNS answers and is required for DANE, but it adds a step to every DNS host change. If you enable it, test it after each change to your DNS host or keys.

How long does a DS change take to apply?

The registry publishes it after your registrar submits it, and resolvers keep the old DS until its TTL expires. Leave the old key published until then, or validating resolvers may fail in the meantime.

Your first 3 domains are monitored free

No credit card. Upgrade or cancel any time.

Start free