Root certificate · Google Trust Services

GlobalSign

GlobalSign is a root CA certificate operated by Google Trust Services (ECDSA P-256, valid until 2038-01-19, SHA-256 BEC94911). As of the latest CCADB data it is trusted for TLS server authentication by 1 of 4 major root stores: Microsoft.

Data updated Nov 10, 2026

Root store status

Root store	Status	Trusted for TLS	Distrust for TLS after	Constrained
Chrome	Not included Not included	No	—	No
Mozilla	Removed Removed	No	—	No
Apple	Removed Removed	No	—	No
Microsoft	Included Included	Yes	—	Yes

The CCADB lists no EV policy OID for GlobalSign.

Not included Chrome

Status: Not included

Removed Mozilla

Status: Removed

Removed Apple

Status: Removed

Included Microsoft

Status: Included
Trusted EKUs: Server Authentication, Client Authentication, Code Signing, Secure Email, Time Stamping
Not-before cutoff: 2020-06-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: Google Trust Services LLC
Subject: CN=GlobalSign,O=GlobalSign,OU=GlobalSign ECC Root CA - R4
SHA-256: BEC94911C2955676DB6C0A550986D76E3BA005667C442C9762B4FBB773DE228C
SHA-1 (Windows thumbprint): 6969562E4080F424A1E7199F14BAF3EE58AB6ABB
SPKI SHA-256: 08B3A6335FCE5EF48F8F0E543986C07FD18A3B1226129F61864BBD5BDD1F1CC9
Valid from: 2012-11-13
Expires: 2038-01-19
Key: ECDSA P-256
Signature algorithm: ecdsa-with-SHA256
Serial number: 2A38A41C960A04DE42B228A50BE8349802
Trust bits (CCADB): Server Authentication, Client Authentication, Secure Email, Time Stamping
EV policy OIDs (CCADB): not EV-enabled · TLS EV capable: No
Test websites: valid: https://good.gsr4.demosite.pki.goog · expired: https://expired.gsr4.demosite.pki.goog · revoked: https://revoked.gsr4.demosite.pki.goog
CCADB record: A000288
PEM: google-trust-services-globalsign-bec94911.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists no intermediate CA certificate signed directly by GlobalSign.

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

GlobalSign 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.pki.goog/root-r4.crl

What happens when it expires

GlobalSign is valid until 2038-01-19, about 11.2 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 GlobalSign by common name (GlobalSign) 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: Removed)

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 "GlobalSign" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: BEC94911C2955676DB6C0A550986D76E3BA005667C442C9762B4FBB773DE228C

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 6969562E4080F424A1E7199F14BAF3EE58AB6ABB

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 "GlobalSign"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "GlobalSign"

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 "BE:C9:49:11:C2:95:56:76:DB:6C:0A:55:09:86:D7:6E:3B:A0:05:66:7C:44:2C:97:62:B4:FB:B7:73:DE:22:8C"

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

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 google-trust-services-globalsign-bec94911.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=BE:C9:49:11:C2:95:56:76:DB:6C:0A:55:09:86:D7:6E:3B:A0:05:66:7C:44:2C:97:62:B4:FB:B7:73:DE:22:8C

FAQ

Is GlobalSign 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 GlobalSign expire?

On 2038-01-19, about 11.2 years after the 2026-11-10 data snapshot.

How many intermediate certificates has GlobalSign issued?

The CCADB lists no intermediate certificate signed directly by GlobalSign.

Is GlobalSign cross-signed?

No. The CCADB has no certificate with the same subject and public key signed by another CA.

Other roots from Google Trust Services

GlobalSign ECDSA P-256 · 2038-01-19
GTS Root R1 RSA 4096 · 2036-06-22
GTS Root R1 RSA 4096 · 2036-06-22
GTS Root R2 RSA 4096 · 2036-06-22
GTS Root R2 RSA 4096 · 2036-06-22
GTS Root R3 ECDSA P-384 · 2036-06-22
GTS Root R3 ECDSA P-384 · 2036-06-22
GTS Root R4 ECDSA P-384 · 2036-06-22
GTS Root R4 ECDSA P-384 · 2036-06-22

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