RRSIG bogus.d3a5n1.rootcanary.net/A alg 5, id 32389: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG bogus.d3a5n1.rootcanary.net/AAAA alg 5, id 32389: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
Warnings (8)
RRSIG bogus.d3a5n1.rootcanary.net/A alg 5, id 32389: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG bogus.d3a5n1.rootcanary.net/AAAA alg 5, id 32389: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG d3a5n1.rootcanary.net/DNSKEY alg 5, id 32389: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
d3a5n1.rootcanary.net/DS (alg 5, id 32389): DNSSEC implementers are prohibited from implementing signing with DS algorithm 3 (GOST 34.11-94). See RFC 8624, Sec. 3.2.
d3a5n1.rootcanary.net/DS (alg 5, id 32389): DNSSEC implementers are prohibited from implementing signing with DS algorithm 3 (GOST 34.11-94). See RFC 8624, Sec. 3.2.
d3a5n1.rootcanary.net/DS (alg 5, id 32389): Generating cryptographic hashes using algorithm 3 (GOST 34.11-94) is not supported by this code, so the cryptographic status of the DS RR is unknown. See RFC 4035, Sec. 5.2.
d3a5n1.rootcanary.net/DS (alg 5, id 32389): Generating cryptographic hashes using algorithm 3 (GOST 34.11-94) is not supported by this code, so the cryptographic status of the DS RR is unknown. See RFC 4035, Sec. 5.2.
d3a5n1.rootcanary.net/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.