View on GitHub

DNSViz: A DNS visualization tool

savannah.gnu.org

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (7)
  • gnu.org/SOA
  • savannah.gnu.org/A
  • savannah.gnu.org/AAAA
  • savannah.gnu.org/MX
  • savannah.gnu.org/NS
  • savannah.gnu.org/SOA
  • savannah.gnu.org/TXT
Secure (1)
  • org/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • NSEC3 proving non-existence of gnu.org/DS
  • org/DNSKEY (alg 8, id 10449)
  • org/DNSKEY (alg 8, id 15843)
  • org/DNSKEY (alg 8, id 26974)
  • org/DS (alg 8, id 26974)

Delegation statusDelegation status

Insecure (2)
  • gnu.org to savannah.gnu.org
  • org to gnu.org
Secure (1)
  • . to org

NoticesNotices

Errors (2)
  • NSEC3 proving non-existence of gnu.org/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of gnu.org/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (2)
  • NSEC3 proving non-existence of gnu.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of gnu.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph