View on GitHub

DNSViz: A DNS visualization tool

dxdt.ru

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

RRset statusRRset status

Secure (5)
  • dxdt.ru/A
  • dxdt.ru/MX
  • dxdt.ru/NS
  • dxdt.ru/SOA
  • dxdt.ru/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • dxdt.ru/DNSKEY (alg 5, id 4737)
  • dxdt.ru/DNSKEY (alg 5, id 61438)
  • dxdt.ru/DNSKEY (alg 8, id 7306)
  • dxdt.ru/DS (alg 5, id 61438)
  • ru/DNSKEY (alg 8, id 51699)
  • ru/DNSKEY (alg 8, id 7729)
  • ru/DS (alg 8, id 7729)

Delegation statusDelegation status

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

NoticesNotices

Errors (8)
  • RRSIG dxdt.ru/SOA alg 8, id 7306: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG dxdt.ru/SOA alg 8, id 7306: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG dxdt.ru/SOA alg 8, id 7306: 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 UDP. See RFC 1035, Sec. 4.2. (2001:678:14:0:193:232:156:17)
  • zl8uybxvck.dxdt.ru/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • dxdt.ru/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • dxdt.ru/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • dxdt.ru/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (22)
  • RRSIG dxdt.ru/A alg 5, id 61438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dxdt.ru/DNSKEY alg 5, id 4737: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dxdt.ru/DNSKEY alg 5, id 4737: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dxdt.ru/DNSKEY alg 5, id 4737: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dxdt.ru/DNSKEY alg 5, id 61438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dxdt.ru/DNSKEY alg 5, id 61438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dxdt.ru/DNSKEY alg 5, id 61438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dxdt.ru/MX alg 5, id 61438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dxdt.ru/NS alg 5, id 61438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dxdt.ru/SOA alg 5, id 4737: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dxdt.ru/TXT alg 5, id 61438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • dxdt.ru/DNSKEY (alg 5, id 4737): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (46.137.158.193, UDP_-_EDNS0_4096_D_KN)
  • dxdt.ru/DNSKEY (alg 5, id 61438): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (46.137.158.193, UDP_-_EDNS0_4096_D_KN)
  • dxdt.ru/DNSKEY (alg 8, id 7306): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (46.137.158.193, UDP_-_EDNS0_4096_D_KN)
  • dxdt.ru/DS (alg 5, id 61438): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dxdt.ru/DS (alg 5, id 61438): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dxdt.ru/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (46.137.158.193, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • dxdt.ru/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • zl8uybxvck.dxdt.ru/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dxdt.ru/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dxdt.ru/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dxdt.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