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