View on GitHub

DNSViz: A DNS visualization tool

ng.mil

Updated: 2023-02-08 20:17:00 UTC (432 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)
  • ng.mil/NS
  • ng.mil/NSEC3PARAM
  • ng.mil/SOA
  • ng.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • mil/DNSKEY (alg 8, id 55084)
  • mil/DNSKEY (alg 8, id 57763)
  • mil/DNSKEY (alg 8, id 62470)
  • mil/DS (alg 8, id 62470)
  • ng.mil/DNSKEY (alg 8, id 40056)
  • ng.mil/DNSKEY (alg 8, id 51354)
  • ng.mil/DNSKEY (alg 8, id 56860)
  • ng.mil/DNSKEY (alg 8, id 9022)
  • ng.mil/DS (alg 8, id 9022)
  • ng.mil/DS (alg 8, id 9022)

Delegation statusDelegation status

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

NoticesNotices

Warnings (4)
  • ng.mil/DS (alg 8, id 9022): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • ng.mil/DS (alg 8, id 9022): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • ng.mil/DS (alg 8, id 9022): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • ng.mil/DS (alg 8, id 9022): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.

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