google is the DKIM selector Google Workspace suggests when you generate a key: a TXT record that lets Gmail sign mail from your domain with it. You can pick another prefix — Google advises one if google is already taken.
| Whose | Google Workspace — mailbox provider |
| Selector | google |
| Published as | A TXT with the key Google generates; Google keeps the private half |
| Key | 2048-bit if your DNS host supports it, 1024 if not; many older setups are still 1024 |
| Rotation | By hand: Generate New Record, publish it, then Start authentication |
| Before you set it up | Until you set it up, mail from your domain is not signed with a key of your own, so DKIM does not align for DMARC |
| Where to find it | Admin console → Apps → Google Workspace → Gmail → Authenticate email → Generate New Record |
| Can it go? | Google recommends leaving the record in place; after publishing a new one, wait at least four days before removing the old. |
Is Google Workspace’s key on your domain?
Enter a domain — or paste the DKIM-Signature header of a message it sent: we look for Google Workspace’s key under google, check it, and name every other key the domain publishes.
The records
What Google Workspace asks you to publish, with its own values in place of the placeholders:
google._domainkey.example.com TXT v=DKIM1; k=rsa; p=<public key>
How it works
You need to wait 24 to 72 hours after turning Gmail on before you can generate a key, and authentication can take up to 48 hours to start. The Admin console may keep saying the DNS record needs updating for as long, even when it is right.
Common mistakes
- A 2048-bit key is longer than the 255 characters one TXT string holds: split it into quoted strings, in order — or use 1024 at hosts that cannot.
- Clicking Start authentication before the record is published.
- An outbound gateway that adds a footer after Gmail signs: the body no longer matches.
Setting up Google Workspace from scratch? Its SPF, DKIM and DMARC records, and a check of all three.
Questions
Why is my google._domainkey key only 1024 bits?
It was generated when 1024 was the default or your host could not take longer records. Generate a new 2048-bit record under a new prefix, publish it, start authentication, and remove the old one after four days.
Sources
Checked on 27 September 2026 against these official sources:
- Set up DKIM — Security & data protection — knowledge.workspace.google.com
- Troubleshoot DKIM issues — knowledge.workspace.google.com
- Turn off DKIM — knowledge.workspace.google.com