Root certificate · SSL.com

SSL.com TLS ECC Root CA 2022

SSL.com TLS ECC Root CA 2022 is a root CA certificate operated by SSL.com (ECDSA P-384, valid until 2046-08-19, SHA-256 C32FFD9F). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeIncluded IncludedYes—No
MozillaIncluded IncludedYes—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—No

Mozilla treats it as an EV root for policy OID 2.23.140.1.1.

Included Chrome

Status
Included

Included Mozilla

Status
Included
Trust bits
Websites
EV policy OIDs
2.23.140.1.1
First included in
NSS 3.92 / Firefox 117
Inclusion bug
#1799533

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication

"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 TLS ECC Root CA 2022,O=SSL Corporation,C=US
SHA-256
C32FFD9F46F936D16C3673990959434B9AD60AAFBB9E7CF33654F144CC1BA143
SHA-1 (Windows thumbprint)
9F5FD91A546DF50C71F0EE7ABD1749988473E239
SPKI SHA-256
1BF00D5C8F13C094DD17E00504CF0888850F12FD067FA1F92C0FDBF60B86E321
Valid from
2022-08-25
Expires
2046-08-19
Key
ECDSA P-384
Signature algorithm
ecdsa-with-SHA384
Serial number
1403F5ABFB378B17405BE243B2A5D1C4
Country
US
Trust bits (CCADB)
Server Authentication, Client Authentication
EV policy OIDs (CCADB)
2.23.140.1.1 · TLS EV capable: Yes
Test websites
valid: https://test-root-2022-ecc.ssl.com · expired: https://expired-root-2022-ecc.ssl.com · revoked: https://revoked-root-2022-ecc.ssl.com
CCADB record
A010581
PEM
ssl-com-tls-ecc-root-ca-2022.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 13 intermediate CA certificates signed directly by SSL.com TLS ECC Root CA 2022: 13 currently valid, 0 expired and 0 revoked (revoked includes those whose parent was revoked).

Showing 13 of 13: 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.

IntermediateOperated byExpiresStatus
E-Tugra TLS ECC CA 2 SSL.com2036-06-09Valid
Crowdstrike, Inc. OV TLS Issuing ECC CA 1 SSL.com2027-09-26Valid
Entrust EV TLS Issuing ECC CA 1 SSL.com2027-08-22Valid
Entrust OV TLS Issuing ECC CA 1 SSL.com2027-08-22Valid
Entrust DV TLS Issuing ECC CA 1 SSL.com2027-08-22Valid
SSL.com OV TLS Issuing ECC CA 1 SSL.com2032-12-06Valid
SSL.com IV TLS Transit ECC CA 1 SSL.com2037-12-05Valid
SSL.com IV TLS Issuing ECC CA 1 SSL.com2032-12-06Valid
SSL.com OV TLS Transit ECC CA 1 SSL.com2037-12-05Valid
SSL.com TLS Issuing ECC CA R2 SSL.com2032-10-18Valid
SSL.com EV TLS Issuing ECC CA R1 SSL.com2032-10-18Valid
SSL.com TLS Transit ECC CA R2 SSL.com2037-10-17Valid
SSL.com EV TLS Transit ECC CA R2 SSL.com2037-10-17Valid

Cross-signed versions

7 certificate(s) in the CCADB have the same subject and public key as SSL.com TLS ECC Root CA 2022 but a different issuer. A server can send one of them so that clients which trust the issuing root, but not SSL.com TLS ECC Root CA 2022, can still build a chain.

Signed byCA ownerExpiresStatus
AAA Certificate Services crt.sh Sectigo2028-12-31Valid
SecureTrust CA crt.sh SSL.com2029-12-30Valid
XRamp Global Certification Authority crt.sh SSL.com2034-12-30Valid
SSL.com EV Root Certification Authority ECC crt.sh SSL.com2038-11-03Valid
SSL.com Root Certification Authority ECC crt.sh SSL.com2040-02-15Valid
Trustwave Global ECC P384 Certification Authority crt.sh SSL.com2042-08-21Valid
Trustwave Global ECC P256 Certification Authority crt.sh SSL.com2042-08-21Valid

CRL and OCSP addresses

In the root certificate

SSL.com TLS ECC Root CA 2022 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-TLS-Root-2022-ECC.crl

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 13 valid intermediates signed by SSL.com TLS ECC Root CA 2022; the number in brackets is how many of them use each address.

  • CRL: http://crls.ssl.com/SSLcom-TLS-Root-2022-ECC.crl (13)
  • OCSP: http://ocsps.ssl.com (3)

What happens when it expires

SSL.com TLS ECC Root CA 2022 is valid until 2046-08-19, about 19.8 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 SSL.com TLS ECC Root CA 2022 by common name (SSL.com TLS ECC Root CA 2022) 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 TLS ECC Root CA 2022" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: C32FFD9F46F936D16C3673990959434B9AD60AAFBB9E7CF33654F144CC1BA143

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 9F5FD91A546DF50C71F0EE7ABD1749988473E239

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 TLS ECC Root CA 2022"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "SSL.com TLS ECC Root CA 2022"

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 "C3:2F:FD:9F:46:F9:36:D1:6C:36:73:99:09:59:43:4B:9A:D6:0A:AF:BB:9E:7C:F3:36:54:F1:44:CC:1B:A1:43"

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 TLS ECC Root CA 2022.

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.

Download PEM

# 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-tls-ecc-root-ca-2022.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=C3:2F:FD:9F:46:F9:36:D1:6C:36:73:99:09:59:43:4B:9A:D6:0A:AF:BB:9E:7C:F3:36:54:F1:44:CC:1B:A1:43

FAQ

Is SSL.com TLS ECC Root CA 2022 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.

When does SSL.com TLS ECC Root CA 2022 expire?

On 2046-08-19, about 19.8 years after the 2026-11-10 data snapshot.

How many intermediate certificates has SSL.com TLS ECC Root CA 2022 issued?

The CCADB lists 13: 13 valid, 0 expired and 0 revoked. The newest valid one is E-Tugra TLS ECC CA 2, valid until 2036-06-09.

Is SSL.com TLS ECC Root CA 2022 cross-signed?

Yes. The CCADB has 7 cross-certificate(s) with its subject and key, signed by AAA Certificate Services, SecureTrust CA, XRamp Global Certification Authority, SSL.com EV Root Certification Authority ECC, SSL.com Root Certification Authority ECC, Trustwave Global ECC P384 Certification Authority, Trustwave Global ECC P256 Certification Authority; 7 of them are still valid.

Other roots from SSL.com

Sources

  1. CCADB — Resources (TLS Server Authentication report, All Included Root Certificate Trust Bit Settings)
  2. CCADB — All Certificate Information (root and intermediate), CSV V5
  3. CCADB — Mozilla Included CA Certificate Report
  4. CCADB — Chrome / Mozilla / Apple / Microsoft TLS Server Authentication CSV