NSEC3 proving non-existence of yandex.ru/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 yandex.ru/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
ru zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:678:14:0:193:232:156:17)
yandex.ru zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:978:7401::78)
yandex.ru/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:978:7401::78, UDP_-_NOEDNS_)
yandex.ru/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:978:7401::78, UDP_-_NOEDNS_)
yandex.ru/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
NSEC3 proving non-existence of yandex.ru/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of yandex.ru/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
yandex.ru/MX: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2a02:6b8:0:1::1, UDP_-_EDNS0_4096_D_KN)
yandex.ru/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (2a02:6b8:0:1::1, UDP_-_EDNS0_4096_D_KN)
yandex.ru/DS has warnings; select the "Denial of existence" DNSSEC option to see them.