Root certificate · Certainly LLC
Certainly Root R1
Certainly Root R1 is a root CA certificate operated by Certainly LLC (RSA 4096, valid until 2046-04-01, SHA-256 77B82CD8). As of the latest CCADB data it is trusted for TLS server authentication by 3 of 4 major root stores: Chrome, Mozilla, Apple.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Included Included | Yes | — | No |
| Mozilla | Included Included | Yes | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Not included Not included | No | — | No |
The CCADB lists no EV policy OID for Certainly Root R1.
Included Chrome
- Status
- Included
Included Mozilla
- Status
- Included
- Trust bits
- Websites
- EV policy OIDs
- not EV-enabled
- First included in
- NSS 3.80 / Firefox 103
- Inclusion bug
- #1727941
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth
Not included Microsoft
- Status
- Not included
"Trusted for TLS" means the store includes the root with the server-authentication trust bit (Mozilla "Websites", Apple serverAuth, Microsoft Server Authentication EKU). Microsoft "NotBefore" means only certificates issued before a cutoff date are still trusted. "Constrained" means the store applies extra restrictions.
Details
- CA owner
- Certainly LLC
- Subject
- CN=Certainly Root R1,O=Certainly,C=US
- SHA-256
77B82CD8644C4305F7ACC5CB156B45675004033D51C60C6202A8E0C33467D3A0- SHA-1 (Windows thumbprint)
A050EE0F2871F427B2126D6F509625BACC8642AF- SPKI SHA-256
3F93F3FCF79D225D213EEF6A4A3F5885CF84FE3D7A7A3C11553517688C0E2100- Valid from
- 2021-04-01
- Expires
- 2046-04-01
- Key
- RSA 4096
- Signature algorithm
- sha256WithRSAEncryption
- Serial number
8E0FF94B907168653354F4D44439B7E0- Country
- US
- Trust bits (CCADB)
- Server Authentication, Client Authentication
- EV policy OIDs (CCADB)
- not EV-enabled · TLS EV capable: No
- Test websites
- valid:
https://valid.root-r1.certainly.com· expired:https://expired.root-r1.certainly.com· revoked:https://revoked.root-r1.certainly.com - CCADB record
- A007889
- PEM
- certainly-root-r1.pem
Intermediate CAs issued by this root
The CCADB lists 1 intermediate CA certificates signed directly by Certainly Root R1: 1 currently valid, 0 expired and 0 revoked (revoked includes those whose parent was revoked).
Showing 1 of 1: valid certificates first, newest first. Each name links to its crt.sh entry by SHA-256; an arrow marks a cross-certificate for another root on this site.
| Intermediate | Operated by | Expires | Status |
|---|---|---|---|
| Certainly Intermediate R1 | Certainly LLC | 2031-04-01 | Valid |
Cross-signed versions
No certificate in the CCADB has the same subject and public key as Certainly Root R1 with a different issuer, so a client has to carry Certainly Root R1 itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
Certainly Root R1 itself contains no CRL Distribution Points and no OCSP (Authority Information Access) extension. That is normal for a root: clients trust it directly and do not check its own revocation status.
Full CRL this CA publishes (CCADB)
http://crl.root-r1.certainly.com/
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 1 valid intermediates signed by Certainly Root R1; the number in brackets is how many of them use each address.
- CRL:
http://crl.root-r1.certainly.com/(1)
None of the valid intermediates under this root lists an OCSP responder.
What happens when it expires
Certainly Root R1 is valid until 2046-04-01, about 19.4 years after this data snapshot (2026-11-10). From that day, browsers and operating systems that check trust-anchor expiry stop accepting chains that end at this root, so any certificate that can only chain to it fails validation. Android is a known exception: it does not enforce the expiry date of trust anchors.
Check whether your device trusts it
Each platform keeps its own root store. The commands below look up Certainly Root R1 by common name (Certainly Root R1) or fingerprint. The store status in each heading comes from the CCADB snapshot; your device can differ if it is out of date or managed by an administrator.
macOS (Apple store: Included · Trusted for TLS)
Search the system roots keychain by common name. -Z prints the SHA-256 hash, which must match the fingerprint on the last line.
security find-certificate -a -c "Certainly Root R1" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 77B82CD8644C4305F7ACC5CB156B45675004033D51C60C6202A8E0C33467D3A0Windows (Microsoft store: Not included)
Windows identifies roots by SHA-1 thumbprint. It installs third-party roots on demand through Automatic Root Certificates Update, so "not found" can also mean the root has not been needed yet; certutil -generateSSTFromWU roots.sst downloads Microsoft's full list.
certutil -verifystore Root A050EE0F2871F427B2126D6F509625BACC8642AFLinux (ca-certificates follows Mozilla: Included · Trusted for TLS)
Debian, Ubuntu, Fedora and RHEL build their ca-certificates package from Mozilla's root store. Use trust list on p11-kit systems, or search the PEM bundle on Debian and Ubuntu.
# Fedora / RHEL / Arch (p11-kit)
trust list --filter=ca-anchors | grep -iF -A2 "Certainly Root R1"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "Certainly Root R1"Java
Java ships its own cacerts keystore; JDK 9 and later accept -cacerts and the default store password is changeit. Search for the SHA-256 fingerprint in colon form.
keytool -list -cacerts -storepass changeit | grep -i "77:B8:2C:D8:64:4C:43:05:F7:AC:C5:CB:15:6B:45:67:50:04:03:3D:51:C6:0C:62:02:A8:E0:C3:34:67:D3:A0"Android
Android's system store is maintained by Google separately from the four CCADB stores above. Open Settings → Security & privacy → More security settings → Encryption & credentials → Trusted credentials → System (menu names vary by vendor and version) and look for Certainly → Certainly Root R1.
Which root does my site chain to?
List the chain your server sends and compare the last issuer with this root; the fingerprint check confirms a local copy.
# show subject (s:) and issuer (i:) of every certificate the server sends
openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null 2>/dev/null \
| grep -E '^ *[0-9]+ s:|^ *i:'
# subject and SHA-256 fingerprint of the downloaded PEM file
openssl x509 -in certainly-root-r1.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=77:B8:2C:D8:64:4C:43:05:F7:AC:C5:CB:15:6B:45:67:50:04:03:3D:51:C6:0C:62:02:A8:E0:C3:34:67:D3:A0FAQ
Is Certainly Root R1 trusted by Chrome, Firefox, Safari and Windows?
As of 2026-11-10, Chrome, Mozilla, Apple trust it for TLS server authentication; Microsoft do not.
When does Certainly Root R1 expire?
On 2046-04-01, about 19.4 years after the 2026-11-10 data snapshot.
How many intermediate certificates has Certainly Root R1 issued?
The CCADB lists 1: 1 valid, 0 expired and 0 revoked. The newest valid one is Certainly Intermediate R1, valid until 2031-04-01.
Is Certainly Root R1 cross-signed?
No. The CCADB has no certificate with the same subject and public key signed by another CA.
Other roots from Certainly LLC
- Certainly Root E1 ECDSA P-384 · 2046-04-01
Sources
- CCADB — Resources (TLS Server Authentication report, All Included Root Certificate Trust Bit Settings)
- CCADB — All Certificate Information (root and intermediate), CSV V5
- CCADB — Mozilla Included CA Certificate Report
- CCADB — Chrome / Mozilla / Apple / Microsoft TLS Server Authentication CSV