Root certificate · SSL.com
SecureTrust CA
SecureTrust CA is a root CA certificate operated by SSL.com (RSA 2048, valid until 2029-12-31, SHA-256 F1C1B50A). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Removed Removed | No | — | No |
| Mozilla | Removed Removed | No | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | Yes |
The CCADB lists EV policy OID 2.23.140.1.1, 2.16.840.1.114404.1.1.2.4.1 for this root, but Mozilla does not mark it as EV-enabled.
Removed Chrome
- Status
- Removed
Removed Mozilla
- Status
- Removed
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth, emailProtection
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Code Signing, Secure Email, Time Stamping
- Not-before cutoff
- 2025-09-15 (Code Signing)
"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=SecureTrust CA,O=SecureTrust Corporation,C=US
- SHA-256
F1C1B50AE5A20DD8030EC9F6BC24823DD367B5255759B4E71B61FCE9F7375D73- SHA-1 (Windows thumbprint)
8782C6C304353BCFD29692D2593E7D44D934FF11- SPKI SHA-256
77290717614B25F12964EBDB38B5F83CAADC0F6C36B0777F880FC6DEE1D339CC- Valid from
- 2006-11-07
- Expires
- 2029-12-31
- Key
- RSA 2048
- Signature algorithm
- sha1WithRSAEncryption
- Serial number
CF08E5C0816A5AD427FF0EB271859D0- Country
- US
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Secure Email, Time Stamping
- EV policy OIDs (CCADB)
- 2.23.140.1.1, 2.16.840.1.114404.1.1.2.4.1 · TLS EV capable: Yes
- Test websites
- valid:
https://test-stca-rsa.sslsecuretrust.com· expired:https://expired-stca-rsa.sslsecuretrust.com· revoked:https://revoked-stca-rsa.sslsecuretrust.com - CCADB record
- A000184
- PEM
- ssl-com-securetrust-ca.pem
Intermediate CAs issued by this root
The CCADB lists 33 intermediate CA certificates signed directly by SecureTrust CA: 7 currently valid, 1 expired and 25 revoked (revoked includes those whose parent was revoked).
Showing 20 of 33: 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
No certificate in the CCADB has the same subject and public key as SecureTrust CA with a different issuer, so a client has to carry SecureTrust CA itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
- CRL:
http://crl.securetrust.com/STCA.crl
Full CRL this CA publishes (CCADB)
http://crl.vikingcloud.com/STCA.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 7 valid intermediates signed by SecureTrust CA; the number in brackets is how many of them use each address.
- CRL:
http://crl.sslsecuretrust.com/STCA.crl(7) - OCSP:
http://ocsp.sslsecuretrust.com/(7)
What happens when it expires
SecureTrust CA is valid until 2029-12-31, about 3.1 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 SecureTrust CA by common name (SecureTrust CA) 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 "SecureTrust CA" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: F1C1B50AE5A20DD8030EC9F6BC24823DD367B5255759B4E71B61FCE9F7375D73
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 8782C6C304353BCFD29692D2593E7D44D934FF11
Linux (ca-certificates follows Mozilla: Removed)
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 "SecureTrust CA"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "SecureTrust CA"
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 "F1:C1:B5:0A:E5:A2:0D:D8:03:0E:C9:F6:BC:24:82:3D:D3:67:B5:25:57:59:B4:E7:1B:61:FC:E9:F7:37:5D:73"
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 SecureTrust Corporation → SecureTrust CA.
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-securetrust-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=F1:C1:B5:0A:E5:A2:0D:D8:03:0E:C9:F6:BC:24:82:3D:D3:67:B5:25:57:59:B4:E7:1B:61:FC:E9:F7:37:5D:73
FAQ
Is SecureTrust CA trusted by Chrome, Firefox, Safari and Windows?
As of 2026-11-10, Apple, Microsoft trust it for TLS server authentication; Chrome, Mozilla do not.
When does SecureTrust CA expire?
On 2029-12-31, about 3.1 years after the 2026-11-10 data snapshot.
How many intermediate certificates has SecureTrust CA issued?
The CCADB lists 33: 7 valid, 1 expired and 25 revoked. The newest valid one is SSL.com SecureTrust TLS OV Issuing RSA CA R2, valid until 2029-12-28.
Is SecureTrust CA cross-signed?
No. The CCADB has no certificate with the same subject and public key signed by another CA.
Other roots from SSL.com
- Secure Global 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 ECC ECDSA P-384 · 2041-02-12
- 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