Root certificate · Google Trust Services
GTS Root R2
GTS Root R2 is a root CA certificate operated by Google Trust Services (RSA 4096, valid until 2036-06-22, SHA-256 8D25CD97). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Removed Removed | No | — | No |
| Mozilla | Included Included | No | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | No |
The CCADB lists no EV policy OID for GTS Root R2.
Removed Chrome
- Status
- Removed
Included Mozilla
- Status
- Included
- Trust bits
- 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, emailProtection
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 R2,O=Google Trust Services LLC,C=US
- SHA-256
8D25CD97229DBF70356BDA4EB3CC734031E24CF00FAFCFD32DC76EB5841C7EA8- SHA-1 (Windows thumbprint)
9A44497632DBDEFAD0BCFB5A7B17BD9E56092494- SPKI SHA-256
55F77DE41C03792428F8D518C55104225BE43A5598D926A528AD653E1CCEC7BF- Valid from
- 2016-06-22
- Expires
- 2036-06-22
- Key
- RSA 4096
- Signature algorithm
- sha384WithRSAEncryption
- Serial number
203E5AEC58D04251AAB1125AA- 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.gtsr2.demosite.pki.goog· expired:https://expired.gtsr2.demosite.pki.goog· revoked:https://revoked.gtsr2.demosite.pki.goog - CCADB record
- A007407
- PEM
- google-trust-services-gts-root-r2.pem
Intermediate CAs issued by this root
The CCADB lists 6 intermediate CA certificates signed directly by GTS Root R2: 2 currently valid, 0 expired and 4 revoked (revoked includes those whose parent was revoked).
Showing 6 of 6: 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 |
|---|---|---|---|
| MR1 | Google Trust Services LLC | 2029-02-20 | Valid |
| WR5 | Google Trust Services LLC | 2029-02-20 | Valid |
| GTS CA 1D9 | Google Trust Services LLC | 2027-09-30 | Revoked |
| GTS CA 1D8 | Google Trust Services LLC | 2027-09-30 | Revoked |
| GTS Y2 | Google Trust Services LLC | 2028-11-01 | Revoked |
| GTS X2 | Google Trust Services LLC | 2026-06-22 | Revoked |
Cross-signed versions
No certificate in the CCADB has the same subject and public key as GTS Root R2 with a different issuer, so a client has to carry GTS Root R2 itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
GTS Root R2 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/gtsr2/gtsr2.crlhttp://c.pki.goog/r/r2.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 2 valid intermediates signed by GTS Root R2; the number in brackets is how many of them use each address.
- CRL:
http://c.pki.goog/r/r2.crl(2)
None of the valid intermediates under this root lists an OCSP responder.
What happens when it expires
GTS Root R2 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 R2 by common name (GTS Root R2) 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 R2" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 8D25CD97229DBF70356BDA4EB3CC734031E24CF00FAFCFD32DC76EB5841C7EA8
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 9A44497632DBDEFAD0BCFB5A7B17BD9E56092494
Linux (ca-certificates follows Mozilla: Included)
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 R2"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "GTS Root R2"
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 "8D:25:CD:97:22:9D:BF:70:35:6B:DA:4E:B3:CC:73:40:31:E2:4C:F0:0F:AF:CF:D3:2D:C7:6E:B5:84:1C:7E:A8"
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 R2.
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-r2.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=8D:25:CD:97:22:9D:BF:70:35:6B:DA:4E:B3:CC:73:40:31:E2:4C:F0:0F:AF:CF:D3:2D:C7:6E:B5:84:1C:7E:A8
FAQ
Is GTS Root R2 trusted by Chrome, Firefox, Safari and Windows?
As of 2026-11-10, Apple, Microsoft trust it for TLS server authentication; Chrome, Mozilla do not.
When does GTS Root R2 expire?
On 2036-06-22, about 9.6 years after the 2026-11-10 data snapshot.
How many intermediate certificates has GTS Root R2 issued?
The CCADB lists 6: 2 valid, 0 expired and 4 revoked. The newest valid one is MR1, valid until 2029-02-20.
Is GTS Root R2 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
- 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 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