secure.d2a10n3.rootcanary.net
Updated:
2021-05-12 11:32:09 UTC (1319 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (2)
- secure.d2a10n3.rootcanary.net/A
- secure.d2a10n3.rootcanary.net/AAAA
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- d2a10n3.rootcanary.net/DNSKEY (alg 10, id 47604)
- d2a10n3.rootcanary.net/DS (alg 10, id 47604)
- net/DNSKEY (alg 8, id 35886)
- net/DNSKEY (alg 8, id 6203)
- 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
Secure (3)
- . to net
- net to rootcanary.net
- rootcanary.net to d2a10n3.rootcanary.net
Notices
Errors (1)
- d2a10n3.rootcanary.net/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- RRSIG d2a10n3.rootcanary.net/DNSKEY alg 10, id 47604: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG secure.d2a10n3.rootcanary.net/A alg 10, id 47604: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG secure.d2a10n3.rootcanary.net/AAAA alg 10, id 47604: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- d2a10n3.rootcanary.net/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
