osd.mil
Updated:
2021-07-23 16:18:12 UTC (1253 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- osd.mil/MX
- osd.mil/NS
- osd.mil/SOA
- osd.mil/SOA
- osd.mil/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- mil/DNSKEY (alg 8, id 46443)
- 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)
Non_existent (1)
- osd.mil/DNSKEY (alg 8, id 20244)
Delegation status
Secure (2)
- . to mil
- mil to osd.mil
Notices
Errors (16)
- RRSIG osd.mil/DNSKEY alg 8, id 11701: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- RRSIG osd.mil/DNSKEY alg 8, id 11701: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- RRSIG osd.mil/DNSKEY alg 8, id 11701: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- RRSIG osd.mil/DNSKEY alg 8, id 4192: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- RRSIG osd.mil/DNSKEY alg 8, id 4192: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- RRSIG osd.mil/DNSKEY alg 8, id 4192: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- RRSIG osd.mil/DNSKEY 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/DNSKEY 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/DNSKEY alg 8, id 60090: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
- mil to osd.mil: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.252.47.11, 199.252.47.75, TCP_-_EDNS0_4096_D_KN)
- osd.mil/DNSKEY (alg 8, id 20244): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (199.252.47.11, 199.252.47.75, TCP_-_EDNS0_4096_D_KN)
- osd.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- z39fvybaph.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 (12)
- 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.
- osd.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- z39fvybaph.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.
