dtic.mil
Updated:
2023-04-24 11:45:45 UTC (610 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (5)
- dtic.mil/A
- dtic.mil/NS
- dtic.mil/NSEC3PARAM
- dtic.mil/SOA
- dtic.mil/TXT
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- dtic.mil/DS (alg 10, id 55959)
- mil/DNSKEY (alg 8, id 1773)
- mil/DNSKEY (alg 8, id 53035)
- mil/DNSKEY (alg 8, id 62470)
- mil/DS (alg 8, id 62470)
Non_existent (2)
- dtic.mil/DNSKEY (alg 10, id 15680)
- dtic.mil/DNSKEY (alg 10, id 55959)
Delegation status
Bogus (1)
- mil to dtic.mil
Secure (1)
- . to mil
Notices
Errors (21)
- dtic.mil zone: The following NS name(s) did not resolve to address(es): ns1.dtic.mil, ns2.dtic.mil
- dtic.mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (140.18.188.250, 140.18.189.250)
- dtic.mil/A: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (140.18.189.250, UDP_-_EDNS0_4096_)
- dtic.mil/A: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (140.18.189.250, UDP_-_EDNS0_4096_D_KN)
- dtic.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. (140.18.189.250, UDP_-_EDNS0_4096_D_KN)
- dtic.mil/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.18.188.250, 140.18.189.250, UDP_-_NOEDNS_)
- dtic.mil/DNSKEY: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (140.18.189.250, TCP_-_EDNS0_4096_D)
- dtic.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.18.188.250, UDP_-_EDNS0_4096_D_KN)
- dtic.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (140.18.188.250, 140.18.189.250, UDP_-_EDNS0_512_D_KN)
- dtic.mil/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.18.188.250, 140.18.189.250, UDP_-_NOEDNS_)
- dtic.mil/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (140.18.188.250, 140.18.189.250, UDP_-_EDNS0_512_D_KN)
- dtic.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.18.189.250, UDP_-_NOEDNS_)
- dtic.mil/NSEC3PARAM: 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. (140.18.189.250, UDP_-_NOEDNS_)
- dtic.mil/NSEC3PARAM: 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. (140.18.189.250, UDP_-_EDNS0_4096_D_KN)
- dtic.mil/NSEC3PARAM: 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. (140.18.189.250, UDP_-_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. (140.18.188.250, 140.18.189.250, TCP_-_EDNS0_4096_D_N)
- dtic.mil/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.18.188.250, 140.18.189.250, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- 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.
- 82y6e4wxfo.dtic.mil/A 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.
- dtic.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- RRSIG dtic.mil/A alg 10, id 15680: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dtic.mil/NS alg 10, id 15680: 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 15680: 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 15680: 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 15680: 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. (140.18.188.250, UDP_-_EDNS0_4096_D_KN)
- dtic.mil/NS: 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. (140.18.188.250, UDP_-_EDNS0_4096_D_KN)
- dtic.mil/TXT: 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. (140.18.189.250, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
