View on GitHub

DNSViz: A DNS visualization tool

uni-stuttgart.de

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

RRset statusRRset status

Bogus (2)
  • uni-stuttgart.de/NSEC3PARAM (NODATA)
  • uni-stuttgart.de/SOA
Secure (7)
  • uni-stuttgart.de/A
  • uni-stuttgart.de/AAAA
  • uni-stuttgart.de/MX
  • uni-stuttgart.de/NS
  • uni-stuttgart.de/NSEC3PARAM
  • uni-stuttgart.de/SOA
  • uni-stuttgart.de/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • ./DNSKEY (alg 8, id 9799)
  • de/DNSKEY (alg 8, id 26755)
  • de/DNSKEY (alg 8, id 9795)
  • de/DS (alg 8, id 26755)
  • uni-stuttgart.de/DNSKEY (alg 10, id 26499)
  • uni-stuttgart.de/DNSKEY (alg 10, id 42872)
  • uni-stuttgart.de/DS (alg 10, id 26499)

Delegation statusDelegation status

Secure (2)
  • . to de
  • de to uni-stuttgart.de

NoticesNotices

Errors (14)
  • de to uni-stuttgart.de: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.69.252.34, 2001:7c0:7c0:1::babe:face, UDP_-_EDNS0_4096_D_KN)
  • de to uni-stuttgart.de: The DS RRset for the zone included algorithm 10 (RSASHA512), but no DS RR matched a DNSKEY with algorithm 10 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.69.252.34, 2001:7c0:7c0:1::babe:face, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (129.69.252.34, 2001:7c0:7c0:1::babe:face, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (129.69.252.34, 2001:7c0:7c0:1::babe:face, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/DNSKEY (alg 10, id 26499): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (129.69.252.34, 2001:7c0:7c0:1::babe:face, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/DNSKEY (alg 10, id 42872): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (129.69.252.34, 2001:7c0:7c0:1::babe:face, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (129.69.252.34, 2001:7c0:7c0:1::babe:face, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • uni-stuttgart.de/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (129.69.252.34, 2001:7c0:7c0:1::babe:face, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/NSEC3PARAM (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (129.69.252.34, 2001:7c0:7c0:1::babe:face, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (129.69.252.34, 2001:7c0:7c0:1::babe:face, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • uni-stuttgart.de/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (129.69.252.34, 2001:7c0:7c0:1::babe:face, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 5gzrb73ano.uni-stuttgart.de/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • uni-stuttgart.de/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
  • RRSIG uni-stuttgart.de/A alg 10, id 42872: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG uni-stuttgart.de/AAAA alg 10, id 42872: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG uni-stuttgart.de/DNSKEY alg 10, id 26499: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG uni-stuttgart.de/DNSKEY alg 10, id 26499: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG uni-stuttgart.de/DNSKEY alg 10, id 42872: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG uni-stuttgart.de/DNSKEY alg 10, id 42872: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG uni-stuttgart.de/MX alg 10, id 42872: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG uni-stuttgart.de/NS alg 10, id 42872: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG uni-stuttgart.de/NSEC3PARAM alg 10, id 42872: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG uni-stuttgart.de/SOA alg 10, id 42872: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG uni-stuttgart.de/TXT alg 10, id 42872: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • uni-stuttgart.de/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 5gzrb73ano.uni-stuttgart.de/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uni-stuttgart.de/DNSKEY 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