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