dren.mil
Updated:
2024-09-12 14:15:24 UTC (5 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- dren.mil/MX
- dren.mil/NS
- dren.mil/SOA
- dren.mil/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- dren.mil/DNSKEY (alg 13, id 14070)
- dren.mil/DNSKEY (alg 13, id 22530)
- dren.mil/DNSKEY (alg 13, id 60084)
- dren.mil/DNSKEY (alg 13, id 63270)
- dren.mil/DS (alg 13, id 60084)
- dren.mil/DS (alg 13, id 60084)
- mil/DNSKEY (alg 8, id 16801)
- mil/DNSKEY (alg 8, id 20335)
- mil/DNSKEY (alg 8, id 51405)
- mil/DS (alg 8, id 16801)
Delegation status
Secure (2)
- . to mil
- mil to dren.mil
Notices
Errors (1)
- mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:4163:1:143::234)
Warnings (5)
- dren.mil/DS (alg 13, id 60084): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dren.mil/DS (alg 13, id 60084): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dren.mil/DS (alg 13, id 60084): 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.
- dren.mil/DS (alg 13, id 60084): 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/DNSKEY (alg 8, id 20335): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (199.252.155.234, 199.252.162.234, 199.252.180.234, 2608:4122:2:154::234, 2608:c184:1:180::234, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
