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 B085D70B). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeIncluded IncludedYes2027-09-14Yes
MozillaIncluded IncludedYes—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—No

Chrome stops trusting TLS certificates under this root whose SCTs are dated after 2027-09-14 (sct_not_after). The CCADB lists no EV policy OID for GlobalSign.

Included Chrome

Status
Included
Distrust for TLS after
2027-09-14

Included Mozilla

Status
Included
Trust bits
Websites
EV policy OIDs
not EV-enabled
First included in
NSS 3.74 / Firefox 97
Inclusion bug
#1675821

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication, Secure Email

"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
B085D70B964F191A73E4AF0D54AE7A0E07AAFDAF9B71DD0862138AB7325A24A2
SHA-1 (Windows thumbprint)
6BA0B098E171EF5AADFE4815807710F4BD6F0B28
SPKI SHA-256
08B3A6335FCE5EF48F8F0E543986C07FD18A3B1226129F61864BBD5BDD1F1CC9
Valid from
2012-11-13
Expires
2038-01-19
Key
ECDSA P-256
Signature algorithm
ecdsa-with-SHA256
Serial number
203E57EF53F93FDA50921B2A6
Trust bits (CCADB)
Server Authentication, Client Authentication, Secure Email
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
A007405
PEM
google-trust-services-globalsign.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 11 intermediate CA certificates signed directly by GlobalSign: 4 currently valid, 0 expired and 7 revoked (revoked includes those whose parent was revoked).

Showing 11 of 11: 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
WE1 Google Trust Services LLC2029-02-20Valid
WE4 Google Trust Services LLC2029-02-20Valid
WE2 Google Trust Services LLC2029-02-20Valid
WE3 Google Trust Services LLC2029-02-20Valid
GTS CA 2D5 Google Trust Services LLC2027-09-30Revoked
GTS CA 2D4 Google Trust Services LLC2027-09-30Revoked
GIAG4 ECC Google Trust Services LLC2028-11-01Revoked
Google Internet Authority G3 ECC Google Trust Services LLC2027-06-15Revoked
GlobalSign ECC256 EV SSL CA - G3 Google Trust Services LLC2025-04-30Revoked
GlobalSign ECC256 SSL CA - G3 Google Trust Services LLC2025-04-30Revoked
GlobalSign EC Administration CA1 Google Trust Services LLC2023-11-13Revoked

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://c.pki.goog/r/gsr4.crl
  • http://crl.pki.goog/gsr4/gsr4.crl

Used by the intermediates it issued

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

  • CRL: http://c.pki.goog/r/gsr4.crl (4)

None of the valid intermediates under this root lists an OCSP responder.

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. Root programs can stop trusting it before it expires: Chrome 2027-09-14.

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

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 6BA0B098E171EF5AADFE4815807710F4BD6F0B28

Linux (ca-certificates follows Mozilla: Included · Trusted for TLS)

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 "B0:85:D7:0B:96:4F:19:1A:73:E4:AF:0D:54:AE:7A:0E:07:AA:FD:AF:9B:71:DD:08:62:13:8A:B7:32:5A:24:A2"

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.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=B0:85:D7:0B:96:4F:19:1A:73:E4:AF:0D:54:AE:7A:0E:07:AA:FD:AF:9B:71:DD:08:62:13:8A:B7:32:5A:24:A2

FAQ

Is GlobalSign trusted by Chrome, Firefox, Safari and Windows?

Yes. As of 2026-11-10, Chrome, Mozilla (Firefox), Apple (Safari) and Microsoft (Windows) all trust it for TLS server authentication. Distrust-after dates already set: Chrome 2027-09-14.

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 11: 4 valid, 0 expired and 7 revoked. The newest valid one is WE1, valid until 2029-02-20.

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

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