196.in-addr.arpa to 253.41.196.in-addr.arpa: 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. (197.140.10.155, 197.140.11.1, UDP_-_EDNS0_4096_D_KN)
196.in-addr.arpa to 253.41.196.in-addr.arpa: 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. (197.140.10.155, 197.140.11.1, UDP_-_EDNS0_4096_D_KN)
253.41.196.in-addr.arpa zone: The following NS name(s) did not resolve to address(es): ns01icosnet
253.41.196.in-addr.arpa/MX has errors; select the "Denial of existence" DNSSEC option to see them.
253.41.196.in-addr.arpa/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
253.41.196.in-addr.arpa/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
1q0p43umsa.253.41.196.in-addr.arpa/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (17)
196.in-addr.arpa to 253.41.196.in-addr.arpa: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the 196.in-addr.arpa zone): ns01icosnet See RFC 1034, Sec. 4.2.2.
196.in-addr.arpa/DS (alg 8, id 17735): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
196.in-addr.arpa/DS (alg 8, id 17735): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
196.in-addr.arpa/DS (alg 8, id 17735): 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.
196.in-addr.arpa/DS (alg 8, id 17735): 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.
253.41.196.in-addr.arpa/DS (alg 8, id 18215): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
253.41.196.in-addr.arpa/DS (alg 8, id 18215): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
253.41.196.in-addr.arpa/DS (alg 8, id 18215): 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.
253.41.196.in-addr.arpa/DS (alg 8, id 18215): 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.
arpa/DS (alg 8, id 42581): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
arpa/DS (alg 8, id 42581): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
arpa/DS (alg 8, id 42581): 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.
arpa/DS (alg 8, id 42581): 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.
253.41.196.in-addr.arpa/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
253.41.196.in-addr.arpa/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
253.41.196.in-addr.arpa/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
1q0p43umsa.253.41.196.in-addr.arpa/A has warnings; select the "Denial of existence" DNSSEC option to see them.