View on GitHub

DNSViz: A DNS visualization tool

godirect.gov

Updated: 2021-10-16 17:21:36 UTC (1149 days ago) Update now
« 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 (5)
  • godirect.gov/A
  • godirect.gov/MX
  • godirect.gov/NS
  • godirect.gov/SOA
  • godirect.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • godirect.gov/DNSKEY (alg 13, id 31317)
  • godirect.gov/DNSKEY (alg 13, id 53185)
  • godirect.gov/DNSKEY (alg 13, id 59163)
  • godirect.gov/DS (alg 13, id 31317)
  • godirect.gov/DS (alg 13, id 31317)
  • gov/DNSKEY (alg 8, id 57735)
  • gov/DNSKEY (alg 8, id 6229)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Warnings (4)
  • godirect.gov/DS (alg 13, id 31317): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • godirect.gov/DS (alg 13, id 31317): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • godirect.gov/DS (alg 13, id 31317): 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.
  • godirect.gov/DS (alg 13, id 31317): 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.

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