NSEC3 proving non-existence of jyu.fi/DS: 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 jyu.fi/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
jyu.fi/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
NSEC3 proving non-existence of jyu.fi/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of jyu.fi/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
fi/DS (alg 8, id 35221): No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
fi/DS (alg 8, id 35221): No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
jyu.fi/DS has warnings; select the "Denial of existence" DNSSEC option to see them.