NSEC3 proving non-existence of in.ua/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 in.ua/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 in.ua/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 in.ua/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 in.ua/DS: No NSEC3 RR matches the SNAME (in.ua). See RFC 5155, Sec. 8.6.
NSEC3 proving non-existence of in.ua/DS: No NSEC3 RR matches the SNAME (in.ua). See RFC 5155, Sec. 8.6.
dej.in.ua/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2a01:3f1:c001::53, UDP_-_NOEDNS_)
Warnings (4)
NSEC3 proving non-existence of in.ua/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of in.ua/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of in.ua/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of in.ua/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.