Google Workspace
DMARC Google Workspace setup: add the record step by step
Set up DMARC for Google Workspace: one TXT record at _dmarc on your domain host, starting at p=none, then a staged move to enforcement.
Before you start
A DMARC Google Workspace setup is one TXT record named _dmarc.example.com, added at your domain host. Google's help says you don't need to do anything in the Admin console, so the person who makes this change is whoever can edit the domain's DNS.
Set up SPF for Google Workspace and DKIM for Google Workspace first. Google asks for at least 48 hours between turning them on and adding DMARC, and warns that without them messages "will probably have delivery issues". DKIM, unlike DMARC, does need the Admin console.
Run your domain through the DMARC checker. If a record already exists, review its reports before you change it.
Steps
-
Create a place for reports. Make a group or a dedicated mailbox. A Google Group must accept email from outside your organization or reports won't arrive.
-
Check third-party senders. Each message needs SPF or DKIM to pass with alignment to From; both aligned mechanisms are not required. Prefer aligned DKIM. Add a provider to root SPF only if it uses that domain as its envelope sender; otherwise follow its custom bounce-domain instructions.
-
Prepare one DMARC record. If a policy exists, preserve
p=, alignment and report addresses; add your monitoredruadestination to that record. Only for a first policy, use:TXTv=DMARC1; p=none; rua=mailto:dmarc@example.com
-
Publish it. At your domain host, open the page for DNS TXT records and add or update one record:
- Type:
TXT - Host:
_dmarc.example.com - Value: the record from step 3
Some hosts add the domain for you. If yours does, enter
_dmarcalone so the saved name isn't doubled. Keep one DMARC record at this name: RFC 9989 tells receivers to discard them all if a name returns several. - Type:
-
Check each sending domain. An explicit child DMARC record overrides inherited policy. Otherwise, the applicable parent’s
spcontrols subdomains, or itspapplies whenspis absent. -
Read the reports daily for at least a week. Google says a week of daily reports usually represents all your mail streams.
-
Assess enforcement after legitimate senders align. Quarantine can send failing mail to spam; reject can refuse it. For a new monitored deployment, consider quarantine without
pct:TXTv=DMARC1; p=quarantine; rua=mailto:dmarc@example.com
After reviewing the results and remaining risks, assess
p=reject. RFC 9989 removedpct; percentage values cannot provide a reliable partial rollout. Preserve existing report destinations when editing the policy.
Confirm it worked
-
Run the checker after the previous DNS answer’s TTL (cache lifetime) expires.
-
Send a message from your domain to someone else on Gmail. Next to Reply, click More, then Show original. Find
Authentication-Resultsand look fordmarc=pass. -
Wait for reports. They usually arrive once a day by email, and each receiving server sends its own. Success means every legitimate source passes SPF or DKIM with alignment, meaning its authenticated domain matches your
From:domain. Learn how to read aggregate reports.
Common problems
-
Bounces with
5.7.26. The sender can getUnauthenticated email from domain-name is not accepted due to domain's DMARC policy.Check that the mail passes SPF or DKIM, then check alignment, as covered in the 5.7.26 error. -
You copied Google’s sample. Keep a working existing policy and alignment settings. Correct each
ruaURI to includemailto:. If the sample caused legitimate delivery failures, diagnose authentication and alignment first. The owner may choose temporary monitoring or relaxed alignment while repairing them, accepting reduced protection; restore enforcement after validation. -
Reports never reach another domain's mailbox. If the
ruaaddress is in a different domain, that domain must authorize it with a TXT record namedexample.com._report._dmarc.OTHER-DOMAINand this value:TXTv=DMARC1;A report service publishes this on its own side.
-
Group mail shows "via". After
quarantineorreject, mail sent to a Google Group appears as'Sender Name' via Group-Name. This keeps Groups delivery from triggering your policy. -
Mailing lists. RFC 9989 says domains whose users may post to Internet mailing lists should not publish
p=reject. If you want it anyway, it says to publishp=nonefor at least a month, thenp=quarantinefor as long. -
Bulk sending to Gmail. See sender requirements for high-volume mail.