osd.mil
Updated:
2021-11-11 16:14:03 UTC (1052 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (8)
- osd.mil/MX
- osd.mil/NS
- osd.mil/NSEC3PARAM
- osd.mil/SOA
- osd.mil/SOA
- osd.mil/SOA
- osd.mil/SOA
- osd.mil/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- mil/DNSKEY (alg 8, id 39879)
- mil/DNSKEY (alg 8, id 56347)
- mil/DNSKEY (alg 8, id 61224)
- mil/DS (alg 8, id 56347)
- osd.mil/DNSKEY (alg 8, id 4192)
- osd.mil/DNSKEY (alg 8, id 6468)
- osd.mil/DS (alg 8, id 4192)
- osd.mil/DS (alg 8, id 4192)
Delegation status
Secure (2)
- . to mil
- mil to osd.mil
Notices
Errors (13)
- osd.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.47.75, UDP_-_NOEDNS_)
- osd.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.47.11, UDP_-_EDNS0_512_D_KN)
- osd.mil/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.47.11, UDP_-_NOEDNS_)
- osd.mil/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.47.11, 199.252.47.75, UDP_-_EDNS0_512_D_KN)
- osd.mil/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.47.11, 199.252.47.75, UDP_-_NOEDNS_)
- osd.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (199.252.47.75, TCP_-_EDNS0_4096_D_N)
- osd.mil/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.47.11, 199.252.47.75, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- osd.mil/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.47.11, 199.252.47.75, UDP_-_NOEDNS_)
- osd.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- osd.mil/DNSKEY 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.
- 2rto3u8qcl.osd.mil/A 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 (16)
- osd.mil/DS (alg 8, id 4192): 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 4192): 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 4192): 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 4192): 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 4192): 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.154.234, UDP_-_EDNS0_4096_D_KN)
- osd.mil/DS (alg 8, id 4192): 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.154.234, UDP_-_EDNS0_4096_D_KN)
- osd.mil/DS (alg 8, id 4192): 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.154.234, UDP_-_EDNS0_4096_D_KN)
- osd.mil/DS (alg 8, id 4192): 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.154.234, UDP_-_EDNS0_4096_D_KN)
- osd.mil/MX: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (199.252.47.75, UDP_-_EDNS0_4096_D_KN)
- osd.mil/NS: 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.47.75, UDP_-_EDNS0_4096_D_KN)
- osd.mil/SOA: 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. (199.252.47.75, UDP_-_EDNS0_4096_D_KN)
- 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.
- 2rto3u8qcl.osd.mil/A 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.
