Opens in a new tab

Google Workspace SPF, DKIM and DMARC setup

Google Workspace sends your team’s Gmail with your own address as the bounce address, so it needs both parts: Google in your SPF record, and a DKIM key you generate in the Admin console and publish as a TXT record. Until you do, Gmail signs your mail with a Google domain that does not align with yours.

SPFinclude:_spf.google.com
DKIMTXT at google._domainkey
Bounce domainYour own domain — SPF aligns
Set up inAdmin console → Apps → Google Workspace → Gmail → Authenticate email

Is your domain set up for Google Workspace?

We read your SPF record, look for Google Workspace’s DKIM key and check DMARC. Nothing is stored.

SPF for Google Workspace

Google’s record is include:_spf.google.com. Google recommends ending the record with ~all, and says a change can take up to 48 hours to take effect everywhere.

If you have no SPF record yet, publish this TXT record on @ (the domain itself):

v=spf1 include:_spf.google.com ~all

If you already have one, add include:_spf.google.com to it, before the ~all or -all at the end. A domain must have exactly one SPF record: a second one makes both fail.

include:_spf.google.com uses 1 of the 10 DNS lookups an SPF record is allowed (measured 27 September 2026). Past 10, receivers fail SPF for all of your mail. What is inside include:_spf.google.com, and whether you need it →

DKIM for Google Workspace

In the Admin console, go to Apps → Google Workspace → Gmail → Authenticate email, pick the domain and generate a key. Choose 2048 bits if your DNS host accepts it; Google recommends it. The default prefix (selector) is google.

Publish the TXT record it shows, then go back and click Start authentication. Nothing is signed until you do — the most common reason Google Workspace DKIM “does not work”.

Without your own key, Gmail signs outgoing mail with a gappssmtp.com domain, which passes DKIM but does not align with your domain for DMARC.

NameTypeValue
google._domainkeyTXTv=DKIM1; k=rsa; p=<key from the Admin console>

The exact values come from Google Workspace; copy them from there. Placeholders are in angle brackets.

Bounce domain and DMARC

Because Gmail uses your own domain as the bounce address and signs with your own key once DKIM is on, Google Workspace mail passes DMARC on both SPF and DKIM. It is usually the easiest sender to get right — the risk is the other services sending as your domain.

No DMARC record yet? Start with one that only reports, read the reports for a couple of weeks, then tighten it: build it with the DMARC generator.

Common mistakes

  • Publishing the key but never clicking Start authentication.
  • A 2048-bit key is longer than 255 characters. Some DNS hosts need it split into several quoted strings; if yours cannot, use 1024 bits.
  • Adding a second SPF record for Google instead of adding include:_spf.google.com to the existing one.

Questions

Do I need DKIM if SPF already passes?

Yes. SPF breaks when mail is forwarded, and Gmail and Yahoo require bulk senders to have both. DKIM with your own key is what keeps Google Workspace mail passing DMARC after a forward.

How long until DKIM starts working?

Google says up to 48 hours after you publish the record and click Start authentication. The status then reads “Authenticating email with DKIM”.

Sources

Checked against Google Workspace’s own documentation on 25 September 2026:

See every service’s mail pass or fail

Point your DMARC reports at us and we name every server sending as your domain, with what passes, what fails and the exact fix. Free for your first domain.

Create a free account