ntsb.gov
Updated:
2021-03-07 15:52:14 UTC (1362 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (5)
- ntsb.gov/A
- ntsb.gov/MX
- ntsb.gov/NS
- ntsb.gov/SOA
- ntsb.gov/TXT
DNSKEY/DS/NSEC status
Bogus (4)
- ntsb.gov/DNSKEY (alg 8, id 14297)
- ntsb.gov/DNSKEY (alg 8, id 303)
- ntsb.gov/DNSKEY (alg 8, id 60363)
- ntsb.gov/DNSKEY (alg 8, id 62572)
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 42351)
- gov/DNSKEY (alg 8, id 27306)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- ntsb.gov/DS (alg 8, id 14297)
- ntsb.gov/DS (alg 8, id 14297)
- ntsb.gov/DS (alg 8, id 62572)
- ntsb.gov/DS (alg 8, id 62572)
Delegation status
Bogus (1)
- gov to ntsb.gov
Secure (1)
- . to gov
Notices
Errors (19)
- gov to ntsb.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. (199.173.155.4, UDP_-_EDNS0_4096_D_KN)
- gov to ntsb.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. (199.173.155.4, UDP_-_EDNS0_4096_D_KN)
- ntsb.gov zone: The following NS name(s) did not resolve to address(es): 10.200.130.11, ns1.ntsb.gov
- ntsb.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.173.155.5)
- ntsb.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, UDP_-_EDNS0_4096_D_KN)
- ntsb.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.173.155.5, UDP_-_NOEDNS_)
- ntsb.gov/DNSKEY (alg 8, id 14297): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, UDP_-_EDNS0_4096_D_KN)
- ntsb.gov/DNSKEY (alg 8, id 303): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, UDP_-_EDNS0_4096_D_KN)
- ntsb.gov/DNSKEY (alg 8, id 60363): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, UDP_-_EDNS0_4096_D_KN)
- ntsb.gov/DNSKEY (alg 8, id 62572): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, UDP_-_EDNS0_4096_D_KN)
- ntsb.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- ntsb.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, UDP_-_EDNS0_4096_D_KN)
- ntsb.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.173.155.5, UDP_-_NOEDNS_)
- ntsb.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- ntsb.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, UDP_-_EDNS0_4096_D_KN)
- ntsb.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- 73rqflpnkh.ntsb.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- ntsb.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- ntsb.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
- gov to ntsb.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): 10.200.130.11 See RFC 1034, Sec. 4.2.2.
- gov to ntsb.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: ns1.ntsb.gov See RFC 1034, Sec. 4.2.2.
- ntsb.gov/DS (alg 8, id 14297): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ntsb.gov/DS (alg 8, id 14297): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ntsb.gov/DS (alg 8, id 14297): 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.
- ntsb.gov/DS (alg 8, id 14297): 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.
- ntsb.gov/DS (alg 8, id 62572): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ntsb.gov/DS (alg 8, id 62572): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ntsb.gov/DS (alg 8, id 62572): 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.
- ntsb.gov/DS (alg 8, id 62572): 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.
JavaScript is required to make the graph below interactive.
