Step by step
- Sign in at
admin.google.comas an admin, and go to Apps, Google Workspace, Gmail, Authenticate email. - Pick your domain and click Generate new record. Keep the key length at 2048 bits and the prefix (the selector) as
google. - Google shows a host name,
google._domainkey, and a long value startingv=DKIM1; k=rsa; p=. Add it as a TXT record at your DNS provider, exactly as shown. - Wait until the record is visible. Check it below with the selector
google. Google says it can take up to 48 hours. - Back in the Admin console, click Start authentication. The status should change to "Authenticating email with DKIM".
When it doesn't work
- The DNS provider cuts the value. A 2048-bit key is longer than 255 characters. Most providers split it for you; a few don't accept it. If yours won't, generate a 1024-bit key instead. It still works, it's just weaker.
- Extra quotes or spaces. Copy the value in one go. A missing character means the key doesn't verify.
- The host name doubled. Some providers add your domain to the host on their own, so
google._domainkey.example.combecomesgoogle._domainkey.example.com.example.com. Enter onlygoogle._domainkey. - Never clicked Start authentication. The record is there but Gmail isn't using it. This is the most common one.
Why it matters
DKIM puts a signature on every email that only your domain's key can produce. DMARC passes when either SPF or DKIM passes on your own domain, and DKIM survives forwarding where SPF often doesn't. Since 2024 Gmail and Yahoo expect both from anyone sending in volume. Next step: publish a DMARC record.