NSEC3 proving non-existence of 1.in-addr.arpa/TXT: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of 1.in-addr.arpa/TXT: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of 1.in-addr.arpa/TXT: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: 1.in-addr.arpa/TXT See RFC 5155, Sec. 8.5.
NSEC3 proving non-existence of 1.in-addr.arpa/TXT: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: 1.in-addr.arpa/TXT See RFC 5155, Sec. 8.5.
1.in-addr.arpa/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
1.in-addr.arpa/MX has errors; select the "Denial of existence" DNSSEC option to see them.
hzt3pfyliv.1.in-addr.arpa/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
NSEC3 proving non-existence of 1.in-addr.arpa/TXT: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of 1.in-addr.arpa/TXT: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
1.in-addr.arpa/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
1.in-addr.arpa/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
hzt3pfyliv.1.in-addr.arpa/A has warnings; select the "Denial of existence" DNSSEC option to see them.