dnscrypt.pl zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (51.38.99.90, 2001:41d0:701:1100::66c)
dnscrypt.pl zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (51.38.99.90, 2001:41d0:701:1100::66c)
dnscrypt.pl/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (51.38.99.90, 2001:41d0:701:1100::66c, UDP_-_NOEDNS_)
dnscrypt.pl/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (79.98.145.34, UDP_-_EDNS0_4096_D_KN)
dnscrypt.pl/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (51.38.99.90, 2001:41d0:701:1100::66c, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
dnscrypt.pl/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (79.98.145.34, UDP_-_EDNS0_512_D_KN)
dnscrypt.pl/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (51.38.99.90, 2001:41d0:701:1100::66c, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
dnscrypt.pl/NS: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (79.98.145.34, TCP_-_EDNS0_4096_D_KN)
dnscrypt.pl/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (51.38.99.90, 2001:41d0:701:1100::66c, UDP_-_NOEDNS_)
dnscrypt.pl/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (79.98.145.34, TCP_-_EDNS0_4096_D_N)
dnscrypt.pl/SOA: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (79.98.145.34, TCP_-_EDNS0_4096_D_KN_0x20)
dnscrypt.pl/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (51.38.99.90, 2001:41d0:701:1100::66c, TCP_-_NOEDNS_)
dnscrypt.pl/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (51.38.99.90, 2001:41d0:701:1100::66c, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
dnscrypt.pl/TXT: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (79.98.145.34, TCP_-_EDNS0_4096_D_N)
dnscrypt.pl/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (51.38.99.90, 2001:41d0:701:1100::66c, UDP_-_NOEDNS_)
pl to dnscrypt.pl: 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.
dnscrypt.pl/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
xo3l2gctmu.dnscrypt.pl/A has errors; select the "Denial of existence" DNSSEC option to see them.
dnscrypt.pl/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
dnscrypt.pl/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
dnscrypt.pl/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (15)
RRSIG dnscrypt.pl/A alg 5, id 1651: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG dnscrypt.pl/A alg 7, id 1802: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG dnscrypt.pl/MX alg 5, id 1651: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG dnscrypt.pl/MX alg 7, id 1802: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG dnscrypt.pl/SOA alg 5, id 1651: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG dnscrypt.pl/SOA alg 7, id 1802: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
dnscrypt.pl/DS (alg 5, id 65416): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
dnscrypt.pl/DS (alg 5, id 65416): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
dnscrypt.pl/DS (alg 5, id 65416): 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.
dnscrypt.pl/DS (alg 5, id 65416): 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.
dnscrypt.pl/DS (alg 5, id 65416): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
dnscrypt.pl/DS (alg 5, id 65416): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
dnscrypt.pl/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
dnscrypt.pl/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
dnscrypt.pl/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.