cctld.ru
Updated:
2024-01-30 17:05:47 UTC (299 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (6)
- cctld.ru/A
- cctld.ru/MX
- cctld.ru/NS
- cctld.ru/SOA
- cctld.ru/TXT
- ru/SOA
DNSKEY/DS/NSEC status
Bogus (1)
- NSEC3 proving non-existence of cctld.ru/DS
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- 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 cctld.ru
Secure (1)
- . to ru
Notices
Errors (13)
- RRSIG NSEC3 proving non-existence of cctld.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 cctld.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.
- cctld.ru/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (193.232.142.17, UDP_-_NOEDNS_)
- cctld.ru/NS: There was an error communicating with the server over TCP (UNKNOWN). See RFC 1035, Sec. 4.2. (193.232.128.6, TCP_-_EDNS0_4096_D_N)
- ru to cctld.ru: 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. (2001:678:14:0:193:232:156:17, UDP_-_EDNS0_4096_)
- ru to cctld.ru: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (193.232.156.17, UDP_-_NOEDNS_)
- ru to cctld.ru: 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. (2001:678:14:0:193:232:156:17, UDP_-_EDNS0_4096_D_KN)
- ru to cctld.ru: No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (193.232.156.17, UDP_-_EDNS0_4096_D_KN)
- ru to cctld.ru: 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. (193.232.156.17, 2001:678:14:0: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.142.17, UDP_-_EDNS0_512_D_KN)
- ru/SOA: 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. (193.232.156.17, 2001:678:14:0:193:232:156:17, UDP_-_EDNS0_4096_D_KN)
- cctld.ru/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
- ru to cctld.ru: 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. (193.232.142.17, 194.85.252.62, UDP_-_EDNS0_4096_D_KN)
- cctld.ru/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
