army.mil
Updated:
2020-03-22 21:55:50 UTC (1587 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (8)
- army.mil/A
- army.mil/AAAA
- army.mil/NS
- army.mil/SOA
- army.mil/SOA
- army.mil/SOA
- army.mil/SOA
- army.mil/SOA
DNSKEY/DS/NSEC status
Secure (14)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 33853)
- ./DNSKEY (alg 8, id 48903)
- army.mil/DNSKEY (alg 8, id 30256)
- army.mil/DNSKEY (alg 8, id 35230)
- army.mil/DNSKEY (alg 8, id 51378)
- army.mil/DNSKEY (alg 8, id 62274)
- army.mil/DS (alg 8, id 30256)
- army.mil/DS (alg 8, id 30256)
- mil/DNSKEY (alg 8, id 27165)
- mil/DNSKEY (alg 8, id 27843)
- mil/DNSKEY (alg 8, id 7765)
- mil/DS (alg 8, id 7765)
- mil/DS (alg 8, id 7765)
Delegation status
Secure (2)
- . to mil
- mil to army.mil
Notices
Errors (13)
- army.mil/A: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (130.114.200.6, 192.82.113.7, UDP_-_NOEDNS_)
- army.mil/A: No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (130.114.200.6, 192.82.113.7, UDP_-_EDNS0_4096_D_K)
- army.mil/A: 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, 192.82.113.7, UDP_-_EDNS0_4096_D_K)
- army.mil/DS (alg 8, id 30256): 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 30256): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- army.mil/NS: 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_-_NOEDNS_)
- mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.252.154.234)
- mil/DS (alg 8, id 7765): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/DS (alg 8, id 7765): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- army.mil/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
- army.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- two6vz83hm.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 30256): 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 30256): 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 7765): 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 7765): 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/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
- army.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- two6vz83hm.army.mil/A 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.
