osd.mil
Updated:
2023-03-16 21:46:00 UTC (649 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- osd.mil/MX
- osd.mil/NS
- osd.mil/NSEC3PARAM
- osd.mil/SOA
- osd.mil/SOA
- osd.mil/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- mil/DNSKEY (alg 8, id 53035)
- mil/DNSKEY (alg 8, id 62470)
- mil/DNSKEY (alg 8, id 8715)
- mil/DS (alg 8, id 62470)
- osd.mil/DNSKEY (alg 8, id 1342)
- osd.mil/DNSKEY (alg 8, id 26493)
- osd.mil/DNSKEY (alg 8, id 40449)
- osd.mil/DS (alg 8, id 1342)
- osd.mil/DS (alg 8, id 1342)
Delegation status
Secure (2)
- . to mil
- mil to osd.mil
Notices
Errors (5)
- osd.mil/DNSKEY (alg 8, id 40449): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (199.252.47.11, 199.252.47.75, UDP_-_EDNS0_4096_D_KN)
- 0n87ky96s5.osd.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- osd.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- osd.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- osd.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
- osd.mil/DS (alg 8, id 1342): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- osd.mil/DS (alg 8, id 1342): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- osd.mil/DS (alg 8, id 1342): 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.
- osd.mil/DS (alg 8, id 1342): 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.
- osd.mil/DS (alg 8, id 1342): 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.155.234, UDP_-_EDNS0_4096_D_KN)
- osd.mil/DS (alg 8, id 1342): 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.155.234, UDP_-_EDNS0_4096_D_KN)
- osd.mil/DS (alg 8, id 1342): 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.155.234, UDP_-_EDNS0_4096_D_KN)
- osd.mil/DS (alg 8, id 1342): 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.155.234, UDP_-_EDNS0_4096_D_KN)
- 0n87ky96s5.osd.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- osd.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- osd.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
- osd.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- osd.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
