RRSIG access-board.gov/A alg 5, id 2730: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG access-board.gov/DNSKEY alg 5, id 2730: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG access-board.gov/DNSKEY alg 5, id 2730: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG access-board.gov/DNSKEY alg 5, id 2730: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG access-board.gov/DNSKEY alg 5, id 44299: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG access-board.gov/DNSKEY alg 5, id 44299: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG access-board.gov/DNSKEY alg 5, id 44299: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG access-board.gov/MX alg 5, id 2730: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG access-board.gov/NS alg 5, id 2730: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG access-board.gov/SOA alg 5, id 2730: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG access-board.gov/TXT alg 5, id 2730: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
access-board.gov/DS (alg 5, id 44299): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
access-board.gov/DS (alg 5, id 44299): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
access-board.gov/DS (alg 5, id 44299): 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.
access-board.gov/DS (alg 5, id 44299): 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.
access-board.gov/SOA: 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. (52.86.34.161, UDP_-_EDNS0_4096_D_KN)
access-board.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
access-board.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
access-board.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
3klx9dorua.access-board.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
access-board.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.