yandex.ru
Updated:
2022-09-21 05:26:12 UTC (799 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 (8)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- NSEC3 proving non-existence of yandex.ru/DS
- ru/DNSKEY (alg 8, id 33257)
- ru/DNSKEY (alg 8, id 33540)
- ru/DNSKEY (alg 8, id 53643)
- ru/DS (alg 8, id 33257)
Delegation status
Insecure (1)
- ru to yandex.ru
Secure (1)
- . to ru
Notices
Errors (7)
- NSEC3 proving non-existence of yandex.ru/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of yandex.ru/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- ru zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:678:14:0:193:232:156:17)
- yandex.ru zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:978:7401::78)
- yandex.ru/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:978:7401::78, UDP_-_NOEDNS_)
- yandex.ru/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:978:7401::78, UDP_-_NOEDNS_)
- yandex.ru/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- NSEC3 proving non-existence of yandex.ru/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of yandex.ru/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- yandex.ru/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
