View on GitHub

DNSViz: A DNS visualization tool

nrd.gov

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

RRset statusRRset status

Secure (4)
  • nrd.gov/A
  • nrd.gov/MX
  • nrd.gov/NS
  • nrd.gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (15)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • ./DNSKEY (alg 8, id 48903)
  • gov/DNSKEY (alg 8, id 40176)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • nrd.gov/DNSKEY (alg 8, id 17133)
  • nrd.gov/DNSKEY (alg 8, id 37234)
  • nrd.gov/DNSKEY (alg 8, id 42514)
  • nrd.gov/DNSKEY (alg 8, id 65194)
  • nrd.gov/DS (alg 8, id 37234)
  • nrd.gov/DS (alg 8, id 37234)
  • nrd.gov/DS (alg 8, id 65194)
  • nrd.gov/DS (alg 8, id 65194)

Delegation statusDelegation status

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

NoticesNotices

Errors (15)
  • gov to nrd.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. (52.61.51.239, 52.222.56.242, UDP_-_EDNS0_4096_D_K)
  • gov to nrd.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. (52.61.51.239, 52.222.56.242, UDP_-_EDNS0_4096_D_K)
  • nrd.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.61.51.239, 52.222.56.242, UDP_-_EDNS0_4096_D_K)
  • nrd.gov/DNSKEY (alg 8, id 17133): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.61.51.239, 52.222.56.242, UDP_-_EDNS0_4096_D_K)
  • nrd.gov/DNSKEY (alg 8, id 37234): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.61.51.239, 52.222.56.242, UDP_-_EDNS0_4096_D_K)
  • nrd.gov/DNSKEY (alg 8, id 42514): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.61.51.239, 52.222.56.242, UDP_-_EDNS0_4096_D_K)
  • nrd.gov/DNSKEY (alg 8, id 65194): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.61.51.239, 52.222.56.242, UDP_-_EDNS0_4096_D_K)
  • nrd.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.61.51.239, 52.222.56.242, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • nrd.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.61.51.239, 52.222.56.242, UDP_-_EDNS0_4096_D_K)
  • nrd.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (52.61.51.239, 52.222.56.242, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • 03nrkd4s7e.nrd.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • nrd.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • nrd.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • nrd.gov/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • nrd.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): 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.
  • gov/DS (alg 8, id 7698): 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.
  • nrd.gov/DS (alg 8, id 37234): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nrd.gov/DS (alg 8, id 37234): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nrd.gov/DS (alg 8, id 37234): 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.
  • nrd.gov/DS (alg 8, id 37234): 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.
  • nrd.gov/DS (alg 8, id 65194): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nrd.gov/DS (alg 8, id 65194): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nrd.gov/DS (alg 8, id 65194): 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.
  • nrd.gov/DS (alg 8, id 65194): 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.
  • 03nrkd4s7e.nrd.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nrd.gov/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nrd.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nrd.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