bogus.d2a5n1.rootcanary.net
Updated:
2023-05-18 09:16:47 UTC (583 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Bogus (2)
- bogus.d2a5n1.rootcanary.net/A
- bogus.d2a5n1.rootcanary.net/AAAA
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- d2a5n1.rootcanary.net/DNSKEY (alg 5, id 25456)
- d2a5n1.rootcanary.net/DS (alg 5, id 25456)
- net/DNSKEY (alg 8, id 27554)
- net/DNSKEY (alg 8, id 35886)
- 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 d2a5n1.rootcanary.net
Notices
Errors (2)
- RRSIG bogus.d2a5n1.rootcanary.net/A alg 5, id 25456: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- RRSIG bogus.d2a5n1.rootcanary.net/AAAA alg 5, id 25456: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
Warnings (4)
- RRSIG bogus.d2a5n1.rootcanary.net/A alg 5, id 25456: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG bogus.d2a5n1.rootcanary.net/AAAA alg 5, id 25456: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG d2a5n1.rootcanary.net/DNSKEY alg 5, id 25456: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- d2a5n1.rootcanary.net/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
