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 (4)
  • ofcm.gov/NS
  • ofcm.gov/SOA
  • 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 (18)
  • 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/DNSKEY (alg 5, id 21022): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (140.90.33.237, 140.172.17.237, 161.55.32.2, 2610:20:8000:8c00::237, 2610:20:8800:8c00::237, 2610:20:8c00:8c00::2, UDP_-_EDNS0_4096_D_KN)
  • ofcm.gov/DNSKEY (alg 5, id 30726): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (140.90.33.237, 140.172.17.237, 161.55.32.2, 2610:20:8000:8c00::237, 2610:20:8800:8c00::237, 2610:20:8c00:8c00::2, UDP_-_EDNS0_4096_D_KN)
  • ofcm.gov/DNSKEY (alg 5, id 35661): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (140.90.33.237, 140.172.17.237, 161.55.32.2, 2610:20:8000:8c00::237, 2610:20:8800:8c00::237, 2610:20:8c00:8c00::2, UDP_-_EDNS0_4096_D_KN)
  • ofcm.gov/DNSKEY (alg 5, id 46293): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (140.90.33.237, 140.172.17.237, 161.55.32.2, 2610:20:8000:8c00::237, 2610:20:8800:8c00::237, 2610:20:8c00:8c00::2, UDP_-_EDNS0_4096_D_KN)
  • ofcm.gov/DNSKEY (alg 8, id 50923): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (140.90.33.237, 140.172.17.237, 161.55.32.2, 2610:20:8000:8c00::237, 2610:20:8800:8c00::237, 2610:20:8c00:8c00::2, UDP_-_EDNS0_4096_D_KN)
  • ofcm.gov/NS: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (140.90.33.237, 140.172.17.237, 161.55.32.2, 2610:20:8000:8c00::237, 2610:20:8800:8c00::237, 2610:20:8c00:8c00::2, UDP_-_EDNS0_4096_D_KN)
  • ofcm.gov/SOA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (140.90.33.237, 140.172.17.237, 161.55.32.2, 2610:20:8000:8c00::237, 2610:20:8800:8c00::237, 2610:20:8c00:8c00::2, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ofcm.gov/TXT: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (140.90.33.237, 140.172.17.237, 161.55.32.2, 2610:20:8000:8c00::237, 2610:20:8800:8c00::237, 2610:20:8c00:8c00::2, UDP_-_EDNS0_4096_D_KN)
  • ofcm.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • ofcm.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • ofcm.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • ofcm.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • ofcm.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ofcm.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • ntm9yfd142.ofcm.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ofcm.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (54)
  • 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 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 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 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 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 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: 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): ns-02.noaa.gov, ns-01.noaa.gov, ns-03.noaa.gov See RFC 1034, Sec. 4.2.2.
  • ofcm.gov/DNSKEY (alg 8, id 11792): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (140.90.33.237, 140.172.17.237, 161.55.32.2, 2610:20:8000:8c00::237, 2610:20:8800:8c00::237, 2610:20:8c00:8c00::2, UDP_-_EDNS0_4096_D_KN)
  • 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.
  • 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.
  • ntm9yfd142.ofcm.gov/A 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