View on GitHub

DNSViz: A DNS visualization tool

army.mil

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • army.mil/DNSKEY (alg 8, id 2685)
  • army.mil/DNSKEY (alg 8, id 52329)
  • army.mil/DNSKEY (alg 8, id 62140)
  • army.mil/DS (alg 8, id 62140)
  • army.mil/DS (alg 8, id 62140)
  • 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)

Delegation statusDelegation status

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

NoticesNotices

Errors (19)
  • RRSIG army.mil/SOA alg 8, id 52329: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG army.mil/SOA alg 8, id 52329: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • army.mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (140.153.43.44)
  • army.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.153.43.44, UDP_-_EDNS0_4096_D_KN)
  • army.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_)
  • army.mil/NSEC3PARAM: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (140.153.43.44, UDP_-_NOEDNS_)
  • army.mil/NSEC3PARAM: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (140.153.43.44, UDP_-_EDNS0_4096_D_KN)
  • army.mil/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (140.153.43.44, UDP_-_EDNS0_4096_D_KN)
  • army.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (130.114.200.6, 140.153.43.44, 192.82.113.7, TCP_-_EDNS0_4096_D_N)
  • mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (199.252.154.234, 199.252.155.234, 199.252.157.234, 199.252.180.234)
  • mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.252.143.234)
  • mil/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.180.234, 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.154.234, UDP_-_EDNS0_512_D_KN)
  • army.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • dkuly3pw26.army.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • army.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • army.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • army.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • army.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (21)
  • army.mil/DS (alg 8, id 62140): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • army.mil/DS (alg 8, id 62140): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • army.mil/DS (alg 8, id 62140): 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.
  • army.mil/DS (alg 8, id 62140): 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.
  • army.mil/DS (alg 8, id 62140): 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.155.234, UDP_-_EDNS0_4096_D_KN)
  • army.mil/DS (alg 8, id 62140): 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.155.234, UDP_-_EDNS0_4096_D_KN)
  • army.mil/DS (alg 8, id 62140): 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.155.234, UDP_-_EDNS0_4096_D_KN)
  • army.mil/DS (alg 8, id 62140): 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.155.234, UDP_-_EDNS0_4096_D_KN)
  • army.mil/DS (alg 8, id 62140): 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.157.234, UDP_-_EDNS0_4096_D_KN)
  • army.mil/DS (alg 8, id 62140): 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.157.234, UDP_-_EDNS0_4096_D_KN)
  • army.mil/DS (alg 8, id 62140): 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.157.234, UDP_-_EDNS0_4096_D_KN)
  • army.mil/DS (alg 8, id 62140): 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.157.234, UDP_-_EDNS0_4096_D_KN)
  • 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.
  • dkuly3pw26.army.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • army.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • army.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • army.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • army.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