NSEC3 proving non-existence of devk.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 devk.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (4)
NSEC3 proving non-existence of devk.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of devk.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
de to devk.de: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the de zone): ns2.vodafone-ip.de See RFC 1034, Sec. 4.2.2.
de to devk.de: The following NS name(s) were found in the delegation NS RRset (i.e., in the de zone), but not in the authoritative NS RRset: ns1.arcor-ip.de See RFC 1034, Sec. 4.2.2.