Root certificate · SSL.com
Trustwave Global ECC P384 Certification Authority
Trustwave Global ECC P384 Certification Authority is a root CA certificate operated by SSL.com (ECDSA P-384, valid until 2042-08-23, SHA-256 55903859). 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=Trustwave Global ECC P384 Certification Authority,O=Trustwave Holdings\, Inc.,L=Chicago,ST=Illinois,C=US
- SHA-256
55903859C8C0C3EBB8759ECE4E2557225FF5758BBD38EBD48276601E1BD58097- SHA-1 (Windows thumbprint)
E7F3A3C8CF6FC3042E6D0E6732C59E68950D5ED2- SPKI SHA-256
828B0EEFF24654E8FF5841A29DD5D4E3ED30952CA43425A79283407208D39D16- Valid from
- 2017-08-23
- Expires
- 2042-08-23
- Key
- ECDSA P-384
- Signature algorithm
- ecdsa-with-SHA384
- Serial number
8BD85976C9927A48068473B- 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-twgca-ecc-p384.sslsecuretrust.com· expired:https://expired-twgca-ecc-p384.sslsecuretrust.com· revoked:https://revoked-twgca-ecc-p384.sslsecuretrust.com - CCADB record
- A006273
- PEM
- ssl-com-trustwave-global-ecc-p384-ca.pem
Intermediate CAs issued by this root
The CCADB lists 15 intermediate CA certificates signed directly by Trustwave Global ECC P384 Certification Authority: 1 currently valid, 0 expired and 14 revoked (revoked includes those whose parent was revoked).
Showing 15 of 15: 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 Trustwave Global ECC P384 Certification Authority with a different issuer, so a client has to carry Trustwave Global ECC P384 Certification Authority itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
Trustwave Global ECC P384 Certification Authority 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.vikingcloud.com/TWGP384CA.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 1 valid intermediates signed by Trustwave Global ECC P384 Certification Authority; the number in brackets is how many of them use each address.
- CRL:
http://crl.sslsecuretrust.com/TWGP384CA.crl(1) - OCSP:
http://ocsp.sslsecuretrust.com/(1)
What happens when it expires
Trustwave Global ECC P384 Certification Authority is valid until 2042-08-23, about 15.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 Trustwave Global ECC P384 Certification Authority by common name (Trustwave Global ECC P384 Certification Authority) 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 "Trustwave Global ECC P384 Certification Authority" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 55903859C8C0C3EBB8759ECE4E2557225FF5758BBD38EBD48276601E1BD58097
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 E7F3A3C8CF6FC3042E6D0E6732C59E68950D5ED2
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 "Trustwave Global ECC P384 Certification Authority"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "Trustwave Global ECC P384 Certification Authority"
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 "55:90:38:59:C8:C0:C3:EB:B8:75:9E:CE:4E:25:57:22:5F:F5:75:8B:BD:38:EB:D4:82:76:60:1E:1B:D5:80:97"
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 Trustwave Holdings, Inc. → Trustwave Global ECC P384 Certification Authority.
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-trustwave-global-ecc-p384-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=55:90:38:59:C8:C0:C3:EB:B8:75:9E:CE:4E:25:57:22:5F:F5:75:8B:BD:38:EB:D4:82:76:60:1E:1B:D5:80:97
FAQ
Is Trustwave Global ECC P384 Certification Authority 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 Trustwave Global ECC P384 Certification Authority expire?
On 2042-08-23, about 15.8 years after the 2026-11-10 data snapshot.
How many intermediate certificates has Trustwave Global ECC P384 Certification Authority issued?
The CCADB lists 15: 1 valid, 0 expired and 14 revoked. The newest valid one is SSL.com TLS ECC Root CA 2022, valid until 2042-08-21.
Is Trustwave Global ECC P384 Certification Authority 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
- 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 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
- 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