View on GitHub

DNSViz: A DNS visualization tool

dren.mil

Updated: 2024-03-06 17:03:17 UTC (44 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (4)
  • dren.mil/MX
  • dren.mil/NS
  • dren.mil/SOA
  • dren.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • dren.mil/DNSKEY (alg 13, id 14070)
  • dren.mil/DNSKEY (alg 13, id 60084)
  • dren.mil/DS (alg 13, id 60084)
  • dren.mil/DS (alg 13, id 60084)
  • mil/DNSKEY (alg 8, id 16801)
  • mil/DNSKEY (alg 8, id 29059)
  • mil/DNSKEY (alg 8, id 49404)
  • mil/DS (alg 8, id 16801)

Delegation statusDelegation status

Secure (2)
  • . to mil
  • mil to dren.mil

NoticesNotices

Warnings (6)
  • dren.mil/DS (alg 13, id 60084): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • dren.mil/DS (alg 13, id 60084): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • dren.mil/DS (alg 13, id 60084): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • dren.mil/DS (alg 13, id 60084): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • mil to dren.mil: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the mil zone): auth-sandiego.dren.mil
  • mil to dren.mil: The following NS name(s) were found in the delegation NS RRset (i.e., in the mil zone), but not in the authoritative NS RRset: auth-west.dren.mil

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