army.mil
Updated:
2024-07-16 17:23:30 UTC (10 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- army.mil/MX
- army.mil/NS
- army.mil/NSEC3PARAM
- army.mil/SOA
- army.mil/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- army.mil/DNSKEY (alg 8, id 21310)
- army.mil/DNSKEY (alg 8, id 24096)
- army.mil/DNSKEY (alg 8, id 5058)
- army.mil/DNSKEY (alg 8, id 57390)
- 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 21018)
- mil/DNSKEY (alg 8, id 54036)
- mil/DS (alg 8, id 16801)
Delegation status
Secure (2)
- . to mil
- mil to army.mil
Notices
Errors (9)
- army.mil/CDNSKEY: 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/CDS: No response was received from the server over UDP (tried 16 times). See RFC 1035, Sec. 4.2. (140.153.43.44, UDP_-_NOEDNS_)
- army.mil/CDS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (130.114.200.6, 192.82.113.7, UDP_-_NOEDNS_)
- army.mil/DS (alg 8, id 21310): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- army.mil/DS (alg 8, id 21310): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- 7hbvc.z05fv.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/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 (9)
- 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.
- 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:4122:2:154::234, UDP_-_EDNS0_4096_D_KN)
- mil/DNSKEY (alg 8, id 21018): 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:4122:2:154::234, UDP_-_EDNS0_4096_D_KN)
- mil/DNSKEY (alg 8, id 54036): 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:4122:2:154::234, UDP_-_EDNS0_4096_D_KN)
- 7hbvc.z05fv.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/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
