View on GitHub

DNSViz: A DNS visualization tool

mail.mil

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

RRset statusRRset status

Secure (4)
  • mail.mil/MX
  • mail.mil/NS
  • mail.mil/SOA
  • mail.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • mail.mil/DNSKEY (alg 8, id 28882)
  • mail.mil/DNSKEY (alg 8, id 37117)
  • mail.mil/DNSKEY (alg 8, id 40044)
  • mail.mil/DS (alg 8, id 37117)
  • mail.mil/DS (alg 8, id 37117)
  • mil/DNSKEY (alg 8, id 24363)
  • mil/DNSKEY (alg 8, id 35118)
  • mil/DNSKEY (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)

Delegation statusDelegation status

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

NoticesNotices

Errors (21)
  • . to 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. (199.252.162.234, TCP_-_NOEDNS_)
  • . to mil: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.252.162.234, TCP_-_NOEDNS_)
  • mail.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (214.3.125.233)
  • mail.mil/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.162.234, UDP_-_NOEDNS_)
  • mail.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (214.3.125.233, UDP_-_NOEDNS_)
  • mil zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (199.252.154.234)
  • mil zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (199.252.162.234)
  • mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.252.155.234, 199.252.157.234, 199.252.180.234)
  • mil/DNSKEY (alg 8, id 24363): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (199.252.162.234, TCP_-_NOEDNS_)
  • mil/DNSKEY (alg 8, id 24363): No response was received from the server over UDP (tried 11 times) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (199.252.162.234, UDP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY (alg 8, id 35118): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (199.252.162.234, TCP_-_NOEDNS_)
  • mil/DNSKEY (alg 8, id 35118): No response was received from the server over UDP (tried 11 times) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (199.252.162.234, UDP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY (alg 8, id 51349): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (199.252.162.234, TCP_-_NOEDNS_)
  • mil/DNSKEY (alg 8, id 51349): No response was received from the server over UDP (tried 11 times) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (199.252.162.234, UDP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.154.234, UDP_-_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.154.234, 199.252.162.234, UDP_-_EDNS0_512_D_KN)
  • mail.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • mail.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • xqt7lwvoya.mail.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • mail.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • mail.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
  • mail.mil/DS (alg 8, id 37117): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mail.mil/DS (alg 8, id 37117): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mail.mil/DS (alg 8, id 37117): 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.
  • mail.mil/DS (alg 8, id 37117): 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): 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.
  • mail.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • mail.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • xqt7lwvoya.mail.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • mail.mil/CNAME 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