NSEC3 proving non-existence of rodier.me/A: 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 rodier.me/A: 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 rodier.me/AAAA: 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 rodier.me/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
me zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:500:54::1)
me/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
NSEC3 proving non-existence of rodier.me/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of rodier.me/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of rodier.me/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of rodier.me/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
me/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.