View on GitHub

DNSViz: A DNS visualization tool

stratcom.mil

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

RRset statusRRset status

Secure (3)
  • stratcom.mil/NS
  • stratcom.mil/SOA
  • stratcom.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • mil/DNSKEY (alg 8, id 48726)
  • mil/DNSKEY (alg 8, id 7765)
  • mil/DNSKEY (alg 8, id 8223)
  • mil/DS (alg 8, id 7765)
  • mil/DS (alg 8, id 7765)
  • stratcom.mil/DNSKEY (alg 8, id 19866)
  • stratcom.mil/DNSKEY (alg 8, id 42970)
  • stratcom.mil/DS (alg 8, id 42970)
  • stratcom.mil/DS (alg 8, id 42970)

Delegation statusDelegation status

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

NoticesNotices

Errors (6)
  • ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.112.36.4, UDP_-_EDNS0_512_D_K)
  • 3y46qwj785.stratcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • stratcom.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • stratcom.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • stratcom.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • stratcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
  • 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.
  • stratcom.mil/DS (alg 8, id 42970): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • stratcom.mil/DS (alg 8, id 42970): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • stratcom.mil/DS (alg 8, id 42970): 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.
  • stratcom.mil/DS (alg 8, id 42970): 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.
  • 3y46qwj785.stratcom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • stratcom.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • stratcom.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • stratcom.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • stratcom.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