Fail

Your domain fails DNSSEC validation

The short version

Make the DS record at your registrar match the key your DNS provider signs with now, or remove the DS record if you turned DNSSEC off.

What it means

Validating resolvers reject your zone: the chain of trust from the root breaks somewhere between the DS record at your registry and the signatures on your records. The check lists the exact reason, and the resolver's own explanation when it gave one.

Why it matters

Most public resolvers check DNSSEC, so for a large share of visitors your domain looks offline. Websites fail to load and mail stops arriving, while everything still works on networks that don't validate, which makes the problem confusing to track down.

How to fix it

  1. Read the other DNSSEC findings in this result: they say whether the DS record, the keys or the signatures are at fault.
  2. If you moved DNS providers or turned DNSSEC off, delete the DS record at your registrar. That makes the zone unsigned but working.
  3. If DNSSEC should stay on, replace the DS record at the registrar with the one your DNS provider shows now.
  4. If signatures expired, ask your DNS provider to re-sign the zone, or restart your signing process.

Cloudflare

Under DNS settings, the DNSSEC panel shows the DS record (key tag, algorithm, digest type and digest) to add at your registrar. Cloudflare Registrar updates it for you.

Check it worked

Run the check again. Resolvers can keep the old DS record for its TTL, often a day, so allow that long before every network sees the fix.