View on GitHub

DNSViz: A DNS visualization tool

test.dyn.weberdns.de

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

RRset statusRRset status

Secure (2)
  • test.dyn.weberdns.de/A
  • test.dyn.weberdns.de/AAAA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • de/DNSKEY (alg 8, id 45580)
  • de/DNSKEY (alg 8, id 46428)
  • de/DS (alg 8, id 45580)
  • dyn.weberdns.de/DNSKEY (alg 10, id 45918)
  • dyn.weberdns.de/DNSKEY (alg 10, id 58340)
  • dyn.weberdns.de/DS (alg 10, id 45918)
  • weberdns.de/DNSKEY (alg 8, id 12528)
  • weberdns.de/DNSKEY (alg 8, id 3880)
  • weberdns.de/DS (alg 8, id 3880)

Delegation statusDelegation status

Secure (3)
  • . to de
  • de to weberdns.de
  • weberdns.de to dyn.weberdns.de

NoticesNotices

Errors (1)
  • dyn.weberdns.de/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • RRSIG dyn.weberdns.de/DNSKEY alg 10, id 45918: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dyn.weberdns.de/DNSKEY alg 10, id 45918: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dyn.weberdns.de/DNSKEY alg 10, id 58340: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dyn.weberdns.de/DNSKEY alg 10, id 58340: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG test.dyn.weberdns.de/A alg 10, id 58340: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG test.dyn.weberdns.de/AAAA alg 10, id 58340: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • dyn.weberdns.de/DNSKEY (alg 10, id 45918): 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. (2001:470:1f0b:16b0::a26:53, UDP_-_EDNS0_4096_D_K)
  • dyn.weberdns.de/DNSKEY (alg 10, id 58340): 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. (2001:470:1f0b:16b0::a26:53, UDP_-_EDNS0_4096_D_K)
  • test.dyn.weberdns.de/AAAA: 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. (2001:470:1f0b:16b0::a26:53, UDP_-_EDNS0_4096_D_K)
  • dyn.weberdns.de/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