yandex.com
Updated:
2023-12-02 23:50:58 UTC (790 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- yandex.com/A
- yandex.com/AAAA
- yandex.com/MX
- yandex.com/NS
- yandex.com/SOA
- yandex.com/TXT
Secure (1)
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- NSEC3 proving non-existence of yandex.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 63246)
- com/DS (alg 8, id 30909)
Non_existent (1)
- com/DNSKEY (alg 13, id 46171)
Delegation status
Insecure (1)
- com to yandex.com
Secure (1)
- . to com
Notices
Warnings (6)
- yandex.com/A: 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:0:1::1, UDP_-_EDNS0_4096_D_KN)
- yandex.com/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::1, UDP_-_EDNS0_4096_D_KN)
- yandex.com/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::1, UDP_-_EDNS0_4096_D_KN)
- yandex.com/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)
- cltokerp7h.yandex.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- yandex.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
