Skip to content
LookupOwl

DNSSEC visualizer

Draw a domain's chain of trust as a graph of zones, keys and signatures, with the broken link marked.

A domain, or any name inside it. We find the zone for you.

Results for dnssec-failed.org

Checked live lookup1529 ms

JSONCheck again

DNSSEC: Broken

The chain breaks at dnssec-failed.org.

The DS record at org (tag 42069) matches none of the keys the zone publishes. Resolvers that validate (Google, Cloudflare, Quad9) are refusing this name now.

Resolvers refuse this name
Resolvers that validate
0of 3

All 3 answer SERVFAIL

DS 42069 at org points at a key dnssec-failed.org does not have. Everything after it is not checked.

How to fix it

Replace the DS

Give your registrar the DS for the key the zone uses now (KSK 50719):

Adddnssec-failed.org. 3600 IN DS 50719 13 2 D602C971A02AF89B7661B99D6DD1B9E2EC876617631D04F633902A42CD4D6BBD
Turned DNSSEC off?

Remove the DS at your registrar. The name works again, unsigned, once the DS has expired from caches.

Re-sign

If KSK 42069 still exists in your signer, publish it and sign the key set with it again.

Chain of trust, 4 steps

  1. Root.Trust anchor

    The IANA root key (KSK 20326) is where every chain starts.

    •  KSK 20326 · RSA/SHA-256
    •  KSK 38696 · RSA/SHA-256
    •  ZSK 8763 · RSA/SHA-256

    Two root KSKs are published during the planned root key rollover. That is normal.

    ZSK 8763 signs the DS for org.

    Valid for 13 days in total, 12 days left
  2. Top-level domainorgPass
    •  KSK 725 · RSA/SHA-256
    •  KSK 26974 · RSA/SHA-256
    •  ZSK 11859 · RSA/SHA-256
    •  ZSK 25488 · RSA/SHA-256

    ZSK 11859 signs the DS for dnssec-failed.org.

    Valid for 21 days in total, 16 days left
  3. Your zonednssec-failed.orgBroken here
    •  KSK 50719 · ECDSA P-256
    •  ZSK 32784 · ECDSA P-256

    The keys the zone does publish are listed above. The DS points at none of them.

  4. AnswerSOA dnssec-failed.orgNot checked

    Not checked: the chain broke above.

What public resolvers say

Our finding: no key matches the DS record. Resolvers report the same failure in different words. Ours comes from checking the keys.

ResolverAnswerValidated (AD)Their reason
Cloudflare 1.1.1.1SERVFAILNoEDE 9: no SEP matching the DS found for dnssec-failed.org.
Google 8.8.8.8SERVFAILNoEDE 9: No DNSKEY matches DS RRs of dnssec-failed.org
Quad9 9.9.9.9SERVFAILNoEDE 6: DNSSEC Bogus

With checking switched off (the CD bit) the answer comes back: the data is there, the chain is what fails.

  • Look up the DS and DNSKEY recordsSee the raw records the chain uses.
    DS lookup
  • Open the checkerThe steps and the issues for dnssec-failed.org, first.
    Checker
  • Has the DS change reached everyone?DNS propagation, type DS.
    Propagation
  • What does the registry hold?WHOIS shows the DS data from RDAP.
    WHOIS
  • Copy the graph dataNodes and edges as JSON.
