ss zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (185.17.236.20)
ss/DNSKEY: No response was received from the server over TCP (tried 11 times). See RFC 1035, Sec. 4.2. (185.17.236.20, TCP_-_EDNS0_4096_D_N)
ss/DNSKEY: No response was received from the server over UDP (tried 7 times). See RFC 1035, Sec. 4.2. (185.17.236.20, UDP_-_EDNS0_512_D_KN)
ss/SOA: No response was received from the server over TCP (tried 2 times). See RFC 1035, Sec. 4.2. (185.17.236.20, TCP_-_EDNS0_4096_D_N)
ss/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (185.17.236.20, TCP_-_EDNS0_4096_D_N)
fzmohtn2sr.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 (6)
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.
fzmohtn2sr.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.