View on GitHub

DNSViz: A DNS visualization tool

ofcm.gov

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • gov/DNSKEY (alg 8, id 6229)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • ofcm.gov/DNSKEY (alg 5, id 21022)
  • ofcm.gov/DNSKEY (alg 5, id 35661)
  • ofcm.gov/DNSKEY (alg 5, id 46293)
  • ofcm.gov/DS (alg 5, id 21022)
  • ofcm.gov/DS (alg 5, id 21022)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to ofcm.gov

NoticesNotices

Warnings (20)
  • 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 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/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/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/TXT alg 5, id 35661: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • ofcm.gov/DS (alg 5, id 21022): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ofcm.gov/DS (alg 5, id 21022): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ofcm.gov/DS (alg 5, id 21022): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • ofcm.gov/DS (alg 5, id 21022): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • 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.
  • cj987ige6m.ofcm.gov/A 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