dren.mil
Updated:
2023-11-06 20:27:40 UTC (436 days ago)
Go to most recent »
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 (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- dren.mil/DNSKEY (alg 13, id 14070)
- dren.mil/DNSKEY (alg 13, id 60084)
- 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 29343)
- mil/DNSKEY (alg 8, id 44065)
- mil/DS (alg 8, id 16801)
Delegation status
Secure (2)
- . to mil
- mil to dren.mil
Notices
Errors (1)
- mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2608:c144:1:155::234, UDP_-_EDNS0_512_D_KN)
Warnings (4)
- 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.
JavaScript is required to make the graph below interactive.
