dnssec.fail
Updated:
2021-05-28 19:26:18 UTC (1274 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (4)
- dnssec.fail/A
- dnssec.fail/AAAA
- dnssec.fail/NS
- dnssec.fail/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- dnssec.fail/DS (alg 8, id 38464)
- fail/DNSKEY (alg 8, id 33205)
- fail/DNSKEY (alg 8, id 46236)
- fail/DS (alg 8, id 33205)
- fail/DS (alg 8, id 33205)
Non_existent (1)
- dnssec.fail/DNSKEY (alg 8, id 38464)
Delegation status
Bogus (1)
- fail to dnssec.fail
Secure (1)
- . to fail
Notices
Errors (12)
- dnssec.fail/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (151.249.124.1, 151.249.125.2, 151.249.126.3, 2a01:5b40:ac1::1, 2a01:5b40:ac2::1, 2a01:5b40:ac3::1, UDP_-_EDNS0_4096_D_KN)
- dnssec.fail/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (151.249.124.1, 151.249.125.2, 151.249.126.3, 2a01:5b40:ac1::1, 2a01:5b40:ac2::1, 2a01:5b40:ac3::1, UDP_-_EDNS0_4096_D_KN)
- dnssec.fail/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (151.249.124.1, 151.249.125.2, 151.249.126.3, 2a01:5b40:ac1::1, 2a01:5b40:ac2::1, 2a01:5b40:ac3::1, UDP_-_EDNS0_4096_D_KN)
- dnssec.fail/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (151.249.124.1, 151.249.125.2, 151.249.126.3, 2a01:5b40:ac1::1, 2a01:5b40:ac2::1, 2a01:5b40:ac3::1, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- fail to dnssec.fail: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (151.249.124.1, 151.249.125.2, 151.249.126.3, 2a01:5b40:ac1::1, 2a01:5b40:ac2::1, 2a01:5b40:ac3::1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- fail to dnssec.fail: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (151.249.124.1, 151.249.125.2, 151.249.126.3, 2a01:5b40:ac1::1, 2a01:5b40:ac2::1, 2a01:5b40:ac3::1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- fail zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:dcd:4::7)
- ay13jomz0n.dnssec.fail/A has errors; select the "Denial of existence" DNSSEC option to see them.
- dnssec.fail/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- dnssec.fail/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- dnssec.fail/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
- dnssec.fail/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- dnssec.fail/NS: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (151.249.125.2, UDP_-_EDNS0_4096_D_KN)
- fail/DS (alg 8, id 33205): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- fail/DS (alg 8, id 33205): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- fail/DS (alg 8, id 33205): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- fail/DS (alg 8, id 33205): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
JavaScript is required to make the graph below interactive.
