yandex.ru

Updated: 2024-01-30 18:08:19 UTC (300 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 30903)
NSEC3 proving non-existence of yandex.ru/DS
ru/DNSKEY (alg 8, id 43786)
ru/DNSKEY (alg 8, id 44301)
ru/DNSKEY (alg 8, id 52263)
ru/DS (alg 8, id 43786)

RRSIG NSEC3 proving non-existence of yandex.ru/DS alg 8, id 52263: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG NSEC3 proving non-existence of yandex.ru/DS alg 8, id 52263: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG ru/SOA alg 8, id 52263: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG ru/SOA alg 8, id 52263: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
yandex.ru/DS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (193.232.142.17, UDP_-_NOEDNS_)
yandex.ru/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2a02:6b8::1, UDP_-_EDNS0_512_D_KN)
yandex.ru/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (193.232.142.17, UDP_-_NOEDNS_)
yandex.ru/DS has errors; select the "Denial of existence" DNSSEC option to see them.

yandex.ru/AAAA: 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/MX: 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/SOA: 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. (2a02:6b8::1, UDP_-_EDNS0_4096_D_KN)