secure.d3a13n3.rootcanary.net
Updated:
2020-04-19 18:05:55 UTC (1716 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (2)
- secure.d3a13n3.rootcanary.net/A
- secure.d3a13n3.rootcanary.net/AAAA
DNSKEY/DS/NSEC status
Insecure (1)
- d3a13n3.rootcanary.net/DNSKEY (alg 13, id 23307)
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- d3a13n3.rootcanary.net/DS (alg 13, id 23307)
- 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)
Delegation status
Insecure (1)
- rootcanary.net to d3a13n3.rootcanary.net
Secure (2)
- . to net
- net to rootcanary.net
Notices
Errors (1)
- d3a13n3.rootcanary.net/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- d3a13n3.rootcanary.net/DS (alg 13, id 23307): DNSSEC implementers are prohibited from implementing signing with DS algorithm 3 (GOST 34.11-94). See RFC 8624, Sec. 3.2.
- d3a13n3.rootcanary.net/DS (alg 13, id 23307): DNSSEC implementers are prohibited from implementing signing with DS algorithm 3 (GOST 34.11-94). See RFC 8624, Sec. 3.2.
- d3a13n3.rootcanary.net/DS (alg 13, id 23307): 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.
- d3a13n3.rootcanary.net/DS (alg 13, id 23307): 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.
JavaScript is required to make the graph below interactive.
