View on GitHub

DNSViz: A DNS visualization tool

ng.mil

« 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 (2)
  • ng.mil/NS
  • ng.mil/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • mil/DNSKEY (alg 8, id 27165)
  • mil/DNSKEY (alg 8, id 7765)
  • mil/DS (alg 8, id 7765)
  • mil/DS (alg 8, id 7765)
  • ng.mil/DNSKEY (alg 8, id 26238)
  • ng.mil/DNSKEY (alg 8, id 44854)
  • ng.mil/DNSKEY (alg 8, id 48369)
  • ng.mil/DNSKEY (alg 8, id 6460)
  • ng.mil/DS (alg 8, id 6460)
  • ng.mil/DS (alg 8, id 6460)

Delegation statusDelegation status

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

NoticesNotices

Errors (6)
  • ng.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • ng.mil/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • ng.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • 7g0puj8xt2.ng.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ng.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • ng.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (15)
  • mil to ng.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: ns01.army.mil See RFC 1034, Sec. 4.2.2.
  • mil/DS (alg 8, id 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 7765): 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.
  • mil/DS (alg 8, id 7765): 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.
  • ng.mil/DS (alg 8, id 6460): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ng.mil/DS (alg 8, id 6460): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ng.mil/DS (alg 8, id 6460): 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.
  • ng.mil/DS (alg 8, id 6460): 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.
  • ng.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ng.mil/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ng.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 7g0puj8xt2.ng.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ng.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ng.mil/A 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