Root certificate · SSL.com

SSL.com EV Root Certification Authority RSA R2

SSL.com EV Root Certification Authority RSA R2 is a root CA certificate operated by SSL.com (RSA 4096, valid until 2042-05-30, SHA-256 2E7BF16C). 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 IncludedYes2026-06-14Yes
MozillaIncluded IncludedYes—No
AppleIncluded IncludedYes—Yes
MicrosoftIncluded IncludedYes—Yes

Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2026-06-14 (sct_not_after). Mozilla treats it as an EV root for policy OID 2.23.140.1.1.

Included Chrome

Status
Included
Distrust for TLS after
2026-06-14

Included Mozilla

Status
Included
Trust bits
Websites
EV policy OIDs
2.23.140.1.1
First included in
NSS 3.34 / Firefox 58
Inclusion bug
#1277336

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth
Allowed policies
Server Authentication, Client Authentication

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication, Code Signing, Document Signing, Encrypting File System, Secure Email, Time Stamping
Not-before cutoff
2025-09-15 (Secure Email)

"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 EV Root Certification Authority RSA R2,O=SSL Corporation,L=Houston,ST=Texas,C=US
SHA-256
2E7BF16CC22485A7BBE2AA8696750761B0AE39BE3B2FE9D0CC6D4EF73491425C
SHA-1 (Windows thumbprint)
743AF0529BD032A0F44A83CDD4BAA97B7C2EC49A
SPKI SHA-256
7CD67C248F69D83FC2F9BB01DCB1F7AD67A363D046043796D0984C3A231F6BB0
Valid from
2017-05-31
Expires
2042-05-30
Key
RSA 4096
Signature algorithm
sha256WithRSAEncryption
Serial number
56B629CD34BC78F6
Country
US
Trust bits (CCADB)
Server Authentication, Client Authentication, Code Signing, Document Signing, Encrypting File System, Time Stamping
EV policy OIDs (CCADB)
2.23.140.1.1, 2.23.140.1.3, 1.3.6.1.4.1.38064.1.3.1.4, 1.3.6.1.4.1.38064.1.3.3.2 · TLS EV capable: Yes
Test websites
valid: https://test-ev-rsa.ssl.com · expired: https://expired-rsa-ev.ssl.com · revoked: https://revoked-rsa-ev.ssl.com/
CCADB record
A004439
PEM
ssl-com-ev-root-ca-rsa-r2.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 21 intermediate CA certificates signed directly by SSL.com EV Root Certification Authority RSA R2: 10 currently valid, 0 expired and 11 revoked (revoked includes those whose parent was revoked).

Showing 20 of 21: 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 EV Root Certification Authority RSA R2 but a different issuer. A server can send one of them so that clients which trust the issuing root, but not SSL.com EV Root Certification Authority RSA R2, can still build a chain.

Signed byCA ownerExpiresStatus
SecureTrust CA crt.sh SSL.com2029-12-30Valid
XRamp Global Certification Authority crt.sh SSL.com2034-12-30Valid
Certum Trusted Network CA crt.sh Asseco Data Systems S.A.2023-09-11Expired

CRL and OCSP addresses

In the root certificate

SSL.com EV Root Certification Authority RSA R2 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-EV-RSA-4096-R2.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 EV Root Certification Authority RSA R2; the number in brackets is how many of them use each address.

  • CRL: http://crls.ssl.com/SSLcom-RootCA-EV-RSA-4096-R2.crl (9)
  • OCSP: http://ocsps.ssl.com (7)

What happens when it expires

SSL.com EV Root Certification Authority RSA R2 is valid until 2042-05-30, about 15.6 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 EV Root Certification Authority RSA R2 by common name (SSL.com EV Root Certification Authority RSA R2) 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 EV Root Certification Authority RSA R2" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 2E7BF16CC22485A7BBE2AA8696750761B0AE39BE3B2FE9D0CC6D4EF73491425C

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 743AF0529BD032A0F44A83CDD4BAA97B7C2EC49A

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 EV Root Certification Authority RSA R2"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "SSL.com EV Root Certification Authority RSA R2"

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 "2E:7B:F1:6C:C2:24:85:A7:BB:E2:AA:86:96:75:07:61:B0:AE:39:BE:3B:2F:E9:D0:CC:6D:4E:F7:34:91:42:5C"

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 EV Root Certification Authority RSA R2.

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-ev-root-ca-rsa-r2.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=2E:7B:F1:6C:C2:24:85:A7:BB:E2:AA:86:96:75:07:61:B0:AE:39:BE:3B:2F:E9:D0:CC:6D:4E:F7:34:91:42:5C

FAQ

Is SSL.com EV Root Certification Authority RSA R2 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 EV Root Certification Authority RSA R2 expire?

On 2042-05-30, about 15.6 years after the 2026-11-10 data snapshot.

How many intermediate certificates has SSL.com EV Root Certification Authority RSA R2 issued?

The CCADB lists 21: 10 valid, 0 expired and 11 revoked. The newest valid one is SSL.com TLS RSA Root CA 2022, valid until 2038-11-03.

Is SSL.com EV Root Certification Authority RSA R2 cross-signed?

Yes. The CCADB has 3 cross-certificate(s) with its subject and key, signed by SecureTrust CA, XRamp Global Certification Authority, Certum Trusted Network CA; 2 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