army.mil
Updated:
2021-08-09 14:28:19 UTC (1231 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (1)
- army.mil/SOA
Secure (7)
- army.mil/MX
- army.mil/NS
- army.mil/NSEC3PARAM
- army.mil/SOA
- army.mil/SOA
- army.mil/SOA
- army.mil/TXT
DNSKEY/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 status
Secure (2)
- . to mil
- mil to army.mil
Notices
Errors (15)
- army.mil zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (192.82.113.7)
- army.mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (130.114.200.6)
- army.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (130.114.200.6, 192.82.113.7, UDP_-_EDNS0_4096_D_KN)
- army.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.82.113.7, UDP_-_EDNS0_512_D_KN)
- army.mil/SOA: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (130.114.200.6, UDP_-_EDNS0_4096__0x20)
- 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, 192.82.113.7, TCP_-_EDNS0_4096_D_N)
- army.mil/SOA: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (130.114.200.6, UDP_-_EDNS0_4096_D_KN_0x20)
- army.mil/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (130.114.200.6, UDP_-_NOEDNS_)
- army.mil/SOA: 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. (130.114.200.6, UDP_-_EDNS0_4096_D_KN_0x20)
- mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (199.252.154.234)
- army.mil/DNSKEY 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.
- army.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- eh8rioxs4q.army.mil/A 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 (15)
- 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/MX: 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. (192.82.113.7, UDP_-_EDNS0_4096_D_KN)
- army.mil/NSEC3PARAM: 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. (192.82.113.7, UDP_-_EDNS0_4096_D_KN)
- army.mil/SOA: 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. (192.82.113.7, UDP_-_EDNS0_4096_D_KN)
- army.mil/TXT: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (192.82.113.7, 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.
- 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.
JavaScript is required to make the graph below interactive.
