secure.d4a1n1.rootcanary.net
Updated:
2020-04-19 17:25:22 UTC (1706 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (2)
- secure.d4a1n1.rootcanary.net/A
- secure.d4a1n1.rootcanary.net/AAAA
DNSKEY/DS/NSEC status
Insecure (1)
- d4a1n1.rootcanary.net/DNSKEY (alg 1, id 1927)
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- d4a1n1.rootcanary.net/DS (alg 1, id 1927)
- 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 d4a1n1.rootcanary.net
Secure (2)
- . to net
- net to rootcanary.net
Notices
Warnings (7)
- RRSIG d4a1n1.rootcanary.net/DNSKEY alg 1, id 1927: DNSSEC implementers are prohibited from implementing signing with DNSSEC algorithm 1 (RSAMD5). See RFC 8624, Sec. 3.1.
- RRSIG d4a1n1.rootcanary.net/DNSKEY alg 1, id 1927: DNSSEC implementers are prohibited from implementing validation of DNSSEC algorithm 1 (RSAMD5). See RFC 8624, Sec. 3.1.
- RRSIG secure.d4a1n1.rootcanary.net/A alg 1, id 1927: DNSSEC implementers are prohibited from implementing signing with DNSSEC algorithm 1 (RSAMD5). See RFC 8624, Sec. 3.1.
- RRSIG secure.d4a1n1.rootcanary.net/A alg 1, id 1927: DNSSEC implementers are prohibited from implementing validation of DNSSEC algorithm 1 (RSAMD5). See RFC 8624, Sec. 3.1.
- RRSIG secure.d4a1n1.rootcanary.net/AAAA alg 1, id 1927: DNSSEC implementers are prohibited from implementing signing with DNSSEC algorithm 1 (RSAMD5). See RFC 8624, Sec. 3.1.
- RRSIG secure.d4a1n1.rootcanary.net/AAAA alg 1, id 1927: DNSSEC implementers are prohibited from implementing validation of DNSSEC algorithm 1 (RSAMD5). See RFC 8624, Sec. 3.1.
- d4a1n1.rootcanary.net/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
