Google’s own authority, behind Google Cloud’s managed certificates, Firebase, and one of the authorities Cloudflare, Shopify, Render and DigitalOcean use. Its CAA value is pki.goog — the one most often missing when a Cloudflare-hosted site’s renewal fails.
| Run by | Google Trust Services LLC, United States |
| CAA value | pki.goog |
| CAA parameters | accounturi and validationmethods — it “may” limit issuance by them; its account URL format is not published |
| ACME | https://dv.acme-v02.api.pki.goog/directory — with an External Account Binding key from your account |
| Cost | Free — through Google Cloud’s Public CA, with a Google Cloud project for the account key |
| Certificates | Domain validated (DV) only, IP addresses included. Wildcards with DNS validation. |
| Longest certificate | 90 days by default, or any number of days from 1 to 90 on request; its policy caps them at 93 |
| Issuer names on its certificates | WR1–WR5, WE1–WE5 |
| Issues for | Google Cloud and Firebase; one of the authorities Cloudflare, Shopify, Render and DigitalOcean use |
May Google Trust Services issue for your domain?
Enter a domain or hostname: we read its CAA records as Google Trust Services must — its own, or the nearest parent’s — and say whether they let it issue, for wildcards too, and which authority issued the certificate it serves now.
The CAA record for Google Trust Services
Published on your domain, this lets Google Trust Services issue for it and for every name under it that has no CAA records of its own. Every authority not named must refuse. Keep the records for any other authority you use — your host’s or CDN’s included.
example.com. CAA 0 issue "pki.goog"
An issue record covers wildcard certificates too. To let Google Trust Services issue wildcards and no one else, add an issuewild record — once there is one, issue records stop counting for wildcards — and an iodef address for authorities to report refused requests to:
example.com. CAA 0 issuewild "pki.goog"
example.com. CAA 0 iodef "mailto:security@example.com"
How it reads CAA
A lookup that fails is never permission: Google Trust Services refuses rather than issue when it cannot read the records. An unknown tag with the critical flag stops it too.
Cloudflare publishes it as pki.goog; cansignhttpexchanges=yes — the parameter asked for signed-exchange (SXG) certificates, which Google stops issuing around 30 September 2026. Plain pki.goog lets it issue ordinary certificates.
Getting a certificate
Create an external account key with gcloud publicca external-account-keys create — it must be used within 7 days — and give it to your ACME client with the directory above. There is no charge. Quotas are per Google Cloud project: 100 certificate requests an hour.
When a CAA record stops it
Its documentation gives no wording: a CAA refusal comes back as the ACME error type caa, and Google Cloud’s load balancers show FAILED_CAA_FORBIDDEN or FAILED_CAA_CHECKING.
What changed
- March 2024 — Moved to its W-series intermediates: WR1 and WE1 replaced GTS CA 1P5 and the other old names, which are now revoked.
- 13 April 2026 — Stopped issuing certificates with TLS client authentication, with no exceptions.
- July 2026 — Added ACME profiles (standard and minimal) and the dns-account-01 challenge.
- About 30 September 2026 — Stops issuing signed-exchange (SXG) certificates; ordinary certificates are unaffected.
Worth knowing
- Its intermediates say “Google Trust Services”; its roots “Google Trust Services LLC”. GTS Root R1 and R4 are cross-signed by GlobalSign for older devices.
- Chrome has removed its roots R2 and R3, under which WR5 and WE5 sit.
Questions
Why is pki.goog in my CAA records when I never added it?
Because Cloudflare adds it: once a zone on Cloudflare has any CAA record, Cloudflare publishes records for the four authorities it uses — Google Trust Services among them. They do not show in its dashboard, but every lookup sees them.
Is Google Trust Services really free?
Yes. Google charges nothing for its public certificates; you need a Google Cloud project only to create the ACME account key.
Sources
Checked on 27 September 2026 against these official sources:
- Google Trust Services CP/CPS for TLS, version 6.9 — pki.goog
- How do I configure CAA to explicitly authorize issuance by Google Trust Services — developers.google.com
- Request a certificate using Public CA and an ACME client — docs.cloud.google.com
- Add CAA records — developers.cloudflare.com