osd.mil
Updated:
2021-08-16 20:49:43 UTC (1224 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (2)
- osd.mil/SOA
- osd.mil/SOA
Secure (4)
- osd.mil/MX
- osd.mil/NS
- osd.mil/NSEC3PARAM
- osd.mil/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- mil/DNSKEY (alg 8, id 39879)
- mil/DNSKEY (alg 8, id 51349)
- mil/DNSKEY (alg 8, id 9498)
- mil/DS (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
- osd.mil/DNSKEY (alg 8, id 11701)
- osd.mil/DNSKEY (alg 8, id 20244)
- osd.mil/DNSKEY (alg 8, id 4192)
- osd.mil/DNSKEY (alg 8, id 60090)
- 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 (14)
- RRSIG osd.mil/SOA alg 8, id 20244: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- RRSIG osd.mil/SOA alg 8, id 20244: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- RRSIG osd.mil/SOA alg 8, id 60090: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- RRSIG osd.mil/SOA alg 8, id 60090: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.143.234, UDP_-_EDNS0_512_D_KN)
- osd.mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (214.14.133.11)
- osd.mil/A: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.47.11, 199.252.47.75, 214.14.133.11, TCP_-_EDNS0_4096_D)
- osd.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (214.14.133.11, UDP_-_EDNS0_4096_D_KN)
- osd.mil/NS: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (214.14.133.11, TCP_-_EDNS0_4096_D)
- osd.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (199.252.47.11, 199.252.47.75, 214.14.133.11, TCP_-_EDNS0_4096_D_N)
- r35m417k9y.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.
- osd.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
- mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/DS (alg 8, id 51349): 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.
- mil/DS (alg 8, id 51349): 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): 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.
- r35m417k9y.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.
