ru
Updated:
2024-01-30 16:37:38 UTC (298 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (3)
- ru/NS
- ru/NSEC3PARAM
- ru/SOA
DNSKEY/DS/NSEC status
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
Secure (1)
- . to ru
Notices
Errors (11)
- RRSIG ru/NS alg 8, id 52263: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- RRSIG ru/NSEC3PARAM 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.
- ru zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (193.232.128.6, 2001:678:15:0:193:232:142:17, 2001:678:17:0:193:232:128:6)
- ru/DNSKEY: No response was received from the server over UDP (tried 11 times). See RFC 1035, Sec. 4.2. (194.85.252.62, UDP_-_EDNS0_4096_D_KN)
- ru/DNSKEY: The TCP connection was interrupted (ECONNRESET). See RFC 1035, Sec. 4.2. (193.232.128.6, TCP_-_EDNS0_4096_D_KN)
- ru/SOA: The TCP connection was interrupted (ECONNRESET). See RFC 1035, Sec. 4.2. (193.232.128.6, TCP_-_EDNS0_4096_D_N)
- ru/SOA: There was an error communicating with the server over TCP (UNKNOWN). See RFC 1035, Sec. 4.2. (2001:678:15:0:193:232:142:17, 2001:678:17:0:193:232:128:6, TCP_-_EDNS0_4096_D_N)
- wpfmokrz0a.ru/A has errors; select the "Denial of existence" DNSSEC option to see them.
- ru/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- ru/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- ru/DNSKEY (alg 8, id 43786): No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (193.232.142.17, UDP_-_EDNS0_4096_D_KN)
- ru/DNSKEY (alg 8, id 44301): No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (193.232.142.17, UDP_-_EDNS0_4096_D_KN)
- ru/DNSKEY (alg 8, id 52263): No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (193.232.142.17, UDP_-_EDNS0_4096_D_KN)
- ru/NSEC3PARAM: 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. (194.85.252.62, UDP_-_EDNS0_4096_D_KN)
- ru/NSEC3PARAM: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (193.232.156.17, UDP_-_EDNS0_4096_D_KN)
- ru/SOA: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (193.232.156.17, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- ru/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- ru/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
