NSEC3 proving non-existence of ofcm.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 ofcm.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
ofcm.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
NSEC3 proving non-existence of ofcm.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of ofcm.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
gov to ofcm.gov: Authoritative AAAA records exist for ns-01.noaa.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
gov to ofcm.gov: Authoritative AAAA records exist for ns-02.noaa.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
gov to ofcm.gov: Authoritative AAAA records exist for ns-03.noaa.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
gov to ofcm.gov: The glue address(es) for ns-02.noaa.gov (137.75.116.93) differed from its authoritative address(es) (137.75.112.7). See RFC 1034, Sec. 4.2.2.
ofcm.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.