Root certificate · SSL.com
SSL.com Root Certification Authority ECC
SSL.com Root Certification Authority ECC is a root CA certificate operated by SSL.com (ECDSA P-384, valid until 2041-02-12, SHA-256 3417BB06). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Included Included | Yes | 2026-06-14 | Yes |
| Mozilla | Included Included | Yes | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | No |
Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2026-06-14 (sct_not_after). The CCADB lists no EV policy OID for SSL.com Root Certification Authority ECC.
Included Chrome
- Status
- Included
- Distrust for TLS after
- 2026-06-14
Included Mozilla
- Status
- Included
- Trust bits
- Websites, Email
- EV policy OIDs
- not EV-enabled
- First included in
- NSS 3.34 / Firefox 58
- Inclusion bug
- #1277336
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth, emailProtection
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Code Signing, Document Signing, Encrypting File System, Secure Email, Time Stamping
"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
- SSL.com
- Subject
- CN=SSL.com Root Certification Authority ECC,O=SSL Corporation,L=Houston,ST=Texas,C=US
- SHA-256
3417BB06CC6007DA1B961C920B8AB4CE3FAD820E4AA30B9ACBC4A74EBDCEBC65- SHA-1 (Windows thumbprint)
C3197C3924E654AF1BC4AB20957AE2C30E13026A- SPKI SHA-256
A320F4D534D7BE97C1AE8DD0499735BC895C323ADD2D388BFCCF662C23D7F99A- Valid from
- 2016-02-12
- Expires
- 2041-02-12
- Key
- ECDSA P-384
- Signature algorithm
- ecdsa-with-SHA256
- Serial number
75E6DFCBC1685BA8- Country
- US
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Code Signing, Document Signing, Secure Email, Encrypting File System, Time Stamping
- EV policy OIDs (CCADB)
- not EV-enabled · TLS EV capable: No
- Test websites
- valid:
https://test-dv-ecc.ssl.com· expired:https://expired-ecc-dv.ssl.com· revoked:https://revoked-ecc-dv.ssl.com - CCADB record
- A003658
- PEM
- ssl-com-root-ca-ecc.pem
Intermediate CAs issued by this root
The CCADB lists 26 intermediate CA certificates signed directly by SSL.com Root Certification Authority ECC: 10 currently valid, 0 expired and 16 revoked (revoked includes those whose parent was revoked).
Showing 20 of 26: 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.
Cross-signed versions
3 certificate(s) in the CCADB have the same subject and public key as SSL.com Root Certification Authority ECC but a different issuer. A server can send one of them so that clients which trust the issuing root, but not SSL.com Root Certification Authority ECC, can still build a chain.
| Signed by | CA owner | Expires | Status |
|---|---|---|---|
| SSL.com Root Certification Authority RSA crt.sh | SSL.com | 2027-02-12 | Valid |
| SecureTrust CA crt.sh | SSL.com | 2029-12-30 | Valid |
| XRamp Global Certification Authority crt.sh | SSL.com | 2034-12-30 | Valid |
CRL and OCSP addresses
In the root certificate
SSL.com Root Certification Authority ECC 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://crls.ssl.com/SSLcom-RootCA-ECC-384-R1.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 10 valid intermediates signed by SSL.com Root Certification Authority ECC; the number in brackets is how many of them use each address.
- CRL:
http://crls.ssl.com/SSLcom-RootCA-ECC-384-R1.crl(6) - CRL:
http://crls.ssl.com/ssl.com-ecc-RootCA.crl(4) - OCSP:
http://ocsps.ssl.com(4)
What happens when it expires
SSL.com Root Certification Authority ECC is valid until 2041-02-12, about 14.3 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. Root programs can stop trusting it before it expires: Chrome 2026-06-14.
Check whether your device trusts it
Each platform keeps its own root store. The commands below look up SSL.com Root Certification Authority ECC by common name (SSL.com Root Certification Authority ECC) 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 "SSL.com Root Certification Authority ECC" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 3417BB06CC6007DA1B961C920B8AB4CE3FAD820E4AA30B9ACBC4A74EBDCEBC65
Windows (Microsoft store: Included · Trusted for TLS)
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 C3197C3924E654AF1BC4AB20957AE2C30E13026A
Linux (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 "SSL.com Root Certification Authority ECC"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "SSL.com Root Certification Authority ECC"
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 "34:17:BB:06:CC:60:07:DA:1B:96:1C:92:0B:8A:B4:CE:3F:AD:82:0E:4A:A3:0B:9A:CB:C4:A7:4E:BD:CE:BC:65"
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 SSL Corporation → SSL.com Root Certification Authority ECC.
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 ssl-com-root-ca-ecc.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=34:17:BB:06:CC:60:07:DA:1B:96:1C:92:0B:8A:B4:CE:3F:AD:82:0E:4A:A3:0B:9A:CB:C4:A7:4E:BD:CE:BC:65
FAQ
Is SSL.com Root Certification Authority ECC trusted by Chrome, Firefox, Safari and Windows?
Yes. As of 2026-11-10, Chrome, Mozilla (Firefox), Apple (Safari) and Microsoft (Windows) all trust it for TLS server authentication. Distrust-after dates already set: Chrome 2026-06-14.
When does SSL.com Root Certification Authority ECC expire?
On 2041-02-12, about 14.3 years after the 2026-11-10 data snapshot.
How many intermediate certificates has SSL.com Root Certification Authority ECC issued?
The CCADB lists 26: 10 valid, 0 expired and 16 revoked. The newest valid one is SSL.com TLS ECC Root CA 2022, valid until 2040-02-15.
Is SSL.com Root Certification Authority ECC cross-signed?
Yes. The CCADB has 3 cross-certificate(s) with its subject and key, signed by SSL.com Root Certification Authority RSA, SecureTrust CA, XRamp Global Certification Authority; 3 of them are still valid.
Other roots from SSL.com
- Secure Global CA RSA 2048 · 2029-12-31
- SecureTrust CA RSA 2048 · 2029-12-31
- SSL.com EV Root Certification Authority ECC ECDSA P-384 · 2041-02-12
- SSL.com EV Root Certification Authority RSA R2 RSA 4096 · 2042-05-30
- SSL.com Root Certification Authority RSA RSA 4096 · 2041-02-12
- SSL.com TLS ECC Root CA 2022 ECDSA P-384 · 2046-08-19
- SSL.com TLS RSA Root CA 2022 RSA 4096 · 2046-08-19
- Trustwave Global Certification Authority RSA 4096 · 2042-08-23
- Trustwave Global ECC P256 Certification Authority ECDSA P-256 · 2042-08-23
- Trustwave Global ECC P384 Certification Authority ECDSA P-384 · 2042-08-23
- XRamp Global Certification Authority RSA 2048 · 2035-01-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