bogus.d3a16n3.rootcanary.net

Updated: 2020-04-19 17:18:47 UTC (1706 days ago) Update now

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 48903)
d3a16n3.rootcanary.net/DS (alg 16, id 28995)
net/DNSKEY (alg 8, id 24512)
net/DNSKEY (alg 8, id 35886)
net/DNSKEY (alg 8, id 36059)
net/DS (alg 8, id 35886)
rootcanary.net/DNSKEY (alg 8, id 25188)
rootcanary.net/DNSKEY (alg 8, id 64786)
rootcanary.net/DS (alg 8, id 64786)

RRSIG bogus.d3a16n3.rootcanary.net/A alg 16, id 28995: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG bogus.d3a16n3.rootcanary.net/AAAA alg 16, id 28995: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
d3a16n3.rootcanary.net/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.

d3a16n3.rootcanary.net/DS (alg 16, id 28995): DNSSEC implementers are prohibited from implementing signing with DS algorithm 3 (GOST 34.11-94). See RFC 8624, Sec. 3.2.
d3a16n3.rootcanary.net/DS (alg 16, id 28995): DNSSEC implementers are prohibited from implementing signing with DS algorithm 3 (GOST 34.11-94). See RFC 8624, Sec. 3.2.
d3a16n3.rootcanary.net/DS (alg 16, id 28995): 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.
d3a16n3.rootcanary.net/DS (alg 16, id 28995): 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.