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 (9)
  • osd.mil/MX
  • osd.mil/NS
  • osd.mil/NSEC3PARAM
  • osd.mil/SOA
  • osd.mil/SOA
  • osd.mil/SOA
  • osd.mil/SOA
  • osd.mil/SOA
  • osd.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • mil/DNSKEY (alg 8, id 56347)
  • mil/DNSKEY (alg 8, id 61224)
  • mil/DNSKEY (alg 8, id 6876)
  • mil/DS (alg 8, id 56347)
  • osd.mil/DNSKEY (alg 8, id 4192)
  • osd.mil/DNSKEY (alg 8, id 6468)
  • osd.mil/DS (alg 8, id 4192)
  • osd.mil/DS (alg 8, id 4192)
Non_existent (1)
  • osd.mil/DNSKEY (alg 8, id 30081)

Delegation statusDelegation status

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

NoticesNotices

Errors (11)
  • RRSIG osd.mil/DNSKEY alg 8, id 4192: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG osd.mil/DNSKEY alg 8, id 4192: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG osd.mil/DNSKEY alg 8, id 6468: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG osd.mil/DNSKEY alg 8, id 6468: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • mil to osd.mil: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (214.14.133.11, TCP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.143.234, UDP_-_EDNS0_512_D_KN)
  • osd.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • osd.mil/DNSKEY 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.
  • enjrs9yq6v.osd.mil/A 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 (8)
  • 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.
  • osd.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • enjrs9yq6v.osd.mil/A 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