yandex.ru
Updated:
2024-01-30 17:57:32 UTC (301 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (2)
- ru/SOA
- ru/SOA
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 (7)
- ./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)
Delegation status
Insecure (1)
- ru to yandex.ru
Secure (1)
- . to ru
Notices
Errors (11)
- 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.
- ru zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (193.232.156.17, 2001:678:14:0:193:232:156:17)
- ru zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (194.85.252.62)
- ru/DNSKEY: No response was received from the server over UDP (tried 10 times). See RFC 1035, Sec. 4.2. (2001:678:14:0:193:232:156:17, UDP_-_EDNS0_4096_D)
- ru/DNSKEY: No response was received from the server over UDP (tried 14 times). See RFC 1035, Sec. 4.2. (193.232.156.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. (193.232.128.6, 193.232.142.17, 194.190.124.17, UDP_-_EDNS0_512_D_KN)
- 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/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- yandex.ru/NS: 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::1, UDP_-_EDNS0_4096_D_KN)
- 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::1, UDP_-_EDNS0_4096_D_KN)
- yandex.ru/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
- yandex.ru/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
