View on GitHub

DNSViz: A DNS visualization tool

nsf.gov

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

RRset statusRRset status

Secure (6)
  • nsf.gov/A
  • nsf.gov/AAAA
  • nsf.gov/MX
  • nsf.gov/NS
  • nsf.gov/SOA
  • nsf.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • gov/DNSKEY (alg 8, id 24250)
  • gov/DNSKEY (alg 8, id 50011)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • nsf.gov/DNSKEY (alg 5, id 13516)
  • nsf.gov/DNSKEY (alg 5, id 29743)
  • nsf.gov/DNSKEY (alg 5, id 42708)
  • nsf.gov/DS (alg 5, id 13516)
  • nsf.gov/DS (alg 5, id 13516)
  • nsf.gov/DS (alg 5, id 29743)
  • nsf.gov/DS (alg 5, id 29743)

Delegation statusDelegation status

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

NoticesNotices

Errors (4)
  • nsf.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (204.14.134.242, 2607:f478:80:1::242, 2620:10f:6001:2::55, 2620:10f:6001:2::56)
  • nsf.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (204.14.134.242, 2607:f478:80:1::242, 2620:10f:6001:2::55, 2620:10f:6001:2::56, UDP_-_NOEDNS_)
  • nsf.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (204.14.134.242, 2607:f478:80:1::242, 2620:10f:6001:2::55, 2620:10f:6001:2::56, UDP_-_NOEDNS_)
  • 7mgc0tljas.nsf.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (29)
  • ./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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 60955): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
  • RRSIG nsf.gov/A alg 5, id 42708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/AAAA alg 5, id 42708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/DNSKEY alg 5, id 13516: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/DNSKEY alg 5, id 13516: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/DNSKEY alg 5, id 13516: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/DNSKEY alg 5, id 29743: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/DNSKEY alg 5, id 29743: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/DNSKEY alg 5, id 29743: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/DNSKEY alg 5, id 42708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/DNSKEY alg 5, id 42708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/DNSKEY alg 5, id 42708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/MX alg 5, id 42708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/NS alg 5, id 42708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/SOA alg 5, id 42708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/TXT alg 5, id 42708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • gov to nsf.gov: The following NS name(s) were found in the delegation NS RRset (i.e., in the gov zone), but not in the authoritative NS RRset: ns3.nsf.gov See RFC 1034, Sec. 4.2.2.
  • nsf.gov/DS (alg 5, id 13516): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nsf.gov/DS (alg 5, id 13516): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nsf.gov/DS (alg 5, id 13516): 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.
  • nsf.gov/DS (alg 5, id 13516): 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.
  • nsf.gov/DS (alg 5, id 29743): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nsf.gov/DS (alg 5, id 29743): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nsf.gov/DS (alg 5, id 29743): 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.
  • nsf.gov/DS (alg 5, id 29743): 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.
  • nsf.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nsf.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nsf.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