Google Workspace will send your company’s mail from the first day, without complaint, and without ever mentioning that it is signing that mail on behalf of a domain that is not yours. Open the headers of a message from a freshly created Workspace account and you will find a DKIM signature, valid and correct, for a Google-owned domain ending in gappssmtp.com. It is a perfectly good signature. It simply belongs to Google, and DMARC, which cares only about your domain, gives you no credit for it.
Fixing this takes three DNS records and one button. The button is the step people forget. This guide covers all four, in the order that works, and then the Workspace-specific corners where authenticated mail quietly stops being authenticated.
What you are setting up
| Record | DNS name | Where the value comes from |
|---|---|---|
| SPF | example.com (the bare domain) | Google’s documented include |
| DKIM | google._domainkey.example.com | Generated for you in the Google Admin console |
| DMARC | _dmarc.example.com | You write it |
You need a super administrator login for the Google Admin console and access to the domain’s DNS. Before changing anything, run a domain health check to see which of the three already exist. Domains set up through a registrar’s Workspace bundle sometimes have SPF in place and nothing else.
Step 1: SPF
If Google Workspace is the only thing that sends mail for your domain, the SPF record is:
example.com. TXT "v=spf1 include:_spf.google.com ~all"If other services send as your domain too, they go in the same record. A domain may have only one SPF record; a second one invalidates both.
example.com. TXT "v=spf1 include:_spf.google.com include:servers.other-sender.example ~all"Take each additional include from that provider’s own documentation. The Google include costs several of your ten permitted DNS lookups by itself, since it expands into further includes, so there is less room than the short record suggests. The SPF checker shows the running total, and the SPF generator will merge senders into one record.
For mail sent by people in Gmail, the envelope sender is the user’s own address, so SPF passes and aligns with your domain. That is one of the two ways to pass DMARC. Do not stop there: SPF fails whenever a recipient forwards your mail, and DKIM is what covers that case.
Step 2: Generate and publish the DKIM key
This is done in the Admin console, not in DNS alone.
- Sign in at
admin.google.comand go to Apps → Google Workspace → Gmail → Authenticate email. - Choose your domain from the Selected domain menu. Each domain in the account has its own key.
- Click Generate new record. Choose a 2048-bit key if your DNS host supports TXT values of that length; nearly all do. Leave the prefix selector at its default,
google, unless that name is already in use. - The console now shows a DNS host name and a TXT record value. Copy both exactly as displayed.
The record you add to DNS will have this shape:
google._domainkey.example.com. TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A...(copy the full value from the Admin console)"The p= value is your public key, and it is unique to your account. Do not copy it from this page, from a forum, or from another domain. A 2048-bit key is longer than the 255 characters a single DNS string can hold; most DNS hosts split it automatically, but if yours truncates it, the signature will fail. If your DNS is at Cloudflare, see the Cloudflare DNS guide for how long TXT values are entered there.
On a brand-new Workspace account, the console may decline to generate a key for the first day or three after Gmail is turned on. That is normal. Come back later.
Step 3: Press the button
Publishing the key does not turn on signing. Return to the same Authenticate email page and click Start authentication. The status should change to say that email is being authenticated with DKIM.
If the console reports that it cannot find the record, DNS has not caught up; it can take up to 48 hours, though minutes is more usual. Confirm that the record is visible from outside with the DKIM checker, using the selector google, and try again.
The key in DNS is a lock with no one assigned to turn it. Until you click Start authentication, Google goes on signing as Google.
Step 4: Verify with a real message
Send a message from your Workspace account to any Gmail address. Open it, choose Show original from the message menu, and read the summary at the top. You want three lines:
SPF: PASS with IP 209.85.x.x
DKIM: 'PASS' with domain example.com
DMARC: 'PASS'The detail that matters is the DKIM domain. If it shows your domain, signing is aligned. If it shows something ending in gappssmtp.com, the button in step 3 was not pressed or has not taken effect. For mail received somewhere other than Gmail, paste the headers into the email header analyzer and look for header.d= in the DKIM result.
Step 5: Publish DMARC
With SPF and DKIM both aligned, add the policy record:
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"Start at p=none. It changes nothing about delivery and causes receivers, Google among them, to send daily aggregate reports to the rua address. The DMARC generator will build the record, and how to configure DMARC covers every tag. If you would like the reports parsed for you, add a SpoofKiller address to the rua tag as described in the reporting setup guide.
This is not optional for larger senders. Since 2024, Google has required anyone sending bulk mail to personal Gmail accounts, which it defines as roughly five thousand messages a day or more, to have SPF, DKIM, and a DMARC record, with the From domain aligned to one of the two. Smaller senders need at least SPF or DKIM. Meeting the stricter standard regardless of size is the sensible course.
Where Workspace mail goes unauthenticated
Mail that people write in Gmail is now in good order. The trouble, when it comes, is from everything else that uses your domain.
Secondary domains and domain aliases
If your account includes more than one domain, each needs its own SPF record, its own DKIM key generated from the Selected domain menu, and its own DMARC record. Authenticating the primary domain does nothing for the others.
Other services sending as your domain
The newsletter platform, the CRM, and the billing system do not send through Google. Each must be configured separately to sign with your domain. Your DMARC reports will show them as sources that pass SPF and DKIM for someone else’s domain; alignment explained covers what that means, and the guides for SendGrid and Postmark give two worked examples.
Google Groups and mailing lists
When a message passes through a group or mailing list that alters it, by adding a footer or a subject prefix, the original DKIM signature can break, and SPF no longer matches the original sender. Such mail may fail DMARC through no fault of the author. Expect to see a little of this in your reports. It is not impersonation.
Printers, scanners, and applications
Devices and scripts that send mail as your domain through some other route, such as an ISP’s mail server, will fail. Route them through an authenticated path, or have them use a separate subdomain with its own records. The reports will reveal them; they always do.
From none to reject
Leave the policy at none for a few weeks and read what comes back. When every source you recognize is passing, move to quarantine and then reject, following the staged plan for reaching p=reject. DMARC monitoring names the services behind the IP addresses and tells you when the failures that remain are only forwarding and strangers.
Then leave the DKIM record alone. The most common way a working Workspace setup breaks is a DNS cleanup in which someone deletes a TXT record named google._domainkey because it looked unfamiliar. It was load-bearing.

