Root certificate · SSL.com

Trustwave Global Certification Authority

Trustwave Global Certification Authority is a root CA certificate operated by SSL.com (RSA 4096, valid until 2042-08-23, SHA-256 97552015). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeRemoved RemovedNo—No
MozillaRemoved RemovedNo—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—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 Certification Authority,O=Trustwave Holdings\, Inc.,L=Chicago,ST=Illinois,C=US
SHA-256
97552015F5DDFC3C8788C006944555408894450084F100867086BC1A2BB58DC8
SHA-1 (Windows thumbprint)
2F8F364FE1589744215987A52A9AD06995267FB5
SPKI SHA-256
2E06CAE1FC20B200E6FB748557A4444BEC9317DFFF2E4151669E0F7944F0A9E0
Valid from
2017-08-23
Expires
2042-08-23
Key
RSA 4096
Signature algorithm
sha256WithRSAEncryption
Serial number
5F70E86DA49F346352EBAB2
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-rsa.sslsecuretrust.com · expired: https://expired-twgca-rsa.sslsecuretrust.com · revoked: https://revoked-twgca-rsa.sslsecuretrust.com
CCADB record
A006271
PEM
ssl-com-trustwave-global-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 18 intermediate CA certificates signed directly by Trustwave Global Certification Authority: 1 currently valid, 0 expired and 17 revoked (revoked includes those whose parent was revoked).

Showing 18 of 18: 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
SSL.com TLS RSA Root CA 2022 → SSL.com TLS RSA Root CA 2022 SSL.com2042-08-21Valid
VikingCloud TWG TLS OV CA, Level 1 SSL.com2035-02-24Revoked
VikingCloud TWG TLS EV CA, Level 1 SSL.com2035-02-24Revoked
VikingCloud TWG TLS IV CA, Level 1 SSL.com2035-02-24Revoked
VikingCloud TWG TLS DV CA, Level 2 SSL.com2035-02-24Revoked
VikingCloud TWG TLS DV CA, Level 1 SSL.com2034-08-28Revoked
Viking Cloud TWG Timestamping CA, Level 1 SSL.com2037-08-10Revoked
Viking Cloud TWG Code Signing CA, Level 1 SSL.com2032-08-10Revoked
SecureTrust TWG Secure Email CA, Level 2 SSL.com2030-10-08Revoked
SecureTrust TWG Client CA, Level 3 SSL.com2030-10-08Revoked
SecureTrust TWG Client CA, Level 2 SSL.com2030-09-21Revoked
SecureTrust TWG Secure Email CA, Level 1 SSL.com2030-09-21Revoked
Trustwave Global Client CA, Level 1 SSL.com2028-02-24Revoked
Trustwave Global Domain Validation CA, Level 1 SSL.com2028-02-24Revoked
Trustwave Global Timestamping CA, Level 1 SSL.com2042-08-21Revoked
Trustwave Global Code Signing CA, Level 1 SSL.com2042-08-21Revoked
Trustwave Global Organization Validation CA, Level 1 SSL.com2028-02-24Revoked
Trustwave Global Extended Validation CA, Level 1 SSL.com2028-02-24Revoked

Cross-signed versions

No certificate in the CCADB has the same subject and public key as Trustwave Global Certification Authority with a different issuer, so a client has to carry Trustwave Global Certification Authority itself in its root store to trust it.

CRL and OCSP addresses

In the root certificate

Trustwave Global 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/TWGCA.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 Certification Authority; the number in brackets is how many of them use each address.

  • CRL: http://crl.sslsecuretrust.com/TWGCA.crl (1)
  • OCSP: http://ocsp.sslsecuretrust.com/ (1)

What happens when it expires

Trustwave Global 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 Certification Authority by common name (Trustwave Global 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 Certification Authority" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 97552015F5DDFC3C8788C006944555408894450084F100867086BC1A2BB58DC8

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 2F8F364FE1589744215987A52A9AD06995267FB5

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 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 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 "97:55:20:15:F5:DD:FC:3C:87:88:C0:06:94:45:55:40:88:94:45:00:84:F1:00:86:70:86:BC:1A:2B:B5:8D:C8"

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 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.

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-trustwave-global-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=97:55:20:15:F5:DD:FC:3C:87:88:C0:06:94:45:55:40:88:94:45:00:84:F1:00:86:70:86:BC:1A:2B:B5:8D:C8

FAQ

Is Trustwave Global 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 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 Certification Authority issued?

The CCADB lists 18: 1 valid, 0 expired and 17 revoked. The newest valid one is SSL.com TLS RSA Root CA 2022, valid until 2042-08-21.

Is Trustwave Global 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

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