View on GitHub

DNSViz: A DNS visualization tool

osd.mil

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

RRset statusRRset status

Secure (5)
  • osd.mil/MX
  • osd.mil/NS
  • osd.mil/SOA
  • osd.mil/SOA
  • osd.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • mil/DNSKEY (alg 8, id 46443)
  • mil/DNSKEY (alg 8, id 51349)
  • mil/DNSKEY (alg 8, id 9498)
  • mil/DS (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)
  • osd.mil/DNSKEY (alg 8, id 11701)
  • osd.mil/DNSKEY (alg 8, id 20244)
  • osd.mil/DNSKEY (alg 8, id 4192)
  • osd.mil/DNSKEY (alg 8, id 60090)
  • osd.mil/DS (alg 8, id 4192)
  • osd.mil/DS (alg 8, id 4192)

Delegation statusDelegation status

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

NoticesNotices

Errors (8)
  • RRSIG osd.mil/SOA alg 8, id 20244: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG osd.mil/SOA alg 8, id 20244: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG osd.mil/SOA alg 8, id 60090: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG osd.mil/SOA alg 8, id 60090: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • osd.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • tjd3rqfelu.osd.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • osd.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • osd.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
  • mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 51349): 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 51349): 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.
  • osd.mil/DS (alg 8, id 4192): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • osd.mil/DS (alg 8, id 4192): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • osd.mil/DS (alg 8, id 4192): 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.
  • osd.mil/DS (alg 8, id 4192): 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.
  • osd.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • tjd3rqfelu.osd.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • osd.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • osd.mil/AAAA 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