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

Bogus (1)
  • nsf.gov/SOA
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 (10)
  • ./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)
  • nsf.gov/DNSKEY (alg 5, id 12556)
  • nsf.gov/DNSKEY (alg 5, id 28041)
  • nsf.gov/DNSKEY (alg 5, id 6273)
  • nsf.gov/DS (alg 5, id 12556)
  • nsf.gov/DS (alg 5, id 12556)

Delegation statusDelegation status

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

NoticesNotices

Errors (16)
  • RRSIG nsf.gov/A alg 5, id 28041: The Signature Expiration field of the RRSIG RR (2021-09-06 04:52:32+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG nsf.gov/AAAA alg 5, id 28041: The Signature Expiration field of the RRSIG RR (2021-09-06 21:20:04+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG nsf.gov/DNSKEY alg 5, id 12556: The Signature Expiration field of the RRSIG RR (2021-09-06 11:23:48+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG nsf.gov/DNSKEY alg 5, id 12556: The Signature Expiration field of the RRSIG RR (2021-09-06 11:23:48+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG nsf.gov/DNSKEY alg 5, id 28041: The Signature Expiration field of the RRSIG RR (2021-09-06 11:23:48+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG nsf.gov/DNSKEY alg 5, id 28041: The Signature Expiration field of the RRSIG RR (2021-09-06 11:23:48+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG nsf.gov/MX alg 5, id 28041: The Signature Expiration field of the RRSIG RR (2021-09-06 19:35:16+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG nsf.gov/NS alg 5, id 28041: The Signature Expiration field of the RRSIG RR (2021-09-07 02:51:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG nsf.gov/SOA alg 5, id 28041: The Signature Expiration field of the RRSIG RR (2021-09-07 04:05:28+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG nsf.gov/TXT alg 5, id 28041: The Signature Expiration field of the RRSIG RR (2021-09-06 15:34:14+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • gov to nsf.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. (128.150.2.55, 2620:10f:6001:2::55, UDP_-_EDNS0_4096_D_KN)
  • nsf.gov/DNSKEY (alg 5, id 6273): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (128.150.2.55, 2620:10f:6001:2::55, UDP_-_EDNS0_4096_D_KN)
  • nsf.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • nsf.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • 9bu6xo72t5.nsf.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • nsf.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (40)
  • RRSIG nsf.gov/A alg 5, id 28041: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/A alg 5, id 28041: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsf.gov/A alg 5, id 6273: 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 28041: 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 28041: 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 6273: 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 12556: 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 12556: 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 12556: 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 12556: 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 12556: 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 28041: 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 28041: 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 28041: 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 28041: 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 28041: 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 6273: 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 6273: 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 6273: 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 28041: 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 28041: 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 6273: 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 28041: 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 28041: 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 6273: 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 28041: 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 28041: 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 6273: 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 28041: 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 28041: 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 6273: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • nsf.gov/DS (alg 5, id 12556): 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 12556): 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 12556): 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 12556): 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/TXT: 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. (2620:10f:6001:2::55, 2620:10f:6001:2::56, UDP_-_EDNS0_4096_D_KN)
  • 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.
  • 9bu6xo72t5.nsf.gov/A 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