secure.d3a8n3.rootcanary.net

Updated: 2020-04-19 18:05:47 UTC (1719 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 48903)
d3a8n3.rootcanary.net/DS (alg 8, id 5782)
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)

d3a8n3.rootcanary.net/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.

d3a8n3.rootcanary.net/DS (alg 8, id 5782): DNSSEC implementers are prohibited from implementing signing with DS algorithm 3 (GOST 34.11-94). See RFC 8624, Sec. 3.2.
d3a8n3.rootcanary.net/DS (alg 8, id 5782): DNSSEC implementers are prohibited from implementing signing with DS algorithm 3 (GOST 34.11-94). See RFC 8624, Sec. 3.2.
d3a8n3.rootcanary.net/DS (alg 8, id 5782): 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.
d3a8n3.rootcanary.net/DS (alg 8, id 5782): 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.
secure.d3a8n3.rootcanary.net/AAAA: 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. (195.176.255.9, UDP_-_EDNS0_4096_D_K)