nsf.gov
Updated:
2022-10-20 01:02:28 UTC (765 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- nsf.gov/A
- nsf.gov/AAAA
- nsf.gov/MX
- nsf.gov/NS
- nsf.gov/SOA
- nsf.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 261)
- gov/DNSKEY (alg 8, id 56278)
- 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 44235)
- nsf.gov/DS (alg 5, id 13516)
- nsf.gov/DS (alg 5, id 13516)
Delegation status
Secure (2)
- . to gov
- gov to nsf.gov
Notices
Errors (3)
- nsf.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (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. (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. (2620:10f:6001:2::55, 2620:10f:6001:2::56, UDP_-_NOEDNS_)
Warnings (19)
- RRSIG nsf.gov/A alg 5, id 44235: 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 44235: 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 44235: 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 44235: 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 44235: 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 44235: 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 44235: 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 44235: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- 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/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. (2607:f478:80:1::242, 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.
- brxne03su5.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.
JavaScript is required to make the graph below interactive.
