dtic.mil
Updated:
2023-06-22 13:20:02 UTC (550 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- dtic.mil/A
- dtic.mil/MX
- dtic.mil/NS
- dtic.mil/SOA
- dtic.mil/TXT
Secure (1)
- mil/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- dtic.mil/DNSKEY (alg 13, id 33031)
- dtic.mil/DNSKEY (alg 13, id 4528)
Secure (8)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- NSEC3 proving non-existence of dtic.mil/DS
- mil/DNSKEY (alg 8, id 40318)
- mil/DNSKEY (alg 8, id 62470)
- mil/DNSKEY (alg 8, id 62514)
- mil/DS (alg 8, id 62470)
Delegation status
Insecure (1)
- mil to dtic.mil
Secure (1)
- . to mil
Notices
Errors (5)
- NSEC3 proving non-existence of dtic.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of dtic.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- dtic.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.155.243, UDP_-_EDNS0_512_D_KN)
- dtic.mil/DS 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 (3)
- NSEC3 proving non-existence of dtic.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of dtic.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- dtic.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