Structured result (JSON) · 8.5 KB
{
  "name": "dnssec-failed.org",
  "zone": "dnssec-failed.org",
  "type": "SOA",
  "mode": "live",
  "verdict": "bogus",
  "state": "ds-no-match",
  "verdictText": "The chain breaks at dnssec-failed.org.",
  "explain": "The DS record at org (tag 42069) matches none of the keys the zone publishes. Resolvers that validate (Google, Cloudflare, Quad9) are refusing this name now.",
  "anchor": {
    "kind": "iana-root",
    "keyTag": 20326,
    "algorithm": 8
  },
  "chain": [
    {
      "zone": ".",
      "role": "root",
      "status": "ok",
      "keys": [
        {
          "tag": 20326,
          "flags": 257,
          "role": "ksk",
          "algorithm": 8,
          "bits": 2048,
          "anchor": true
        },
        {
          "tag": 38696,
          "flags": 257,
          "role": "ksk",
          "algorithm": 8,
          "bits": 2048,
          "anchor": true
        },
        {
          "tag": 8763,
          "flags": 256,
          "role": "zsk",
          "algorithm": 8,
          "bits": 2048
        }
      ],
      "dnskeySig": {
        "by": 38696,
        "valid": true,
        "expires": "2026-12-01T00:00Z",
        "lifetimeDays": 21,
        "lifetimeHours": 504,
        "leftHours": 340.3
      },
      "link": null,
      "servers": []
    },
    {
      "zone": "org",
      "role": "tld",
      "status": "ok",
      "keys": [
        {
          "tag": 725,
          "flags": 257,
          "role": "ksk",
          "algorithm": 8,
          "bits": 2048,
          "anchor": true
        },
        {
          "tag": 26974,
          "flags": 257,
          "role": "ksk",
          "algorithm": 8,
          "bits": 2048
        },
        {
          "tag": 11859,
          "flags": 256,
          "role": "zsk",
          "algorithm": 8,
          "bits": 1024
        },
        {
          "tag": 25488,
          "flags": 256,
          "role": "zsk",
          "algorithm": 8,
          "bits": 1024
        }
      ],
      "dnskeySig": {
        "by": 725,
        "valid": true,
        "expires": "2026-11-30T17:09Z",
        "lifetimeDays": 21,
        "lifetimeHours": 506,
        "leftHours": 333.5
      },
      "link": {
        "status": "ok",
        "word": "Holds",
        "text": "DS 725 · RSA/SHA-256 · SHA-256 · matches KSK 725",
        "ds": [
          {
            "tag": 725,
            "algorithm": 8,
            "digestType": 2,
            "matches": 725
          }
        ],
        "signedBy": 8763,
        "expires": "2026-11-29T17:00Z",
        "lifetimeHours": 313,
        "leftHours": 309.3
      },
      "servers": []
    },
    {
      "zone": "dnssec-failed.org",
      "role": "zone",
      "status": "broken",
      "keys": [
        {
          "tag": 50719,
          "flags": 257,
          "role": "ksk",
          "algorithm": 13,
          "bits": 256
        },
        {
          "tag": 32784,
          "flags": 256,
          "role": "zsk",
          "algorithm": 13,
          "bits": 256
        }
      ],
      "dnskeySig": null,
      "link": {
        "status": "broken",
        "word": "No key matches this DS",
        "text": "DS 42069 · ECDSA P-256 · SHA-256 · no key has tag 42069",
        "ds": [
          {
            "tag": 42069,
            "algorithm": 13,
            "digestType": 2,
            "matches": null
          }
        ],
        "signedBy": 11859,
        "expires": "2026-12-03T00:23Z",
        "lifetimeHours": 506,
        "leftHours": 388.7
      },
      "servers": []
    }
  ],
  "denial": null,
  "issues": [
    {
      "id": "ds-no-match",
      "level": "fail",
      "step": 2,
      "evidence": "None of the DNSKEY records of dnssec-failed.org matches a DS record published by the parent.",
      "rfc": "RFC 4035 5",
      "fix": "Replace the DS at your registrar with the one for the key the zone uses now: dnssec-failed.org. 3600 IN DS 50719 13 2 D602C971A02AF89B7661B99D6DD1B9E2EC876617631D04F633902A42CD4D6BBD"
    }
  ],
  "extras": {
    "cds": false,
    "cdnskey": false,
    "nsec3param": null,
    "walkable": false,
    "suggestedDs": "dnssec-failed.org. 3600 IN DS 50719 13 2 D602C971A02AF89B7661B99D6DD1B9E2EC876617631D04F633902A42CD4D6BBD"
  },
  "rdap": {
    "dsData": [
      {
        "tag": 42069
      }
    ],
    "matchesZone": true
  },
  "resolvers": [
    {
      "name": "Cloudflare 1.1.1.1",
      "ip": "1.1.1.1",
      "ad": false,
      "rcode": "SERVFAIL",
      "ede": "EDE 9: no SEP matching the DS found for dnssec-failed.org.",
      "cdRcode": "NOERROR"
    },
    {
      "name": "Google 8.8.8.8",
      "ip": "8.8.8.8",
      "ad": false,
      "rcode": "SERVFAIL",
      "ede": "EDE 9: No DNSKEY matches DS RRs of dnssec-failed.org",
      "cdRcode": "NOERROR"
    },
    {
      "name": "Quad9 9.9.9.9",
      "ip": "9.9.9.9",
      "ad": false,
      "rcode": "SERVFAIL",
      "ede": "EDE 6: DNSSEC Bogus",
      "cdRcode": "NOERROR"
    }
  ],
  "graph": {
    "nodes": [
      {
        "id": "z0-ksk-20326",
        "kind": "ksk",
        "zone": ".",
        "label": "KSK 20326",
        "tag": 20326,
        "status": "ok",
        "row": 0,
        "zoneIndex": 0
      },
      {
        "id": "z0-ksk-38696",
        "kind": "ksk",
        "zone": ".",
        "label": "KSK 38696",
        "tag": 38696,
        "status": "ok",
        "row": 1,
        "zoneIndex": 0
      },
      {
        "id": "z0-zsk-8763",
        "kind": "zsk",
        "zone": ".",
        "label": "ZSK 8763",
        "tag": 8763,
        "status": "ok",
        "row": 2,
        "zoneIndex": 0
      },
      {
        "id": "z1-ds-725",
        "kind": "ds",
        "zone": "org",
        "label": "DS 725",
        "tag": 725,
        "status": "ok",
        "row": 0,
        "zoneIndex": 1
      },
      {
        "id": "z1-ksk-725",
        "kind": "ksk",
        "zone": "org",
        "label": "KSK 725",
        "tag": 725,
        "status": "ok",
        "row": 1,
        "zoneIndex": 1
      },
      {
        "id": "z1-ksk-26974",
        "kind": "ksk",
        "zone": "org",
        "label": "KSK 26974",
        "tag": 26974,
        "status": "ok",
        "row": 2,
        "zoneIndex": 1
      },
      {
        "id": "z1-zsk-11859",
        "kind": "zsk",
        "zone": "org",
        "label": "ZSK 11859",
        "tag": 11859,
        "status": "ok",
        "row": 3,
        "zoneIndex": 1
      },
      {
        "id": "z1-zsk-25488",
        "kind": "zsk",
        "zone": "org",
        "label": "ZSK 25488",
        "tag": 25488,
        "status": "ok",
        "row": 4,
        "zoneIndex": 1
      },
      {
        "id": "z2-ds-42069",
        "kind": "ds",
        "zone": "dnssec-failed.org",
        "label": "DS 42069",
        "tag": 42069,
        "status": "broken",
        "row": 0,
        "zoneIndex": 2
      },
      {
        "id": "z2-ksk-50719",
        "kind": "ksk",
        "zone": "dnssec-failed.org",
        "label": "KSK 50719",
        "tag": 50719,
        "status": "skipped",
        "row": 1,
        "zoneIndex": 2
      },
      {
        "id": "z2-zsk-32784",
        "kind": "zsk",
        "zone": "dnssec-failed.org",
        "label": "ZSK 32784",
        "tag": 32784,
        "status": "skipped",
        "row": 2,
        "zoneIndex": 2
      },
      {
        "id": "z2-rr-SOA",
        "kind": "rr",
        "zone": "dnssec-failed.org",
        "label": "SOA",
        "status": "skipped",
        "row": 3,
        "zoneIndex": 2
      }
    ],
    "edges": [
      {
        "from": "z0-ksk-20326",
        "to": "z0-zsk-8763",
        "kind": "signs",
        "status": "ok"
      },
      {
        "from": "z1-ds-725",
        "to": "z1-ksk-725",
        "kind": "digest",
        "status": "ok"
      },
      {
        "from": "z1-ksk-725",
        "to": "z1-zsk-11859",
        "kind": "signs",
        "status": "ok"
      },
      {
        "from": "z1-ksk-725",
        "to": "z1-zsk-25488",
        "kind": "signs",
        "status": "ok"
      },
      {
        "from": "z0-zsk-8763",
        "to": "z1-ds-725",
        "kind": "delegates",
        "status": "ok"
      },
      {
        "from": "z2-ds-42069",
        "to": "z2-ksk-50719",
        "kind": "digest",
        "status": "broken"
      },
      {
        "from": "z2-ksk-50719",
        "to": "z2-zsk-32784",
        "kind": "signs",
        "status": "skipped"
      },
      {
        "from": "z1-zsk-11859",
        "to": "z2-ds-42069",
        "kind": "delegates",
        "status": "broken"
      },
      {
        "from": "z2-rr-SOA",
        "to": "z2-rr-SOA",
        "kind": "signs",
        "status": "skipped"
      }
    ],
    "folded": 0
  }
}

