army.mil
Updated:
2020-10-25 02:00:48 UTC (1544 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
DNSKEY/DS/NSEC status
Secure (14)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- army.mil/DNSKEY (alg 8, id 30256)
- army.mil/DNSKEY (alg 8, id 41133)
- army.mil/DNSKEY (alg 8, id 49608)
- army.mil/DNSKEY (alg 8, id 62140)
- army.mil/DNSKEY (alg 8, id 873)
- army.mil/DS (alg 8, id 62140)
- army.mil/DS (alg 8, id 62140)
- mil/DNSKEY (alg 8, id 11451)
- mil/DNSKEY (alg 8, id 3870)
- mil/DNSKEY (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
Delegation status
Secure (2)
- . to mil
- mil to army.mil
Notices
Errors (13)
- 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. (130.114.200.6, 140.153.43.44, 192.82.113.7)
- army.mil zone: There was an error resolving the following NS name(s) to address(es): ns03.army.mil
- army.mil/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (130.114.200.6, 140.153.43.44, 192.82.113.7, UDP_-_NOEDNS_)
- army.mil/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (130.114.200.6, 140.153.43.44, 192.82.113.7, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
- army.mil/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (130.114.200.6, 140.153.43.44, 192.82.113.7, UDP_-_NOEDNS_)
- army.mil/SOA: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (140.153.43.44, UDP_-_NOEDNS_)
- army.mil/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (130.114.200.6, 140.153.43.44, 192.82.113.7, TCP_-_NOEDNS_)
- army.mil/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (130.114.200.6, 140.153.43.44, 192.82.113.7, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- army.mil/TXT: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (140.153.43.44, 192.82.113.7, UDP_-_NOEDNS_)
- army.mil/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (130.114.200.6, UDP_-_NOEDNS_)
- s92e0dimwo.army.mil/A 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/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- 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.
- 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.
JavaScript is required to make the graph below interactive.
