ss
Updated:
2021-01-08 12:15:05 UTC (1416 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- ss/NS
- ss/SOA
- ss/SOA
- ss/SOA
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- ./DNSKEY (alg 8, id 42351)
- ss/DNSKEY (alg 8, id 14462)
- ss/DNSKEY (alg 8, id 43817)
- ss/DNSKEY (alg 8, id 48189)
- ss/DNSKEY (alg 8, id 58030)
- ss/DS (alg 8, id 43817)
- ss/DS (alg 8, id 43817)
Delegation status
Secure (1)
- . to ss
Notices
Errors (14)
- . 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. (196.216.168.27, UDP_-_EDNS0_4096_D_KN)
- RRSIG ss/DNSKEY alg 8, id 14462: The Signature Expiration field of the RRSIG RR (2020-12-30 18:35:39+00:00) is 8 days in the past. See RFC 4035, Sec. 5.3.1.
- RRSIG ss/DNSKEY alg 8, id 14462: The Signature Expiration field of the RRSIG RR (2020-12-30 18:35:39+00:00) is 8 days in the past. See RFC 4035, Sec. 5.3.1.
- RRSIG ss/DNSKEY alg 8, id 14462: The Signature Expiration field of the RRSIG RR (2020-12-30 18:35:39+00:00) is 8 days in the past. See RFC 4035, Sec. 5.3.1.
- RRSIG ss/DNSKEY alg 8, id 14462: The Signature Expiration field of the RRSIG RR (2020-12-30 18:35:39+00:00) is 8 days in the past. See RFC 4035, Sec. 5.3.1.
- RRSIG ss/DNSKEY alg 8, id 43817: The Signature Expiration field of the RRSIG RR (2020-12-30 18:35:39+00:00) is 8 days in the past. See RFC 4035, Sec. 5.3.1.
- RRSIG ss/DNSKEY alg 8, id 43817: The Signature Expiration field of the RRSIG RR (2020-12-30 18:35:39+00:00) is 8 days in the past. See RFC 4035, Sec. 5.3.1.
- RRSIG ss/DNSKEY alg 8, id 43817: The Signature Expiration field of the RRSIG RR (2020-12-30 18:35:39+00:00) is 8 days in the past. See RFC 4035, Sec. 5.3.1.
- RRSIG ss/DNSKEY alg 8, id 43817: The Signature Expiration field of the RRSIG RR (2020-12-30 18:35:39+00:00) is 8 days in the past. See RFC 4035, Sec. 5.3.1.
- ss zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (185.17.236.20, 2a03:dd40:3::20, 2a03:dd41:239::3)
- ss/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.17.236.20, 2a03:dd40:3::20, 2a03:dd41:239::3, UDP_-_NOEDNS_)
- laz8k5q6jm.ss/A has errors; select the "Denial of existence" DNSSEC option to see them.
- ss/DNSKEY 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)
- . to ss: The glue address(es) for root.nic.ss (185.17.236.20) differed from its authoritative address(es) (185.17.239.3). See RFC 1034, Sec. 4.2.2.
- . to ss: The glue address(es) for root.nic.ss (2a03:dd40:3::20) differed from its authoritative address(es) (2a03:dd41:239::3). See RFC 1034, Sec. 4.2.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): 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.
- laz8k5q6jm.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.
