gov.ru
Updated:
2024-01-30 16:26:57 UTC (298 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (6)
- gov.ru/A
- gov.ru/MX
- gov.ru/NS
- gov.ru/NSEC3PARAM
- gov.ru/SOA
- gov.ru/TXT
DNSKEY/DS/NSEC status
Bogus (4)
- gov.ru/DNSKEY (alg 13, id 28029)
- gov.ru/DNSKEY (alg 13, id 39270)
- gov.ru/DNSKEY (alg 13, id 45988)
- gov.ru/DS (alg 13, id 28029)
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 (2)
- . to ru
- ru to gov.ru
Notices
Errors (25)
- . to ru: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (193.232.142.17, TCP_-_EDNS0_4096_)
- . to ru: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (193.232.142.17, TCP_-_EDNS0_4096_)
- RRSIG gov.ru/DS alg 8, id 52263: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- gov.ru zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (95.173.128.77, 193.232.66.15)
- gov.ru/DS (alg 13, id 28029): 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. (193.232.142.17, UDP_-_EDNS0_4096_)
- gov.ru/DS (alg 13, id 28029): 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. (193.232.142.17, UDP_-_EDNS0_4096_)
- gov.ru/DS (alg 13, id 28029): 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. (193.232.142.17, UDP_-_EDNS0_4096_D_KN)
- gov.ru/DS (alg 13, id 28029): 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. (193.232.142.17, UDP_-_EDNS0_4096_D_KN)
- gov.ru/DS (alg 13, id 28029): 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.142.17, UDP_-_EDNS0_4096_D_KN)
- gov.ru/DS (alg 13, id 28029): 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.142.17, UDP_-_EDNS0_4096_D_KN)
- gov.ru/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (95.173.128.77, TCP_-_EDNS0_4096_D_N)
- gov.ru/SOA: There was an error communicating with the server over TCP (UNKNOWN). See RFC 1035, Sec. 4.2. (193.232.66.15, TCP_-_EDNS0_4096_D_N)
- ru zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (193.232.128.6)
- ru/DNSKEY (alg 8, id 43786): 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. (193.232.142.17, TCP_-_EDNS0_4096_)
- ru/DNSKEY (alg 8, id 43786): 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. (193.232.142.17, UDP_-_EDNS0_4096_D_KN)
- ru/DNSKEY (alg 8, id 44301): 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. (193.232.142.17, TCP_-_EDNS0_4096_)
- ru/DNSKEY (alg 8, id 44301): 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. (193.232.142.17, UDP_-_EDNS0_4096_D_KN)
- ru/DNSKEY (alg 8, id 52263): 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. (193.232.142.17, TCP_-_EDNS0_4096_)
- ru/DNSKEY (alg 8, id 52263): 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. (193.232.142.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, 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.128.6, TCP_-_EDNS0_4096_D_KN)
- 2j0magscv6.gov.ru/A has errors; select the "Denial of existence" DNSSEC option to see them.
- gov.ru/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- gov.ru/DS has errors; select the "Denial of existence" DNSSEC option to see them.
- gov.ru/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- 2j0magscv6.gov.ru/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- gov.ru/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- gov.ru/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
