View on GitHub

DNSViz: A DNS visualization tool

ku.de

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

RRset statusRRset status

Secure (5)
  • ku.de/A
  • ku.de/MX
  • ku.de/NS
  • ku.de/SOA
  • ku.de/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 38696)
  • ./DNSKEY (alg 8, id 46441)
  • ./DNSKEY (alg 8, id 53148)
  • de/DNSKEY (alg 8, id 25113)
  • de/DNSKEY (alg 8, id 26755)
  • de/DS (alg 8, id 26755)
  • ku.de/DNSKEY (alg 10, id 4487)
  • ku.de/DNSKEY (alg 10, id 47166)
  • ku.de/DS (alg 10, id 47166)

Delegation statusDelegation status

Secure (2)
  • . to de
  • de to ku.de

NoticesNotices

Errors (4)
  • ku.de zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:638:10b::ffff:ffff:7fa)
  • ku.de/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:638:10b::ffff:ffff:7fa, UDP_-_NOEDNS_)
  • ku.de/MX: No response was received from the server over UDP (tried 15 times). See RFC 1035, Sec. 4.2. (2001:638:d:b101::1, UDP_-_EDNS0_4096_D_KN)
  • ku.de/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:638:10b::ffff:ffff:7fa, UDP_-_NOEDNS_)
Warnings (22)
  • RRSIG ku.de/A alg 10, id 4487: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ku.de/DNSKEY alg 10, id 4487: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ku.de/DNSKEY alg 10, id 4487: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ku.de/DNSKEY alg 10, id 47166: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ku.de/DNSKEY alg 10, id 47166: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ku.de/MX alg 10, id 4487: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ku.de/NS alg 10, id 4487: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ku.de/SOA alg 10, id 4487: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ku.de/TXT alg 10, id 4487: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • ku.de/DNSKEY (alg 10, id 4487): 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:638:d:b101::1, UDP_-_EDNS0_4096_D_KN)
  • ku.de/DNSKEY (alg 10, id 47166): 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:638:d:b101::1, UDP_-_EDNS0_4096_D_KN)
  • ku.de/NS: 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:638:d:b101::1, UDP_-_EDNS0_4096_D_KN)
  • ku.de/SOA: No response was received from the server over UDP (tried 11 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (2001:638:d:b101::1, UDP_-_EDNS0_4096_D_KN)
  • ku.de/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. (2001:638:d:b101::1, UDP_-_EDNS0_4096_D_KN)
  • ku.de/TXT: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (2001:638:d:b101::1, UDP_-_EDNS0_4096_D_KN)
  • ku.de/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ku.de/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ku.de/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ku.de/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ejlud.y1o8w.ku.de/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ku.de/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ku.de/AAAA 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