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.
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/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (194.85.252.62, UDP_-_NOEDNS_)
cctld.ru/DS: There was an error communicating with the server over TCP (UNKNOWN). See RFC 1035, Sec. 4.2. (194.190.124.17, TCP_-_EDNS0_4096_D_N)
ru zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (2001:678:14:0:193:232:156:17)
ru zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (193.232.156.17)
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 12 times). See RFC 1035, Sec. 4.2. (194.85.252.62, UDP_-_NOEDNS_)
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.85.252.62, 2001:678:14:0:193:232:156:17, UDP_-_EDNS0_512_D_KN)
ru/DNSKEY: There was an error communicating with the server over TCP (UNKNOWN). See RFC 1035, Sec. 4.2. (193.232.156.17, TCP_-_EDNS0_4096_D)
cctld.ru/DS has errors; select the "Denial of existence" DNSSEC option to see them.