army.mil
Updated:
2021-08-07 05:30:08 UTC (1019 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (12)
- 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/SOA
- army.mil/SOA
- army.mil/SOA
- army.mil/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- army.mil/DS (alg 8, id 62140)
- mil/DNSKEY (alg 8, id 46443)
- mil/DNSKEY (alg 8, id 51349)
- mil/DNSKEY (alg 8, id 9498)
- mil/DS (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
Non_existent (2)
- army.mil/DNSKEY (alg 8, id 52329)
- army.mil/DNSKEY (alg 8, id 62140)
Delegation status
Bogus (1)
- mil to army.mil
Secure (1)
- . to mil
Notices
Errors (9)
- army.mil zone: The server(s) were not responsive to queries over TCP. (130.114.200.6, 140.153.43.44, 192.82.113.7)
- army.mil/DNSKEY: No response was received from the server over TCP (tried 12 times). (130.114.200.6, TCP_-_EDNS0_4096_D_KN)
- army.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). (140.153.43.44, 192.82.113.7, UDP_-_EDNS0_4096_D_KN)
- army.mil/MX: No response was received from the server over UDP (tried 4 times). (192.82.113.7, UDP_-_EDNS0_512_D_KN)
- army.mil/NSEC3PARAM: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. (140.153.43.44, UDP_-_NOEDNS_)
- army.mil/NSEC3PARAM: The DNSSEC records necessary to validate the response could not be retrieved from the server. (140.153.43.44, UDP_-_EDNS0_4096_D_KN)
- army.mil/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). (140.153.43.44, UDP_-_EDNS0_4096_D_KN)
- army.mil/SOA: No response was received from the server over TCP (tried 3 times). (130.114.200.6, 140.153.43.44, 192.82.113.7, TCP_-_EDNS0_4096_D_N)
- mil to army.mil: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone.
Warnings (10)
- army.mil/DS (alg 8, id 62140): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- army.mil/DS (alg 8, id 62140): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- 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.
- 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.
- army.mil/DS (alg 8, id 62140): 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. (199.252.154.234, UDP_-_EDNS0_4096_D_KN)
- army.mil/DS (alg 8, id 62140): 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. (199.252.154.234, UDP_-_EDNS0_4096_D_KN)
- mil/DS (alg 8, id 51349): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- mil/DS (alg 8, id 51349): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- 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.
- 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.
JavaScript is required to make the graph below interactive.
