cisa.gov
Updated:
2022-03-01 17:37:27 UTC (1004 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (8)
- cisa.gov/A
- cisa.gov/A
- cisa.gov/AAAA
- cisa.gov/MX
- cisa.gov/NS
- cisa.gov/NSEC3PARAM
- cisa.gov/SOA
- cisa.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- cisa.gov/DNSKEY (alg 8, id 43039)
- cisa.gov/DNSKEY (alg 8, id 44160)
- cisa.gov/DNSKEY (alg 8, id 64709)
- cisa.gov/DS (alg 8, id 64709)
- cisa.gov/DS (alg 8, id 64709)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to cisa.gov
Notices
Errors (2)
- cisa.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- mnzp6lh0vq.cisa.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- cisa.gov/DS (alg 8, id 64709): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- cisa.gov/DS (alg 8, id 64709): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- cisa.gov/DS (alg 8, id 64709): 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.
- cisa.gov/DS (alg 8, id 64709): 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.
- cisa.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- mnzp6lh0vq.cisa.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
