bogus.d4a7n3.rootcanary.net
Updated:
2021-02-05 14:30:21 UTC (1415 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Bogus (2)
- bogus.d4a7n3.rootcanary.net/A
- bogus.d4a7n3.rootcanary.net/AAAA
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 42351)
- d4a7n3.rootcanary.net/DNSKEY (alg 7, id 48396)
- d4a7n3.rootcanary.net/DS (alg 7, id 48396)
- net/DNSKEY (alg 8, id 30944)
- 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 d4a7n3.rootcanary.net
Notices
Errors (3)
- RRSIG bogus.d4a7n3.rootcanary.net/A alg 7, id 48396: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- RRSIG bogus.d4a7n3.rootcanary.net/AAAA alg 7, id 48396: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- d4a7n3.rootcanary.net/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- RRSIG bogus.d4a7n3.rootcanary.net/A alg 7, id 48396: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG bogus.d4a7n3.rootcanary.net/AAAA alg 7, id 48396: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG d4a7n3.rootcanary.net/DNSKEY alg 7, id 48396: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- d4a7n3.rootcanary.net/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
