View on GitHub

DNSViz: A DNS visualization tool

nwcg.gov

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

RRset statusRRset status

Secure (3)
  • nwcg.gov/NS
  • nwcg.gov/SOA
  • nwcg.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./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)
  • nwcg.gov/DNSKEY (alg 10, id 11297)
  • nwcg.gov/DNSKEY (alg 10, id 23787)
  • nwcg.gov/DNSKEY (alg 10, id 27534)
  • nwcg.gov/DNSKEY (alg 10, id 8945)
  • nwcg.gov/DS (alg 10, id 23787)
  • nwcg.gov/DS (alg 10, id 23787)

Delegation statusDelegation status

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

NoticesNotices

Errors (1)
  • ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:500:12::d0d, UDP_-_EDNS0_512_D_K)
Warnings (38)
  • ./DNSKEY (alg 8, id 20326): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_K)
  • ./DNSKEY (alg 8, id 48903): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_K)
  • RRSIG nwcg.gov/DNSKEY alg 10, id 11297: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/DNSKEY alg 10, id 11297: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/DNSKEY alg 10, id 11297: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/DNSKEY alg 10, id 11297: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/DNSKEY alg 10, id 23787: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/DNSKEY alg 10, id 23787: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/DNSKEY alg 10, id 23787: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/DNSKEY alg 10, id 23787: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/DNSKEY alg 10, id 27534: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/DNSKEY alg 10, id 27534: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/DNSKEY alg 10, id 27534: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/DNSKEY alg 10, id 27534: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/DNSKEY alg 10, id 8945: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/DNSKEY alg 10, id 8945: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/DNSKEY alg 10, id 8945: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/DNSKEY alg 10, id 8945: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/NS alg 10, id 11297: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/NS alg 10, id 8945: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/SOA alg 10, id 11297: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/SOA alg 10, id 8945: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/TXT alg 10, id 11297: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG nwcg.gov/TXT alg 10, id 8945: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • 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.
  • nwcg.gov/DS (alg 10, id 23787): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nwcg.gov/DS (alg 10, id 23787): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nwcg.gov/DS (alg 10, id 23787): 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.
  • nwcg.gov/DS (alg 10, id 23787): 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.
  • nwcg.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nwcg.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nwcg.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ysda0wt6x4.nwcg.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nwcg.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nwcg.gov/CNAME 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