dtic.mil
Updated:
2021-08-10 11:19:15 UTC (1255 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (6)
- dtic.mil/A
- dtic.mil/MX
- dtic.mil/NSEC3PARAM
- dtic.mil/SOA
- dtic.mil/SOA
- dtic.mil/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- dtic.mil/DS (alg 10, id 1536)
- 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)
- dtic.mil/DNSKEY (alg 10, id 1536)
- dtic.mil/DNSKEY (alg 10, id 51437)
Delegation status
Bogus (1)
- mil to dtic.mil
Secure (1)
- . to mil
Notices
Errors (15)
- dtic.mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (131.84.136.73, 131.84.136.89)
- dtic.mil/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (131.84.136.73, TCP_-_EDNS0_4096_D_KN)
- dtic.mil/DNSKEY: No response was received from the server over TCP (tried 9 times). See RFC 1035, Sec. 4.2. (131.84.136.89, TCP_-_EDNS0_4096_D)
- dtic.mil/NS: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (131.84.136.73, TCP_-_EDNS0_4096_D_N)
- dtic.mil/NS: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (131.84.136.89, TCP_-_EDNS0_4096_D_KN)
- dtic.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (131.84.136.73, 131.84.136.89, TCP_-_EDNS0_4096_D_N)
- mil to dtic.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. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11.
- mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (199.252.154.234, 199.252.155.234, 199.252.157.234, 199.252.180.234)
- mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.252.143.234)
- mil/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.180.234, TCP_-_EDNS0_4096_D_KN)
- mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.154.234, UDP_-_EDNS0_512_D_KN)
- dtic.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- 9rh0j81wb4.dtic.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- dtic.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- dtic.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (17)
- RRSIG dtic.mil/A alg 10, id 51437: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dtic.mil/MX alg 10, id 51437: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dtic.mil/NSEC3PARAM alg 10, id 51437: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dtic.mil/SOA alg 10, id 51437: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dtic.mil/SOA alg 10, id 51437: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dtic.mil/TXT alg 10, id 51437: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- dtic.mil/A: 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. (131.84.136.73, 131.84.136.89, UDP_-_EDNS0_4096_D_KN)
- dtic.mil/DS (alg 10, id 1536): 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. (199.252.180.234, UDP_-_EDNS0_4096_D_KN)
- dtic.mil/DS (alg 10, id 1536): 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. (199.252.180.234, UDP_-_EDNS0_4096_D_KN)
- dtic.mil/SOA: 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. (131.84.136.73, UDP_-_EDNS0_4096_D_KN)
- 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.
- dtic.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
- dtic.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- dtic.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
