NSEC3 proving non-existence of tu-berlin.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-berlin.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
tu-berlin.de zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (130.149.7.7, 2001:638:809:7::7)
tu-berlin.de/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (130.149.7.7, 2001:638:809:7::7, UDP_-_NOEDNS_)
tu-berlin.de/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (130.149.7.7, 2001:638:809:7::7, UDP_-_NOEDNS_)
tu-berlin.de/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
NSEC3 proving non-existence of tu-berlin.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of tu-berlin.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
tu-berlin.de/DS has warnings; select the "Denial of existence" DNSSEC option to see them.