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