cctld.ru
Updated:
2024-01-30 17:03:05 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 (7)
- 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/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (193.232.142.17, 194.85.252.62, UDP_-_NOEDNS_)
- cctld.ru/NS: The TCP connection was interrupted (ECONNRESET). See RFC 1035, Sec. 4.2. (193.232.128.6, TCP_-_EDNS0_4096_D_N)
- 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)
- cctld.ru/DS has errors; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
