Root certificate · Google Trust Services

GTS Root R4

GTS Root R4 is a root CA certificate operated by Google Trust Services (ECDSA P-384, valid until 2036-06-22, SHA-256 71CCA539). 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	—	No

The CCADB lists no EV policy OID for GTS Root R4.

Not included Chrome

Status: Not included

Removed Mozilla

Status: Removed

Removed Apple

Status: Removed

Included Microsoft

Status: Included
Trusted EKUs: Server Authentication, Client Authentication, Secure Email, Time Stamping

"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=GTS Root R4,O=Google Trust Services LLC,C=US
SHA-256: 71CCA5391F9E794B04802530B363E121DA8A3043BB26662FEA4DCA7FC951A4BD
SHA-1 (Windows thumbprint): 2A1D6027D94AB10A1C4D915CCD33A0CB3E2D54CB
SPKI SHA-256: 9847E5653E5E9E847516E5CB818606AA7544A19BE67FD7366D506988E8D84347
Valid from: 2016-06-22
Expires: 2036-06-22
Key: ECDSA P-384
Signature algorithm: ecdsa-with-SHA384
Serial number: 6E47A9C88B94B6E8BB3B2AD8A2B2C199
Country: US
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.gtsr4.demosite.pki.goog · expired: https://expired.gtsr4.demosite.pki.goog · revoked: https://revoked.gtsr4.demosite.pki.goog
CCADB record: A004189
PEM: google-trust-services-gts-root-r4-71cca539.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists no intermediate CA certificate signed directly by GTS Root R4.

Cross-signed versions

1 certificate(s) in the CCADB have the same subject and public key as GTS Root R4 but a different issuer. A server can send one of them so that clients which trust the issuing root, but not GTS Root R4, can still build a chain.

Signed by	CA owner	Expires	Status
GlobalSign Root CA crt.sh	GlobalSign nv-sa	2028-01-28	Valid

CRL and OCSP addresses

In the root certificate

GTS Root R4 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/gtsr4/gtsr4.crl
http://c.pki.goog/r/r4.crl

What happens when it expires

GTS Root R4 is valid until 2036-06-22, about 9.6 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 GTS Root R4 by common name (GTS Root R4) 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 "GTS Root R4" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 71CCA5391F9E794B04802530B363E121DA8A3043BB26662FEA4DCA7FC951A4BD

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

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

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 "71:CC:A5:39:1F:9E:79:4B:04:80:25:30:B3:63:E1:21:DA:8A:30:43:BB:26:66:2F:EA:4D:CA:7F:C9:51:A4:BD"

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 Google Trust Services LLC → GTS Root R4.

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-gts-root-r4-71cca539.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=71:CC:A5:39:1F:9E:79:4B:04:80:25:30:B3:63:E1:21:DA:8A:30:43:BB:26:66:2F:EA:4D:CA:7F:C9:51:A4:BD

FAQ

Is GTS Root R4 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 GTS Root R4 expire?

On 2036-06-22, about 9.6 years after the 2026-11-10 data snapshot.

How many intermediate certificates has GTS Root R4 issued?

The CCADB lists no intermediate certificate signed directly by GTS Root R4.

Is GTS Root R4 cross-signed?

Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by GlobalSign Root CA; 1 of them are still valid.

Other roots from Google Trust Services

GlobalSign ECDSA P-256 · 2038-01-19
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

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