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

Bogus (6)
  • osd.mil/MX
  • osd.mil/NS
  • osd.mil/NSEC3PARAM
  • osd.mil/SOA
  • osd.mil/SOA
  • osd.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • mil/DNSKEY (alg 8, id 16801)
  • mil/DNSKEY (alg 8, id 29059)
  • mil/DNSKEY (alg 8, id 49404)
  • mil/DS (alg 8, id 16801)
  • osd.mil/DS (alg 8, id 49051)
Non_existent (2)
  • osd.mil/DNSKEY (alg 8, id 24975)
  • osd.mil/DNSKEY (alg 8, id 49051)

Delegation statusDelegation status

Bogus (1)
  • mil to osd.mil
Secure (1)
  • . to mil

NoticesNotices

Errors (18)
  • 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.
  • mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (199.252.155.234, 199.252.157.234, 199.252.162.234)
  • mil/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.157.234, TCP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY: No response was received from the server over TCP (tried 9 times). See RFC 1035, Sec. 4.2. (199.252.155.234, 199.252.162.234, TCP_-_EDNS0_4096_D_N)
  • osd.mil/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.47.75, TCP_-_EDNS0_4096_D_KN)
  • osd.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.47.11, 214.14.133.11, UDP_-_NOEDNS_)
  • osd.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.47.11, 199.252.47.75, 214.14.133.11, UDP_-_EDNS0_512_D_KN)
  • osd.mil/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.47.11, 214.14.133.11, UDP_-_NOEDNS_)
  • osd.mil/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.47.11, 199.252.47.75, 214.14.133.11, UDP_-_EDNS0_512_D_KN)
  • osd.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (214.14.133.11, UDP_-_NOEDNS_)
  • osd.mil/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (214.14.133.11, UDP_-_NOEDNS_)
  • osd.mil/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.47.11, 214.14.133.11, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • osd.mil/TXT: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (214.14.133.11, TCP_-_EDNS0_4096_D)
  • c43twzdufi.osd.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • 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.
  • osd.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • osd.mil/DS (alg 8, id 49051): 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 49051): 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 49051): 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 49051): 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/SOA: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (199.252.47.11, UDP_-_EDNS0_4096_D_KN)
  • osd.mil/SOA: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (199.252.47.75, UDP_-_EDNS0_4096_D_KN)
  • osd.mil/TXT: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (199.252.47.11, UDP_-_EDNS0_4096_D_KN)
  • osd.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • c43twzdufi.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