ofcm.gov
Updated:
2022-01-13 17:29:11 UTC (907 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (3)
- ofcm.gov/NS
- ofcm.gov/SOA
- ofcm.gov/TXT
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- ofcm.gov/DNSKEY (alg 8, id 11792)
- ofcm.gov/DNSKEY (alg 8, id 50923)
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- NSEC3 proving non-existence of ofcm.gov/DS
- gov/DNSKEY (alg 8, id 6229)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Insecure (1)
- gov to ofcm.gov
Secure (1)
- . to gov
Notices
Errors (3)
- 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.
JavaScript is required to make the graph below interactive.
