occ.gov
Updated:
2021-08-07 05:16:21 UTC (1209 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (9)
- occ.gov/A
- occ.gov/AAAA
- occ.gov/NS
- occ.gov/NSEC3PARAM
- occ.gov/NSEC3PARAM
- occ.gov/NSEC3PARAM
- occ.gov/SOA
- occ.gov/SOA
- occ.gov/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- gov/DNSKEY (alg 8, id 57735)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- occ.gov/DNSKEY (alg 8, id 1743)
- occ.gov/DNSKEY (alg 8, id 50800)
- occ.gov/DS (alg 8, id 50800)
- occ.gov/DS (alg 8, id 50800)
Delegation status
Secure (2)
- . to gov
- gov to occ.gov
Notices
Errors (3)
- occ.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- j8ecx3oav5.occ.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- occ.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- occ.gov/DS (alg 8, id 50800): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- occ.gov/DS (alg 8, id 50800): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- occ.gov/DS (alg 8, id 50800): 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.
- occ.gov/DS (alg 8, id 50800): 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.
- occ.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- j8ecx3oav5.occ.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- occ.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
