View on GitHub

DNSViz: A DNS visualization tool

sdr.gov

« 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)
  • sdr.gov/NS
  • sdr.gov/SOA
  • sdr.gov/TXT
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (3)
  • sdr.gov/DNSKEY (alg 5, id 15012)
  • sdr.gov/DNSKEY (alg 5, id 28935)
  • sdr.gov/DNSKEY (alg 5, id 4108)
Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • NSEC3 proving non-existence of sdr.gov/DS
  • gov/DNSKEY (alg 8, id 6229)
  • gov/DNSKEY (alg 8, id 7030)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Insecure (1)
  • gov to sdr.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (3)
  • NSEC3 proving non-existence of sdr.gov/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 sdr.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • sdr.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (19)
  • NSEC3 proving non-existence of sdr.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of sdr.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG sdr.gov/DNSKEY alg 5, id 28935: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sdr.gov/DNSKEY alg 5, id 28935: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sdr.gov/DNSKEY alg 5, id 28935: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sdr.gov/DNSKEY alg 5, id 4108: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sdr.gov/DNSKEY alg 5, id 4108: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sdr.gov/DNSKEY alg 5, id 4108: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sdr.gov/NS alg 5, id 28935: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sdr.gov/SOA alg 5, id 28935: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sdr.gov/TXT alg 5, id 28935: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • sdr.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gfrecztms8.sdr.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sdr.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sdr.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sdr.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sdr.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sdr.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sdr.gov/DNSKEY 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