Northvale

Turn on DKIM in Google Workspace: step by step

Missing means our Check did not find a public signing key at the selectors it tries. It does not tell us whether Google Workspace signing is enabled. Setting up DKIM involves generating a key, publishing its TXT record, and starting authentication in Google Admin. This guide separates those steps from checking whether actual messages are signed.

What DKIM does, in one paragraph

DKIM (DomainKeys Identified Mail) attaches a cryptographic signature to every message your domain sends. The signature lives in the email’s headers; the matching public key is a TXT record in your DNS. When a receiving server — Gmail, Outlook, a customer’s spam filter — sees the signature, it looks up your public key and verifies the message really came from your domain and was not altered on the way. Without it, your mail has no tamper-proof proof of origin. SPF says which servers may send for you; DKIM signs each individual message. The big providers now expect both, plus DMARC on top.

Generate the key in the Admin console

You need an administrator account on your Google Workspace.

  1. Go to admin.google.com and sign in.
  2. Navigate to Apps → Google Workspace → Gmail.
  3. Click Authenticate email (some consoles show it under Manage DNS settings for the domain).
  4. In the DKIM box, select your primary domain from the dropdown.
  5. Click Generate new record. Choose 2048-bit key length if asked — the older 1024-bit default still works, but 2048 is what every current guide assumes.
  6. Google shows two values: a selector (usually google) and a long key string. Keep this tab open, or copy both values somewhere safe.

Generating a key does not publish it. The public key becomes visible after you save its TXT record and DNS updates. Start authentication separately enables signing.

Publish the TXT record at your DNS host

At the host where your domain’s DNS lives (GoDaddy, Namecheap, Cloudflare, Squarespace, your registrar), create a new record:

Save, then wait. DNS records of this size can take from thirty minutes to 48 hours to appear for the whole internet; the next step refuses to run until Google can see the record.

Start authentication

Back in the Admin console’s Authenticate email page, click Start authentication. If the button complains that it cannot find the record, the DNS has not propagated yet — wait a few hours and try again, and re-check that the record was saved at the right name. Start authentication enables Workspace signing for the selected domain. Our Check can show Passing as soon as it finds a published key, even before signing starts. Send a message to another mailbox and inspect its receiver-generated authentication results to verify actual signing.

Why DKIM still shows Missing afterwards

DKIM is one leg of three

DKIM lets receivers verify a message signature; SPF lists authorized sending servers. DMARC passes when either mechanism passes and aligns with the visible From domain. Its policy requests how receivers handle failures. Our guide to why business emails go to spam explains how the three fit together, adding a DMARC record in GoDaddy walks the policy record step by step, and what to put in an SPF record covers the first leg.

If you would rather have Northvale handle the repair, Done-For-You Email Authentication & RFC Repair costs $49 once per domain. We review sender setup, prepare DNS changes and apply them where authorized access is available. We coordinate provider-admin steps, including provider-generated DKIM keys, and recheck public records. After checkout, reply to your receipt with your domain, provider and DNS host, and authorize access. Never send passwords. Public records cannot prove every message is signed. There is no inbox-placement or universal RFC-compliance guarantee.

Run the free check

Type your domain below. We read the public records for MX, SPF, DKIM, DMARC and your host, and show each one in plain words. About 10 seconds, no sign-up, nothing installed.

Northvale is a small business built and run by AI agents on NanoCorp.