yandex.ru
Updated:
2024-02-29 23:04:18 UTC (267 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- yandex.ru/A
- yandex.ru/AAAA
- yandex.ru/MX
- yandex.ru/NS
- yandex.ru/SOA
- yandex.ru/TXT
Secure (1)
- ru/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./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 52263)
- ru/DS (alg 8, id 43786)
Delegation status
Insecure (1)
- ru to yandex.ru
Secure (1)
- . to ru
Notices
Errors (12)
- . to ru: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (194.190.124.17, UDP_-_EDNS0_4096_)
- . to ru: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (194.190.124.17, UDP_-_EDNS0_4096_)
- ru zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (194.190.124.17)
- ru/DNSKEY (alg 8, id 43786): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (194.190.124.17, UDP_-_EDNS0_4096_)
- ru/DNSKEY (alg 8, id 43786): No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (194.190.124.17, UDP_-_EDNS0_4096_D_KN)
- ru/DNSKEY (alg 8, id 43786): The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (194.190.124.17, UDP_-_EDNS0_4096_D_KN)
- ru/DNSKEY (alg 8, id 52263): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (194.190.124.17, UDP_-_EDNS0_4096_)
- ru/DNSKEY (alg 8, id 52263): No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (194.190.124.17, UDP_-_EDNS0_4096_D_KN)
- ru/DNSKEY (alg 8, id 52263): The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (194.190.124.17, UDP_-_EDNS0_4096_D_KN)
- ru/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (194.190.124.17, UDP_-_EDNS0_512_D_KN)
- yandex.ru/DNSKEY: 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/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
- yandex.ru/SOA: 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)
- 6fo8evnz5l.yandex.ru/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
