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 349DFA40). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Included Included | Yes | — | No |
| Mozilla | Included Included | Yes | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | No |
The CCADB lists no EV policy OID for GTS Root R4.
Included Chrome
- Status
- Included
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=GTS Root R4,O=Google Trust Services LLC,C=US
- SHA-256
349DFA4058C5E263123B398AE795573C4E1313C83FE68F93556CD5E8031B3C7D- SHA-1 (Windows thumbprint)
77D30367B5E00C15F60C3861DF7CE13B92464D47- SPKI SHA-256
9847E5653E5E9E847516E5CB818606AA7544A19BE67FD7366D506988E8D84347- Valid from
- 2016-06-22
- Expires
- 2036-06-22
- Key
- ECDSA P-384
- Signature algorithm
- ecdsa-with-SHA384
- Serial number
203E5C068EF631A9C72905052- Country
- US
- 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.gtsr4.demosite.pki.goog· expired:https://expired.gtsr4.demosite.pki.goog· revoked:https://revoked.gtsr4.demosite.pki.goog - CCADB record
- A007408
- PEM
- google-trust-services-gts-root-r4.pem
Intermediate CAs issued by this root
The CCADB lists 10 intermediate CA certificates signed directly by GTS Root R4: 5 currently valid, 0 expired and 5 revoked (revoked includes those whose parent was revoked).
Showing 10 of 10: 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.
| Intermediate | Operated by | Expires | Status |
|---|---|---|---|
| WE4 | Google Trust Services LLC | 2029-02-20 | Valid |
| WE3 | Google Trust Services LLC | 2029-02-20 | Valid |
| WE2 | Google Trust Services LLC | 2029-02-20 | Valid |
| AE1 | Google Trust Services LLC | 2029-02-20 | Valid |
| WE1 | Google Trust Services LLC | 2029-02-20 | Valid |
| GTS CA 2P2 | Google Trust Services LLC | 2027-09-30 | Revoked |
| GTS CA 2A1 | Google Trust Services LLC | 2025-09-30 | Revoked |
| GTS Y4 | Google Trust Services LLC | 2030-01-30 | Revoked |
| GTS Y4 | Google Trust Services LLC | 2028-11-01 | Revoked |
| GTS X4 | Google Trust Services LLC | 2026-06-22 | Revoked |
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.crlhttp://c.pki.goog/r/r4.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 5 valid intermediates signed by GTS Root R4; the number in brackets is how many of them use each address.
- CRL:
http://c.pki.goog/r/r4.crl(5)
None of the valid intermediates under this root lists an OCSP responder.
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: 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 "GTS Root R4" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 349DFA4058C5E263123B398AE795573C4E1313C83FE68F93556CD5E8031B3C7D
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 77D30367B5E00C15F60C3861DF7CE13B92464D47
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 "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 "34:9D:FA:40:58:C5:E2:63:12:3B:39:8A:E7:95:57:3C:4E:13:13:C8:3F:E6:8F:93:55:6C:D5:E8:03:1B:3C:7D"
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.
# 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.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=34:9D:FA:40:58:C5:E2:63:12:3B:39:8A:E7:95:57:3C:4E:13:13:C8:3F:E6:8F:93:55:6C:D5:E8:03:1B:3C:7D
FAQ
Is GTS Root R4 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.
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 10: 5 valid, 0 expired and 5 revoked. The newest valid one is WE4, valid until 2029-02-20.
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