View on GitHub

DNSViz: A DNS visualization tool

cnss.gov

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

RRset statusRRset status

Bogus (2)
  • cnss.gov/NS
  • cnss.gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (4)
  • cnss.gov/DNSKEY (alg 8, id 26101)
  • cnss.gov/DNSKEY (alg 8, id 31669)
  • cnss.gov/DNSKEY (alg 8, id 4231)
  • cnss.gov/DNSKEY (alg 8, id 59763)
Secure (7)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • cnss.gov/DS (alg 8, id 16877)
  • cnss.gov/DS (alg 8, id 58309)
  • gov/DNSKEY (alg 8, id 48498)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
Non_existent (2)
  • cnss.gov/DNSKEY (alg 8, id 16877)
  • cnss.gov/DNSKEY (alg 8, id 58309)

Delegation statusDelegation status

Bogus (1)
  • gov to cnss.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (8)
  • gov to cnss.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (8.44.96.33, 8.44.96.34, UDP_-_EDNS0_4096_D_KN)
  • gov to cnss.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (8.44.96.33, 8.44.96.34, UDP_-_EDNS0_4096_D_KN)
  • cnss.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • cnss.gov/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • cnss.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • cnss.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • cnss.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • 0w459u8lpb.cnss.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • cnss.gov/DS (alg 8, id 58309): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cnss.gov/DS (alg 8, id 58309): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cnss.gov/DS (alg 8, id 58309): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • cnss.gov/DS (alg 8, id 58309): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • cnss.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • cnss.gov/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • cnss.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • cnss.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • cnss.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 0w459u8lpb.cnss.gov/A 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