Next step

How to read the graph

Each column is a zone, from the root on the left to the name you typed on the right. On a narrow screen the zones run top to bottom instead. Keys sit inside their zone, a DS record joins a parent to its child and a line means a signature or a digest that was checked.

  • Thick outline: a key signing key (KSK), the key a DS record points at.
  • Rounded pill: a DS record, held by the parent zone.
  • Dashed outline: something that is unsigned or was not checked because the chain broke above it.
  • Warning colour with a cross: the link that fails, labelled with what is wrong.

The graph never relies on colour alone. Every node carries its key tag, and every line has the same meaning as its dash pattern.

The same check in words

The graph is a picture of the same data the DNSSEC checker uses, so a result here and on the checker always agree. Under the graph the chain of trust is listed step by step: the zone, its keys, the DS that joins it to its parent, the signature windows and the servers asked. That list is what a screen reader reads, and it works without JavaScript.

With JavaScript on, hovering or focusing a step in the list highlights its keys in the graph and says what they do. Tapping a key in the graph does the same on a phone.

Long chains and many keys

A name such as a.b.example.co.uk crosses five zones, and a zone in the middle of a key rollover publishes two key signing keys and two DS records. The graph keeps the keys on the path to the answer and folds the rest into a "more keys" node once there are more than 40 nodes. The step list is never folded.

