oldcc.gov
Updated:
2021-06-23 15:55:16 UTC (1246 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- oldcc.gov/A
- oldcc.gov/MX
- oldcc.gov/NS
- oldcc.gov/SOA
- oldcc.gov/SOA
- oldcc.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- gov/DNSKEY (alg 8, id 48498)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- oldcc.gov/DNSKEY (alg 8, id 28999)
- oldcc.gov/DNSKEY (alg 8, id 63645)
- oldcc.gov/DS (alg 8, id 28999)
- oldcc.gov/DS (alg 8, id 28999)
Delegation status
Secure (2)
- . to gov
- gov to oldcc.gov
Notices
Errors (3)
- p9rg2nczy7.oldcc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- oldcc.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- oldcc.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- oldcc.gov/DS (alg 8, id 28999): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- oldcc.gov/DS (alg 8, id 28999): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- oldcc.gov/DS (alg 8, id 28999): 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.
- oldcc.gov/DS (alg 8, id 28999): 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.
- p9rg2nczy7.oldcc.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- oldcc.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- oldcc.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
