RRSIG ietf.org/A alg 5, id 40452: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG ietf.org/AAAA alg 5, id 40452: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG ietf.org/DNSKEY alg 5, id 40452: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG ietf.org/DNSKEY alg 5, id 40452: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG ietf.org/DNSKEY alg 5, id 45586: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG ietf.org/DNSKEY alg 5, id 45586: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG ietf.org/MX alg 5, id 40452: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG ietf.org/NS alg 5, id 40452: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG ietf.org/SOA alg 5, id 40452: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG ietf.org/TXT alg 5, id 40452: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
ietf.org/A: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (4.31.198.40, UDP_-_EDNS0_4096_D_KN)
ietf.org/DNSKEY (alg 5, id 40452): 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. (4.31.198.40, UDP_-_EDNS0_4096_D_KN)
ietf.org/DNSKEY (alg 5, id 45586): 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. (4.31.198.40, UDP_-_EDNS0_4096_D_KN)
ietf.org/DS (alg 5, id 45586): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ietf.org/DS (alg 5, id 45586): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ietf.org/DS (alg 5, id 45586): 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.
ietf.org/DS (alg 5, id 45586): 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.
ietf.org/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (4.31.198.40, UDP_-_EDNS0_4096_D_KN)
ietf.org/SOA: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (4.31.198.40, UDP_-_EDNS0_4096_D_KN_0x20)
ietf.org/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
ietf.org/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
ietf.org/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
ponu7kg8v9.ietf.org/A has warnings; select the "Denial of existence" DNSSEC option to see them.