View on GitHub

DNSViz: A DNS visualization tool

ofcm.gov

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (3)
  • ofcm.gov/NS
  • ofcm.gov/SOA
  • ofcm.gov/TXT
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (6)
  • ofcm.gov/DNSKEY (alg 5, id 21022)
  • ofcm.gov/DNSKEY (alg 5, id 30726)
  • ofcm.gov/DNSKEY (alg 5, id 35661)
  • ofcm.gov/DNSKEY (alg 5, id 46293)
  • ofcm.gov/DNSKEY (alg 8, id 11792)
  • ofcm.gov/DNSKEY (alg 8, id 50923)
Secure (8)
  • ./DNSKEY (alg 8, id 14748)
  • ./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 statusDelegation status

Insecure (1)
  • gov to ofcm.gov
Secure (1)
  • . to gov

NoticesNotices

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 (47)
  • 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.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 21022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 21022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 21022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 21022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 21022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 21022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 30726: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 30726: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 30726: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 30726: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 30726: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 30726: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 35661: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 35661: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 35661: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 35661: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 35661: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 35661: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 46293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 46293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 46293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 46293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 46293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/DNSKEY alg 5, id 46293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/NS alg 5, id 30726: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/NS alg 5, id 35661: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/NS alg 5, id 46293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/SOA alg 5, id 30726: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/SOA alg 5, id 35661: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/SOA alg 5, id 46293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/TXT alg 5, id 30726: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/TXT alg 5, id 35661: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ofcm.gov/TXT alg 5, id 46293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, 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/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ofcm.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ofcm.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 41w3c6byjd.ofcm.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ofcm.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ofcm.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ofcm.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ofcm.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph