View on GitHub

DNSViz: A DNS visualization tool

dren.net

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

RRset statusRRset status

Secure (4)
  • dren.net/MX
  • dren.net/NS
  • dren.net/SOA
  • dren.net/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • dren.net/DNSKEY (alg 10, id 17708)
  • dren.net/DNSKEY (alg 10, id 25698)
  • dren.net/DS (alg 10, id 25698)
  • dren.net/DS (alg 10, id 28488)
  • net/DNSKEY (alg 13, id 37331)
  • net/DNSKEY (alg 13, id 44222)
  • net/DNSKEY (alg 8, id 35886)
  • net/DNSKEY (alg 8, id 51464)
  • net/DS (alg 8, id 35886)
Non_existent (1)
  • dren.net/DNSKEY (alg 10, id 28488)

Delegation statusDelegation status

Secure (2)
  • . to net
  • net to dren.net

NoticesNotices

Warnings (16)
  • RRSIG dren.net/DNSKEY alg 10, id 17708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dren.net/DNSKEY alg 10, id 17708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dren.net/DNSKEY alg 10, id 25698: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dren.net/DNSKEY alg 10, id 25698: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dren.net/MX alg 10, id 17708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dren.net/NS alg 10, id 17708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dren.net/SOA alg 10, id 17708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dren.net/TXT alg 10, id 17708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • dren.net/DNSKEY (alg 10, id 17708): 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. (140.32.59.226, 140.32.61.226, UDP_-_EDNS0_4096_D_KN)
  • dren.net/DNSKEY (alg 10, id 25698): 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. (140.32.59.226, 140.32.61.226, UDP_-_EDNS0_4096_D_KN)
  • dren.net/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dren.net/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dren.net/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dren.net/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dren.net/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • rwve17gkcl.dren.net/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