tu-dresden.de | DNSViz

tu-dresden.de

Updated: 2022-04-28 22:03:23 UTC (789 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Insecure (5)

tu-dresden.de/A
tu-dresden.de/MX
tu-dresden.de/NS
tu-dresden.de/SOA
tu-dresden.de/TXT

Secure (1)

de/SOA

DNSKEY/DS/NSEC status

Secure (6)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 47671)
NSEC3 proving non-existence of tu-dresden.de/DS
de/DNSKEY (alg 8, id 26755)
de/DNSKEY (alg 8, id 28599)
de/DS (alg 8, id 26755)

Delegation status

Insecure (1)

de to tu-dresden.de

Secure (1)

. to de

Notices

Errors (3)

NSEC3 proving non-existence of tu-dresden.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 tu-dresden.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
tu-dresden.de/DS has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (3)

NSEC3 proving non-existence of tu-dresden.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of tu-dresden.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
tu-dresden.de/DS has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend

	SEP bit set
	Revoke bit set
	Trust anchor

See also

DNSSEC Debugger by Verisign Labs.

Download: png | svg

Warning

JavaScript is required to make the graph below interactive.

DNSSEC authentication graph