View on GitHub

DNSViz: A DNS visualization tool

uni-bayreuth.de

Updated: 2025-03-27 13:25:49 UTC (84 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (5)
  • uni-bayreuth.de/A
  • uni-bayreuth.de/MX
  • uni-bayreuth.de/NS
  • uni-bayreuth.de/SOA
  • uni-bayreuth.de/TXT
Secure (1)
  • de/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26470)
  • ./DNSKEY (alg 8, id 38696)
  • ./DNSKEY (alg 8, id 53148)
  • NSEC3 proving non-existence of uni-bayreuth.de/DS
  • de/DNSKEY (alg 8, id 26755)
  • de/DNSKEY (alg 8, id 34356)
  • de/DS (alg 8, id 26755)

Delegation statusDelegation status

Insecure (1)
  • de to uni-bayreuth.de
Secure (1)
  • . to de

NoticesNotices

Errors (19)
  • NSEC3 proving non-existence of uni-bayreuth.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of uni-bayreuth.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • uni-bayreuth.de zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (132.180.15.4)
  • uni-bayreuth.de zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (132.180.15.4)
  • uni-bayreuth.de/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (132.180.15.4, UDP_-_NOEDNS_)
  • uni-bayreuth.de/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (132.180.15.4, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • uni-bayreuth.de/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (132.180.15.4, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • uni-bayreuth.de/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (132.180.15.4, UDP_-_NOEDNS_)
  • uni-bayreuth.de/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (132.180.15.4, TCP_-_NOEDNS_)
  • uni-bayreuth.de/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (132.180.15.4, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • uni-bayreuth.de/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (132.180.15.4, UDP_-_NOEDNS_)
  • uni-bayreuth.de/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • uni-bayreuth.de/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • uni-bayreuth.de/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • xim2g.pq1a2.uni-bayreuth.de/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • uni-bayreuth.de/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • uni-bayreuth.de/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • uni-bayreuth.de/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • uni-bayreuth.de/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • NSEC3 proving non-existence of uni-bayreuth.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of uni-bayreuth.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • uni-bayreuth.de/DS 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