dtic.mil
Updated:
2023-06-22 13:42:46 UTC (549 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- dtic.mil/A
- dtic.mil/MX
- dtic.mil/NS
- dtic.mil/SOA
- dtic.mil/TXT
- mil/SOA
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- NSEC3 proving non-existence of dtic.mil/DS
- dtic.mil/DNSKEY (alg 13, id 33031)
- dtic.mil/DNSKEY (alg 13, id 4528)
- dtic.mil/DS (alg 13, id 4528)
- dtic.mil/DS (alg 13, id 4528)
- 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
Secure (2)
- . to mil
- mil to dtic.mil
Notices
Errors (3)
- 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/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
- 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 (alg 13, id 4528): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dtic.mil/DS (alg 13, id 4528): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dtic.mil/DS (alg 13, id 4528): 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 (alg 13, id 4528): 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/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. (2608:4163:1:143::243, UDP_-_EDNS0_4096_D_KN)
- mil to dtic.mil: 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.143.234, UDP_-_EDNS0_4096_D_KN)
- dtic.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
