ss
Updated:
2020-12-15 20:13:05 UTC (1439 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (1)
- ss/SOA
Secure (2)
- ss/NS
- ss/SOA
DNSKEY/DS/NSEC status
Bogus (2)
- ss/DNSKEY (alg 8, id 14462)
- ss/DNSKEY (alg 8, id 58030)
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- ss/DNSKEY (alg 8, id 43817)
- ss/DNSKEY (alg 8, id 48412)
- ss/DNSKEY (alg 8, id 51468)
- ss/DS (alg 8, id 43817)
- ss/DS (alg 8, id 43817)
Delegation status
Secure (1)
- . to ss
Notices
Errors (9)
- . to ss: 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. (185.17.236.20, 196.216.162.70, 196.216.168.27, 204.61.216.130, 2001:500:14:6130:ad::1, 2001:43f8:e0:1::70, 2001:43f8:120::27, UDP_-_EDNS0_4096_D_K)
- . to ss: 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. (185.17.236.20, 196.216.162.70, 196.216.168.27, 204.61.216.130, 2001:500:14:6130:ad::1, 2001:43f8:e0:1::70, 2001:43f8:120::27, UDP_-_EDNS0_4096_D_K)
- ss zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2a03:dd40:3::20)
- ss/DNSKEY (alg 8, id 43817): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (185.17.236.20, 196.216.162.70, 196.216.168.27, 204.61.216.130, 2001:500:14:6130:ad::1, 2001:43f8:e0:1::70, 2001:43f8:120::27, UDP_-_EDNS0_4096_D_K)
- ss/DNSKEY (alg 8, id 51468): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (185.17.236.20, 196.216.162.70, 196.216.168.27, 204.61.216.130, 2001:500:14:6130:ad::1, 2001:43f8:e0:1::70, 2001:43f8:120::27, UDP_-_EDNS0_4096_D_K)
- ss/DNSKEY (alg 8, id 58030): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (185.28.194.194, 185.38.108.108, UDP_-_EDNS0_4096_D_K)
- ss/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2a03:dd40:3::20, UDP_-_NOEDNS_)
- s6di2hcz07.ss/A has errors; select the "Denial of existence" DNSSEC option to see them.
- ss/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- ss/DNSKEY (alg 8, id 14462): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (185.28.194.194, 185.38.108.108, UDP_-_EDNS0_4096_D_K)
- ss/DNSKEY (alg 8, id 48412): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (185.17.236.20, 196.216.162.70, 196.216.168.27, 204.61.216.130, 2001:500:14:6130:ad::1, 2001:43f8:e0:1::70, 2001:43f8:120::27, UDP_-_EDNS0_4096_D_K)
- ss/DS (alg 8, id 43817): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ss/DS (alg 8, id 43817): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ss/DS (alg 8, id 43817): 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.
- ss/DS (alg 8, id 43817): 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.
- s6di2hcz07.ss/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- ss/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
