View on GitHub

DNSViz: A DNS visualization tool

gov.ru

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (6)
  • gov.ru/A
  • gov.ru/MX
  • gov.ru/NS
  • gov.ru/NSEC3PARAM
  • gov.ru/SOA
  • gov.ru/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • gov.ru/DNSKEY (alg 13, id 28029)
  • gov.ru/DNSKEY (alg 13, id 39270)
  • gov.ru/DS (alg 13, id 28029)
  • ru/DNSKEY (alg 8, id 43786)
  • ru/DNSKEY (alg 8, id 52263)
  • ru/DS (alg 8, id 43786)

Delegation statusDelegation status

Secure (2)
  • . to ru
  • ru to gov.ru

NoticesNotices

Errors (19)
  • gov.ru zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (193.232.82.15, 2001:6d0:ffd7:0:193:232:82:15)
  • gov.ru zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (193.232.82.15, 2001:6d0:ffd7:0:193:232:82:15)
  • gov.ru zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (95.173.128.77)
  • gov.ru zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:6d0:ffd6:0:194:85:84:15)
  • gov.ru/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:6d0:ffd6:0:194:85:84:15, UDP_-_NOEDNS_)
  • gov.ru/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.232.82.15, 2001:6d0:ffd7:0:193:232:82:15, UDP_-_EDNS0_4096_D_KN)
  • gov.ru/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.232.82.15, 2001:6d0:ffd7:0:193:232:82:15, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov.ru/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.232.82.15, 2001:6d0:ffd7:0:193:232:82:15, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov.ru/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:6d0:ffd6:0:194:85:84:15, UDP_-_NOEDNS_)
  • gov.ru/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.232.82.15, 2001:6d0:ffd7:0:193:232:82:15, UDP_-_EDNS0_4096_D_KN)
  • gov.ru/NSEC3PARAM: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.232.82.15, 2001:6d0:ffd7:0:193:232:82:15, 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: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.232.82.15, 2001:6d0:ffd7:0:193:232:82:15, TCP_-_EDNS0_4096_D_N)
  • gov.ru/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.232.82.15, 2001:6d0:ffd7:0:193:232:82:15, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • gov.ru/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.232.82.15, 2001:6d0:ffd7:0:193:232:82:15, UDP_-_EDNS0_4096_D_KN)
  • gov.ru/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • jo67eu9h0s.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/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • jo67eu9h0s.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.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph