View on GitHub

DNSViz: A DNS visualization tool

yandex.ru

Updated: 2024-08-25 18:45:04 UTC (24 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset 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 statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of yandex.ru/DS
  • ru/DNSKEY (alg 8, id 35739)
  • ru/DNSKEY (alg 8, id 43786)
  • ru/DS (alg 8, id 43786)

Delegation statusDelegation status

Insecure (1)
  • ru to yandex.ru
Secure (1)
  • . to ru

NoticesNotices

Errors (2)
  • 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 (12)
  • ./DNSKEY (alg 8, id 20038): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_512_D_KN)
  • ru/DS (alg 8, id 43786): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • ru/DS (alg 8, id 43786): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • yandex.ru/NS: 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.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:0:1::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, 2a02:6b8:0:1::1, UDP_-_EDNS0_4096_D_KN)
  • yandex.ru/TXT: 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/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • yandex.ru/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph