← Back to blog
Provider Setup · Google Workspace DKIM

DKIM for Google Workspace: the actual setup steps

DKIM for Google Workspace is generated in the Admin console, not your DNS panel. Here are the exact steps, and why authentication is the first thing worth checking on any deliverability problem.
3 min read · Updated August 2026

Turning on DKIM for Google Workspace happens in the Admin console, not in your domain's DNS panel. Go to Apps, then Google Workspace, then Gmail, then Authenticate email. That screen generates the key and gives you the exact DNS record to publish.

Google recommends generating a 2048-bit key wherever your domain host supports it, stating in its own documentation that longer keys are more secure than shorter ones. The generated record publishes as a TXT record at google._domainkey, the fixed selector Google Workspace uses.

The order that actually gets this working

  1. Generate the key in the Admin console (Apps > Google Workspace > Gmail > Authenticate email), choosing 2048-bit if your DNS host allows it.
  2. Publish the TXT record at google._domainkey with your DNS host.
  3. Wait. Google states DKIM can take up to 48 hours to start authenticating, and the Admin console may keep showing a DNS warning inside that window even once the record is correct.
  4. Turn on authentication in the Admin console only after the record is confirmed live, not before.
How I check it I confirm the DNS record resolves independently first, with the Google Workspace DNS checker, then check the Admin console's own status, because the two can disagree for up to 48 hours without either one being wrong.

Why this is worth doing before anything else

Authentication resolves in minutes against a DNS lookup, while reputation and engagement take an afternoon or longer to read. It is the first of the six checks I run on any deliverability problem for exactly that reason: rule out what is fast before what is slow, not what feels most likely.

Questions I get asked a lot

Why does the Admin console still warn me after I added the DNS record?

Google states this warning can persist for up to 48 hours after a correct record is added, purely from propagation delay, and should be ignored if the record itself is confirmed correct.

Should I use a 1024-bit or 2048-bit key?

Google recommends 2048-bit wherever your DNS host supports the longer TXT value, stating explicitly that longer keys are more secure.

Do I need SPF and DMARC too, or is DKIM enough?

DKIM alone is not enough for Google's own bulk-sender requirements above 5,000 messages a day to personal Gmail accounts, which require SPF, DKIM and DMARC together with From-domain alignment, not any one of the three in isolation.

Not sure authentication is actually clean?
Run the free diagnostic and I will confirm SPF, DKIM and DMARC together before we look anywhere slower.
Start the free diagnostic →
Julian Turgelski
The Diagnostic Blog
hello@julianturgelski.com
Julian's diagnostic console