Root certificate · SSL.com

Secure Global CA

Secure Global CA is a root CA certificate operated by SSL.com (RSA 2048, valid until 2029-12-31, SHA-256 4200F504). As of the latest CCADB data it is trusted for TLS server authentication by 1 of 4 major root stores: Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeRemoved RemovedNo—No
MozillaRemoved RemovedNo—No
AppleBlocked BlockedNo—No
MicrosoftIncluded IncludedYes—Yes

The CCADB lists EV policy OID 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

Blocked Apple

Status
Blocked

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication, Code Signing, Secure Email, Time Stamping
Not-before cutoff
2021-08-01 (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=Secure Global CA,O=SecureTrust Corporation,C=US
SHA-256
4200F5043AC8590EBB527D209ED1503029FBCBD41CA1B506EC27F15ADE7DAC69
SHA-1 (Windows thumbprint)
3A44735AE581901F248661461E3B9CC45FF53A1B
SPKI SHA-256
2596904DC4D699AE20C2CEF4DCE47F285937D77464AC370746F52DEA76BA0C28
Valid from
2006-11-07
Expires
2029-12-31
Key
RSA 2048
Signature algorithm
sha1WithRSAEncryption
Serial number
75622A4E8D48A894DF413C8F0F8EAA5
Country
US
Trust bits (CCADB)
Server Authentication, Client Authentication, Secure Email, Time Stamping
EV policy OIDs (CCADB)
2.16.840.1.114404.1.1.2.4.1 · TLS EV capable: Yes
Test websites
valid: https://test-sgca.sslsecuretrust.com · expired: https://expired-sgca-rsa.sslsecuretrust.com · revoked: https://revoked-sgca-rsa.sslsecuretrust.com
CCADB record
A000182
PEM
ssl-com-secure-global-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 5 intermediate CA certificates signed directly by Secure Global CA: 1 currently valid, 1 expired and 3 revoked (revoked includes those whose parent was revoked).

Showing 5 of 5: 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.com2029-12-28Valid
Trustwave Secure Global Extended Validation CA, Level 1 SSL.com2025-08-09Expired
VikingCloud SG TLS EV CA, Level 1 SSL.com2029-12-22Revoked
Trustwave S/MIME CA, Level 2 SSL.com2028-12-22Revoked
Trustwave Secure E-mail CA, Level 1 SSL.com2028-05-07Revoked

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

  • CRL: http://crl.securetrust.com/SGCA.crl

Full CRL this CA publishes (CCADB)

  • http://crl.vikingcloud.com/SGCA.crl

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 1 valid intermediates signed by Secure Global CA; the number in brackets is how many of them use each address.

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

What happens when it expires

Secure Global 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 Secure Global CA by common name (Secure Global 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: Blocked)

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 "Secure Global CA" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 4200F5043AC8590EBB527D209ED1503029FBCBD41CA1B506EC27F15ADE7DAC69

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 3A44735AE581901F248661461E3B9CC45FF53A1B

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 "Secure Global CA"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "Secure Global 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 "42:00:F5:04:3A:C8:59:0E:BB:52:7D:20:9E:D1:50:30:29:FB:CB:D4:1C:A1:B5:06:EC:27:F1:5A:DE:7D:AC:69"

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 → Secure Global 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.

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-secure-global-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=42:00:F5:04:3A:C8:59:0E:BB:52:7D:20:9E:D1:50:30:29:FB:CB:D4:1C:A1:B5:06:EC:27:F1:5A:DE:7D:AC:69

FAQ

Is Secure Global CA trusted by Chrome, Firefox, Safari and Windows?

As of 2026-11-10, Microsoft trust it for TLS server authentication; Chrome, Mozilla, Apple do not.

When does Secure Global CA expire?

On 2029-12-31, about 3.1 years after the 2026-11-10 data snapshot.

How many intermediate certificates has Secure Global CA issued?

The CCADB lists 5: 1 valid, 1 expired and 3 revoked. The newest valid one is SSL.com TLS RSA Root CA 2022, valid until 2029-12-28.

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

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