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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • army.mil/DNSKEY (alg 8, id 10959)
  • army.mil/DNSKEY (alg 8, id 21310)
  • army.mil/DNSKEY (alg 8, id 22125)
  • army.mil/DNSKEY (alg 8, id 39870)
  • army.mil/DS (alg 8, id 21310)
  • army.mil/DS (alg 8, id 21310)
  • mil/DNSKEY (alg 8, id 16801)
  • mil/DNSKEY (alg 8, id 25501)
  • mil/DNSKEY (alg 8, id 29059)
  • mil/DS (alg 8, id 16801)

Delegation statusDelegation status

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

NoticesNotices

Errors (9)
  • army.mil/DNSKEY: No response was received from the server over TCP (tried 1 times). See RFC 1035, Sec. 4.2. (140.153.43.44, TCP_-_EDNS0_4096_)
  • army.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (140.153.43.44, UDP_-_EDNS0_512_D_KN)
  • army.mil/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (140.153.43.44, 192.82.113.7, UDP_-_EDNS0_512_D_KN)
  • army.mil/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.153.43.44, UDP_-_NOEDNS_)
  • mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:4163:1:143::234)
  • army.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • mwcufkbret.army.mil/A 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/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
  • army.mil/A: 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. (192.82.113.7, UDP_-_EDNS0_4096_D_KN)
  • army.mil/A: 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. (130.114.200.6, UDP_-_EDNS0_4096_D_KN)
  • army.mil/DS (alg 8, id 21310): 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 21310): 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 21310): 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 21310): 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/NS: 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. (130.114.200.6, 192.82.113.7, UDP_-_EDNS0_4096_D_KN)
  • army.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. (140.153.43.44, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • mil/DNSKEY (alg 8, id 16801): 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. (2608:140:c:157::234, UDP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY (alg 8, id 25501): 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. (2608:140:c:157::234, UDP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY (alg 8, id 29059): 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. (2608:140:c:157::234, UDP_-_EDNS0_4096_D_KN)
  • mwcufkbret.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/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