army.mil
Updated:
2023-05-04 14:35:06 UTC (602 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset 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 status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- army.mil/DNSKEY (alg 8, id 16671)
- army.mil/DNSKEY (alg 8, id 22128)
- army.mil/DNSKEY (alg 8, id 559)
- army.mil/DS (alg 8, id 559)
- army.mil/DS (alg 8, id 559)
- mil/DNSKEY (alg 8, id 1773)
- mil/DNSKEY (alg 8, id 53035)
- mil/DNSKEY (alg 8, id 62470)
- mil/DS (alg 8, id 62470)
Delegation status
Secure (2)
- . to mil
- mil to army.mil
Notices
Errors (3)
- 0mcts3ke1u.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 (7)
- army.mil/DS (alg 8, id 559): 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 559): 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 559): 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 559): 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.
- 0mcts3ke1u.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.
