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 (1)
  • uni-stuttgart.de/NSEC3PARAM (NODATA)
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

Bogus (1)
  • NSEC proving non-existence of uni-stuttgart.de/NSEC3PARAM
Secure (9)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • de/DNSKEY (alg 8, id 26755)
  • de/DNSKEY (alg 8, id 54729)
  • de/DS (alg 8, id 26755)
  • uni-stuttgart.de/DNSKEY (alg 10, id 26499)
  • uni-stuttgart.de/DNSKEY (alg 10, id 28968)
  • uni-stuttgart.de/DS (alg 10, id 26499)

Delegation statusDelegation status

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

NoticesNotices

Errors (10)
  • NSEC proving non-existence of uni-stuttgart.de/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (129.143.2.10, 129.143.253.133, 2001:7c0::53:10, 2001:7c0:0:253::133, UDP_-_EDNS0_4096_D_KN)
  • NSEC proving non-existence of uni-stuttgart.de/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (129.143.2.10, 129.143.253.133, 2001:7c0::53:10, 2001:7c0:0:253::133, UDP_-_EDNS0_4096_D_KN)
  • NSEC proving non-existence of uni-stuttgart.de/NSEC3PARAM: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: uni-stuttgart.de/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
  • NSEC proving non-existence of uni-stuttgart.de/NSEC3PARAM: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: uni-stuttgart.de/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
  • uni-stuttgart.de/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (129.143.2.10, 129.143.253.133, 2001:7c0::53:10, 2001:7c0:0:253::133, UDP_-_EDNS0_512_D_KN)
  • uni-stuttgart.de/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (129.143.2.10, 129.143.253.133, 2001:7c0:0:253::133, UDP_-_EDNS0_512_D_KN)
  • uni-stuttgart.de/SOA: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (129.143.2.10, TCP_-_EDNS0_4096_D_N_0x20)
  • uni-stuttgart.de/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • r9m5u8osp3.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 (25)
  • RRSIG uni-stuttgart.de/A alg 10, id 28968: 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 28968: 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 28968: 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 28968: 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 28968: 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 28968: 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 28968: 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 28968: 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 28968: 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 28968: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • uni-stuttgart.de/AAAA: 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. (129.143.2.10, 2001:7c0::53:10, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/DNSKEY (alg 10, id 26499): 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. (129.143.2.10, 129.143.253.133, 2001:7c0::53:10, 2001:7c0:0:253::133, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/DNSKEY (alg 10, id 28968): 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. (129.143.2.10, 129.143.253.133, 2001:7c0::53:10, 2001:7c0:0:253::133, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/MX: 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. (129.143.2.10, 2001:7c0::53:10, 2001:7c0:0:253::133, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/MX: 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. (129.143.253.133, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/SOA: 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. (129.143.2.10, 129.143.253.133, 2001:7c0:0:253::133, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/SOA: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (129.143.2.10, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.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. (129.143.253.133, 2001:7c0::53:10, 2001:7c0:0:253::133, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • uni-stuttgart.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. (129.143.2.10, 2001:7c0::53:10, 2001:7c0:0:253::133, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/TXT: 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. (129.143.253.133, UDP_-_EDNS0_4096_D_KN)
  • uni-stuttgart.de/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • r9m5u8osp3.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