dea.gov
Updated:
2022-05-17 16:37:29 UTC (920 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (19)
- dea.gov/A
- dea.gov/A
- dea.gov/A
- dea.gov/A
- dea.gov/A
- dea.gov/A
- dea.gov/A
- dea.gov/AAAA
- dea.gov/AAAA
- dea.gov/AAAA
- dea.gov/AAAA
- dea.gov/AAAA
- dea.gov/AAAA
- dea.gov/AAAA
- dea.gov/MX
- dea.gov/NS
- dea.gov/NSEC3PARAM
- dea.gov/SOA
- dea.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- dea.gov/DNSKEY (alg 8, id 34120)
- dea.gov/DNSKEY (alg 8, id 44039)
- dea.gov/DNSKEY (alg 8, id 63516)
- dea.gov/DS (alg 8, id 44039)
- dea.gov/DS (alg 8, id 44039)
- gov/DNSKEY (alg 8, id 2706)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to dea.gov
Notices
Errors (2)
- dea.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- 8oj025ey9r.dea.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- dea.gov/DS (alg 8, id 44039): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dea.gov/DS (alg 8, id 44039): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dea.gov/DS (alg 8, id 44039): 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.
- dea.gov/DS (alg 8, id 44039): 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.
- dea.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- 8oj025ey9r.dea.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
