Root certificate · Google Trust Services

GTS Root R3

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

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 R3,O=Google Trust Services LLC,C=US
SHA-256: 15D5B8774619EA7D54CE1CA6D0B0C403E037A917F131E8A04E1E6B7A71BABCE5
SHA-1 (Windows thumbprint): 30D4246F07FFDB91898A0BE9496611EB8C5E46E5
SPKI SHA-256: 4179EDD981EF747477B49626408AF43DAA2CA7AB7F9E082C1060F84096774348
Valid from: 2016-06-22
Expires: 2036-06-22
Key: ECDSA P-384
Signature algorithm: ecdsa-with-SHA384
Serial number: 6E47A9C76CA9732440890F0355DD8D1D
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.gtsr3.demosite.pki.goog · expired: https://expired.gtsr3.demosite.pki.goog · revoked: https://revoked.gtsr3.demosite.pki.goog
CCADB record: A004188
PEM: google-trust-services-gts-root-r3-15d5b877.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 R3.

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

GTS Root R3 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/gtsr3/gtsr3.crl
http://c.pki.goog/r/r3.crl

What happens when it expires

GTS Root R3 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 R3 by common name (GTS Root R3) 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 R3" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 15D5B8774619EA7D54CE1CA6D0B0C403E037A917F131E8A04E1E6B7A71BABCE5

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 30D4246F07FFDB91898A0BE9496611EB8C5E46E5

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

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 "15:D5:B8:77:46:19:EA:7D:54:CE:1C:A6:D0:B0:C4:03:E0:37:A9:17:F1:31:E8:A0:4E:1E:6B:7A:71:BA:BC:E5"

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 R3.

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-r3-15d5b877.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=15:D5:B8:77:46:19:EA:7D:54:CE:1C:A6:D0:B0:C4:03:E0:37:A9:17:F1:31:E8:A0:4E:1E:6B:7A:71:BA:BC:E5

FAQ

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

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

How many intermediate certificates has GTS Root R3 issued?

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

Is GTS Root R3 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 R2 RSA 4096 · 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