View on GitHub

DNSViz: A DNS visualization tool

ru.com

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 5613)
  • com/DNSKEY (alg 13, id 19718)
  • com/DNSKEY (alg 13, id 956)
  • com/DS (alg 13, id 19718)
  • ru.com/DNSKEY (alg 7, id 10879)
  • ru.com/DNSKEY (alg 7, id 30236)
  • ru.com/DNSKEY (alg 7, id 47229)
  • ru.com/DNSKEY (alg 7, id 4949)
  • ru.com/DNSKEY (alg 7, id 9257)
  • ru.com/DS (alg 7, id 30236)
  • ru.com/DS (alg 7, id 30236)

Delegation statusDelegation status

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

NoticesNotices

Errors (2)
  • ru.com/DS (alg 7, id 30236): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ru.com/DS (alg 7, id 30236): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
Warnings (18)
  • RRSIG ru.com/DNSKEY alg 7, id 30236: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ru.com/DNSKEY alg 7, id 30236: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ru.com/DNSKEY alg 7, id 30236: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ru.com/DNSKEY alg 7, id 30236: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ru.com/DNSKEY alg 7, id 30236: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ru.com/MX alg 7, id 47229: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ru.com/NS alg 7, id 47229: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ru.com/NSEC3PARAM alg 7, id 47229: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ru.com/SOA alg 7, id 4949: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ru.com/SOA alg 7, id 4949: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ru.com/TXT alg 7, id 47229: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • ru.com/DS (alg 7, id 30236): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • ru.com/DS (alg 7, id 30236): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • ru.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ru.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ru.com/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ru.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • rnqaiy0164.ru.com/A 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