ss zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (196.1.4.230)
ss zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (196.1.4.230)
ss/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.1.4.230, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
ss/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.1.4.230, UDP_-_NOEDNS_)
ss/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.1.4.230, TCP_-_NOEDNS_)
ss/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.1.4.230, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
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.
wf7ah51zmy.ss/A 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.
wf7ah51zmy.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.