View on GitHub

DNSViz: A DNS visualization tool

ncd.gov

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

RRset statusRRset status

Bogus (3)
  • ncd.gov/MX
  • ncd.gov/SOA
  • ncd.gov/TXT
Secure (2)
  • ncd.gov/A
  • ncd.gov/NS

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • gov/DNSKEY (alg 8, id 57735)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • ncd.gov/DNSKEY (alg 5, id 33278)
  • ncd.gov/DNSKEY (alg 5, id 8907)
  • ncd.gov/DS (alg 5, id 33278)
  • ncd.gov/DS (alg 5, id 33278)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to ncd.gov

NoticesNotices

Errors (7)
  • RRSIG ncd.gov/MX alg 5, id 8907: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG ncd.gov/SOA alg 5, id 8907: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG ncd.gov/TXT alg 5, id 8907: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • ncd.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • awlx0oyp89.ncd.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ncd.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • ncd.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (24)
  • RRSIG ncd.gov/A alg 5, id 8907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ncd.gov/DNSKEY alg 5, id 33278: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ncd.gov/DNSKEY alg 5, id 33278: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ncd.gov/MX alg 5, id 8907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ncd.gov/NS alg 5, id 8907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ncd.gov/SOA alg 5, id 8907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ncd.gov/TXT alg 5, id 8907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • gov to ncd.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): ns3.milesdns.com See RFC 1034, Sec. 4.2.2.
  • ncd.gov/A: The server appeared to understand EDNS by including RRSIG records, but its response included no OPT record. See RFC 6891, Sec. 7. (13.82.63.61, UDP_-_EDNS0_4096_D_KN)
  • ncd.gov/DNSKEY (alg 5, id 33278): The server appeared to understand EDNS by including RRSIG records, but its response included no OPT record. See RFC 6891, Sec. 7. (13.82.63.61, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ncd.gov/DNSKEY (alg 5, id 8907): The server appeared to understand EDNS by including RRSIG records, but its response included no OPT record. See RFC 6891, Sec. 7. (13.82.63.61, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ncd.gov/DS (alg 5, id 33278): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ncd.gov/DS (alg 5, id 33278): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ncd.gov/DS (alg 5, id 33278): 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.
  • ncd.gov/DS (alg 5, id 33278): 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.
  • ncd.gov/MX: The server appeared to understand EDNS by including RRSIG records, but its response included no OPT record. See RFC 6891, Sec. 7. (13.82.63.61, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ncd.gov/NS: The server appeared to understand EDNS by including RRSIG records, but its response included no OPT record. See RFC 6891, Sec. 7. (13.82.63.61, UDP_-_EDNS0_4096_D_KN)
  • ncd.gov/SOA: The server appeared to understand EDNS by including RRSIG records, but its response included no OPT record. See RFC 6891, Sec. 7. (13.82.63.61, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ncd.gov/TXT: The server appeared to understand EDNS by including RRSIG records, but its response included no OPT record. See RFC 6891, Sec. 7. (13.82.63.61, UDP_-_EDNS0_4096_D_KN)
  • ncd.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ncd.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ncd.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • awlx0oyp89.ncd.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ncd.gov/AAAA 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