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. (152.180.40.110, 2600:803:250:1040::110, 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. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
ntsb.gov/A: The DNSKEY RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
ntsb.gov/AAAA: The DNSKEY RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
ntsb.gov/MX: The DNSKEY RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
ntsb.gov/NS: The DNSKEY RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
ntsb.gov/NSEC3PARAM: The DNSKEY RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
ntsb.gov/SOA: The DNSKEY RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (152.180.40.110, 2600:803:250:1040::110, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
ntsb.gov/TXT: The DNSKEY RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
hn81jbaklx.ntsb.gov/A 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 (6)
RRSIG ntsb.gov/DNSKEY alg 10, id 21772: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ntsb.gov/DNSKEY alg 10, id 21772: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG ntsb.gov/DNSKEY alg 10, id 21772: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
ntsb.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
hn81jbaklx.ntsb.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
ntsb.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.