The layout is fixed so the graph reads the same every time. There is no pan or zoom to learn. To work with the data yourself, copy the graph as JSON from the links under the result, or ask for it from the DNSSEC checker API or MCP tool.

If the domain is not signed

An unsigned domain draws a short graph: the root, the top-level domain and a zone with no DS record. That is a choice and not a fault. To turn DNSSEC on, ask your DNS provider to sign the zone, then add the DS record it gives you at your registrar.

Afterwards, draw the graph again. A signed zone with a DS that matches a key shows solid lines from the root down to the answer. For a closer look at the servers, see the DNS trace.

Questions people ask

Is the graph different from the checker?

No. It is the same data drawn another way, so a result here and on the checker always agree. The checker leads with the verdict and the steps, and this page leads with the picture.

Can I move or zoom the graph?

No. The layout is fixed so it reads the same every time and works without a pointer or JavaScript. The step list under it carries every detail as text.

What do the dashed nodes mean?

Dashed means unsigned, or not checked because a link above it failed. A dashed node is never a pass, and every dashed node has a word for it in the step list.

Why is there a node that says "more keys"?

Past 40 nodes the graph keeps the keys on the path to the answer and folds the others into one node so it stays readable. The step list shows every key.

Can I download the graph?

You can copy the nodes and edges as JSON. The same structure comes back from the API and from the MCP tool, so a script or an assistant can draw it too.

Does it work on a phone?

Yes. On a narrow screen the zones run from top to bottom, and tapping a key shows what it does. The step list works the same as on a wide screen.

Use it from AI, the API or the command line

Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is dnssec_check. Please be kind to the rate limits.

curl
curl "https://lookupowl.com/api/v1/tools/dnssec-check?q=cloudflare.com"
MCP
claude mcp add --transport http lookupowl https://lookupowl.com/mcp