NSEC3 proving non-existence of vu.nl/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 vu.nl/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
vu.nl/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
NSEC3 proving non-existence of vu.nl/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of vu.nl/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
nl to vu.nl: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the nl zone): ns2.vu.nl, ns1.vu.nl See RFC 1034, Sec. 4.2.2.
nl to vu.nl: The following NS name(s) were found in the delegation NS RRset (i.e., in the nl zone), but not in the authoritative NS RRset: ns.vu.nl See RFC 1034, Sec. 4.2.2.
nl to vu.nl: The glue address(es) for ns.vu.nl (130.37.129.4) differed from its authoritative address(es) (130.37.129.4, 130.37.129.5). See RFC 1034, Sec. 4.2.2.
vu.nl/DS has warnings; select the "Denial of existence" DNSSEC option to see them.