army.mil
Updated:
2021-08-20 20:33:36 UTC (1239 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (9)
- army.mil/MX
- army.mil/NS
- army.mil/NSEC3PARAM
- army.mil/SOA
- army.mil/SOA
- 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 39879)
- 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 (7)
- army.mil/DNSKEY: No response was received from the server over TCP (tried 2 times). See RFC 1035, Sec. 4.2. (130.114.200.6, TCP_-_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, TCP_-_EDNS0_4096_D_N)
- army.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- n81u6pljbk.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 (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/NSEC3PARAM: 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. (130.114.200.6, 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. (130.114.200.6, UDP_-_EDNS0_4096_D_KN)
- mil to army.mil: The following NS name(s) were found in the delegation NS RRset (i.e., in the mil zone), but not in the authoritative NS RRset: ns03.army.mil See RFC 1034, Sec. 4.2.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): 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.
- n81u6pljbk.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.
