DMARC for Google Workspace
In Google Workspace, DMARC passes for your domain once Google signs your mail with your own DKIM key. Getting there takes three steps that bounce between Google and your DNS host: generate the DKIM key in the Google Admin console, publish it (along with SPF) at your domain host, then go back to the Admin console and click Start authentication. DMARC itself has no Admin console setting. As Google puts it, "You don't need to do anything in your Google Admin console to set up DMARC." You add it as a TXT record at your DNS host, ideally after SPF and DKIM have been working for at least 48 hours.
The order of work
- SPF at your DNS host.
- DKIM: Admin console, then DNS, then Admin console again.
- Wait at least 48 hours.
- A reports mailbox, then DMARC at
p=noneat your DNS host. - Read the reports, fix other senders, then move toward enforcement.
Why the order matters in general is covered in The right order: SPF, DKIM, DMARC, then BIMI.
SPF record for Google Workspace
Publish one TXT record at your domain. A typical Google Workspace record is:
example.com. TXT "v=spf1 include:_spf.google.com ~all"
Google recommends ~all, which is also our default for sending domains (Softfail vs fail (~all vs -all)). If other services send as you, add their includes to this same record. A second v=spf1 record breaks SPF (Multiple SPF records (why that is invalid)).
Two lines on Google's SPF page are looser than the standard. It says a record "can have up to 10 include: tags." The real limit is 10 DNS-querying terms in total, nested ones included (The 10-lookup limit and SPF permerror). It also says ~all tells receivers "to mark messages as spam." What a receiver does with a softfail is up to the receiver. Writing the full record is covered in How to write an SPF record.
Google Workspace DKIM: generate, publish, start
This is the step that makes DMARC work for Workspace mail, because it's what puts your domain in the DKIM signature. Set up DKIM in the Google Admin console.
1. Generate the key in the Admin console
Sign in as a super administrator. Go to Menu > Apps > Google Workspace > Gmail > Authenticate email, pick your domain under Selected domain, and click Generate New Record.
- Key length: choose 2048 if your DNS host supports 2048-bit keys. Choose 1024 only if it doesn't (1024-bit vs 2048-bit DKIM keys).
- Prefix selector: the default is
google. Change it only if your domain already has a DKIM key with that prefix.
Google's note on this step: "Do not click Start Authentication yet."
If you've just turned on Gmail for a new organization, you must wait 24–72 hours before you can get your DKIM key.
2. Publish the TXT record at your DNS host
Copy the two values Google shows: the host name (for example, google._domainkey) and the TXT value, which starts with v=DKIM1; k=rsa; p=. Create the TXT record at your domain host.
A 2048-bit key is longer than 255 characters, and some DNS hosts need a value that long split into several strings. Google links its own help on this from the setup page. Selector records in general are covered in DKIM selectors and DNS records.
3. Click Start authentication
Back on Authenticate email, select the domain and click Start authentication. When it's working, the status changes to "Authenticating email with DKIM." DKIM can take up to 48 hours to start working after you add the key, and the Admin console may keep showing a reminder to update your DNS records for up to 48 hours.
Each domain needs its own key. If you send from more than one domain, to complete these steps for each one.
Check that it worked
Send a message to someone else who uses Gmail or Google Workspace, open it in their inbox, and look at the original message for dkim=pass with your domain. Google warns: "You can't verify DKIM is on by sending yourself a test message."
Wait 48 hours
Google's DMARC page: "DKIM and SPF should be authenticating messages for at least 48 hours before turning on DMARC." Use that time to set up the reports mailbox.
Google Workspace DMARC setup
Set up a reports mailbox first
Google suggests a group or a dedicated mailbox, and says, "We don't recommend using your own email address." A third-party reporting service is the other option Google names. Aggregate reports are XML files meant for software to read. If your reports go to an address on another domain, that domain has to publish an authorization record (rua, ruf, and report authorization).
Check your other senders
Before you publish, list every service that sends as your domain: newsletters, CRM, invoicing, help desk. Google's DMARC page says to make sure each provider passes SPF and DKIM and that the provider's envelope sender domain matches your domain. The more durable fix is to have each one DKIM-sign with your domain (How to add a third-party sender without breaking DMARC).
Publish the record
Create a TXT record at your DNS host with the host name _dmarc. Some hosts add your domain automatically, others expect _dmarc.example.com, so check how yours works. Start in monitoring mode:
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"
p=none doesn't change how receivers handle your mail. It gets you reports. Each domain you use can have its own policy and its own reporting address. The general walk-through is on our DMARC setup page, and every tag is explained in DMARC tags explained: p, sp, np, adkim, aspf, rua, ruf, fo, and t.
Don't copy Google's example record as a template. It reads v=DMARC1; p=reject; rua=mailto:postmaster@example.com, mailto:dmarc@example.com; pct=100; adkim=s; aspf=s. That's enforced, strict, and uses pct, which the current standard removed. Relaxed alignment typically provides sufficient spoofing protection (Relaxed vs strict alignment).
Moving toward enforcement
An outdated rollout still in circulation is p=none for one week, then quarantine for a small percentage of messages using pct, then raising the percentage.
Two differences from the current standard:
pctis gone. The current standard removed it. Don't add it, and remove it from older records. How to phase in enforcement without it is in pct is historic: how to phase in DMARC enforcement now.- One week is Google's figure. Getting to an enforcement decision may take many months of reports, and for domains whose users post to mailing lists, spend at least a month at
none, then an equally long period at quarantine.
Move up when your reports show that your legitimate mail passes with alignment. The staged rollout is in A safe rollout: p=none to quarantine to reject.
If BIMI is on your list, it needs p=quarantine or p=reject. Google still requires that the policy not have a pct value below 100. That advice follows the older standard, where leaving pct out meant 100 (What is BIMI, and why DMARC comes first).
If mail starts bouncing
If people sending from your domain get this bounce:
5.7.26 Unauthenticated email from domain-name is not accepted due to domain's DMARC policy.
If a bounce says the DMARC policy for your domain is causing this issue, a message failed DMARC and your own policy asked the receiver to reject it. Check SPF and DKIM for that source and your alignment settings. A DMARC policy with strict alignment increases the likelihood that messages are rejected or sent to spam. Troubleshooting steps are in Mail started failing after we published DMARC and Microsoft 365 or Google Workspace setup issues.
Reports from Gmail
Aggregate reports, including those about mail you send to Gmail users, arrive at your rua address from receivers that send them. Don't expect failure reports from Gmail: Google's tag table says "Gmail doesn't support the ruf tag." What's inside an aggregate report is in A field-by-field walk-through of a DMARC aggregate report.
Gmail's requirements for senders who mail Gmail users, a separate topic from setting up your own Workspace domain, are in Google, Yahoo, and Microsoft sender requirements and Google and Yahoo sender requirements.
Mistakes worth avoiding
- Never clicking Start authentication, or clicking it before the DNS record resolves.
- Trying to generate a DKIM key in the first 24–72 hours after turning on Gmail.
- Adding a second SPF record for a marketing tool instead of merging the include.
- Pasting a 2048-bit key into a DNS host with a 255-character limit without splitting it.
- Publishing DMARC before SPF and DKIM have run for 48 hours.
- Sending
ruareports to an admin's own inbox. - Testing DKIM by emailing yourself.
Free DMARC account
Turn raw DMARC reports into a readable dashboard
Point your rua address to our platform and read the results by sender and source instead of opening XML files.
- Results grouped by sending source
- SPF, DKIM and alignment results per sender
- The original XML reports are still there to download
FAQ
Do I set up DMARC in the Google Admin console?
No. Add a TXT record at your domain host. DKIM is the part that's set up in the Admin console.
Where is DKIM in the Admin console?
Menu > Apps > Google Workspace > Gmail > Authenticate email.
Should I use a 1024- or 2048-bit DKIM key?
2048 if your DNS host supports it.
How long before DKIM works?
Up to 48 hours after you publish the key. Wait at least 48 hours of working SPF and DKIM before you publish DMARC.
Will Gmail send me failure (ruf) reports?
No. Gmail doesn't support ruf. You'll get aggregate reports if your record has rua.
Can I send DMARC reports to an address outside my domain?
Yes, if that domain publishes the authorization record for your domain. See rua, ruf, and report authorization.