View on GitHub

DNSViz: A DNS visualization tool

git.io

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

RRset statusRRset status

Insecure (3)
  • git.io/A
  • git.io/NS
  • git.io/SOA
Secure (1)
  • io/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • NSEC3 proving non-existence of git.io/DS
  • io/DNSKEY (alg 8, id 11454)
  • io/DNSKEY (alg 8, id 57355)
  • io/DNSKEY (alg 8, id 6933)
  • io/DS (alg 8, id 57355)

Delegation statusDelegation status

Insecure (1)
  • io to git.io
Secure (1)
  • . to io

NoticesNotices

Errors (4)
  • NSEC3 proving non-existence of git.io/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 git.io/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • io zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2a01:8840:9f::17)
  • git.io/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • NSEC3 proving non-existence of git.io/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of git.io/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • git.io/DS has warnings; select the "Denial of existence" DNSSEC option to see them.

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