This warning means the DMARC record for your Google Workspace domain is missing or set to p=none, so receiving servers are not asked to filter emails that fail authentication. To fix it, confirm that SPF and DKIM pass for your domain, then change the _dmarc TXT record at your domain host to p=quarantine, following the gradual rollout Google recommends.
Nothing is broken: your mail still flows. The warning simply says your domain is not yet protected against people sending emails in your name. Below are the exact steps from Google's own documentation, in the order that avoids sending your own messages to spam.
What the warning means
Email checking tools such as MxToolbox raise "DMARC Quarantine/Reject policy not enabled" in two cases:
- there is no DMARC record at
_dmarc.yourdomain.com; - there is one, but its policy is
p=none, which only collects reports.
Google Workspace does not create a DMARC record for you. Google's help is explicit that DMARC is set up at your domain host (your registrar or DNS provider), not in the Admin console. So if you set up Workspace and never touched DMARC, the warning is expected.
Why it is worth fixing
- Protection: with
quarantineorreject, messages pretending to come from your domain without passing SPF or DKIM go to spam or are refused. - Deliverability: Gmail requires SPF, DKIM and DMARC (
p=noneis accepted) from senders above 5,000 messages a day, and Microsoft applies a similar rule for Outlook.com. A complete setup helps at any volume. - Brand logo: BIMI, which can show your logo in some inboxes, requires
p=quarantineorp=rejectwith the policy applied to all mail.
Step 1: check SPF
For a domain that sends only through Google Workspace, Google recommends:
v=spf1 include:_spf.google.com ~allAdd any other service that sends as your domain (CRM, newsletter, invoicing, website forms) to that same record. Keep a single SPF record per domain, and stay within SPF's limit of 10 DNS lookups. Our free SPF checker counts them for you.
Step 2: turn on DKIM in the Admin console
This is the step most often skipped. You need super administrator rights.
- In the Admin console, go to Menu > Apps > Google Workspace > Gmail > Authenticate email.
- Choose your domain under Selected domain and click Generate New Record.
- Choose a 2048-bit key if your DNS host supports it (otherwise 1024), keep the default prefix selector
google, and click Generate. - Copy the host name (
google._domainkey) and the TXT value (it starts withv=DKIM1; k=rsa; p=). - Add that TXT record at your domain host.
- Back in the Admin console, click Start authentication. The status should change to show that email is being authenticated with DKIM.
Timing matters. You cannot generate the key until 24 to 72 hours after Gmail is turned on, and DKIM can take up to 48 hours to start working after the DNS record is published.
Check your domain for free. AttackScout reads your SPF, DMARC and the standard
Step 3: publish DMARC in monitoring mode
Google advises waiting 48 hours after SPF and DKIM are set up before adding DMARC. Then add a TXT record at your domain host:
- Name/host:
_dmarc(some hosts want the full_dmarc.yourdomain.com; check after saving that your host did not add the domain twice) Value:
v=DMARC1; p=none; rua=mailto:[email protected]
Create a Google Group or a dedicated mailbox for the reports. Note that Gmail does not support the ruf tag for failure reports, so there is no point adding it for Google.
For the exact clicks at your DNS host, see our guides for GoDaddy and Hostinger.
Step 4: move to quarantine, gradually
Google's recommended rollout has three stages:
- Monitor for about a week with
p=none, reviewing reports daily. One week is usually enough to see every mail stream; give it longer if some tools send only monthly. Switch to
p=quarantinefor a small share of messages, usingpct. Google gives the example of starting around 10% for a small organization and 1% for a large one:v=DMARC1; p=quarantine; pct=10; rua=mailto:[email protected]- Raise
pctstep by step until 100, checking reports each time.
The warning is about the policy itself, so it should clear once your record says quarantine or reject. The pct steps are there for your safety, not for the checker.
A note on pct: Google still documents it, but the updated DMARC standard published in May 2026 (RFC 9989) removed the tag. Receivers that follow the new text may apply your policy to all messages regardless. Treat each pct step as a precaution, not a guarantee, and only raise the policy when reports are clean.
Should you go to p=reject?
reject means failing messages are never delivered, not even to spam. It offers the strongest protection, but any sender you forgot loses its emails silently. Many organizations stay at quarantine for a while before deciding. If you choose reject, do it only after several weeks at quarantine with nothing legitimate failing.
Step 5: confirm the fix
- Run
nslookup -type=TXT _dmarc.yourdomain.comand check there is exactly one record, with the policy you set. - Send a message from Workspace to a personal Gmail account, open it, choose Show original, and look for
PASSnext to SPF, DKIM and DMARC. - If something fails, paste the full header into the Messageheader tool of the Google Admin Toolbox to see which check failed and why.
You can also re-run our free DMARC checker.
Frequently asked questions
Can I set DMARC from the Google Admin console?
No. The Admin console handles DKIM, but the DMARC record lives at your domain host as a TXT record.
My third-party tool fails DMARC after I enabled quarantine. What now?
Its messages are probably signed with the tool's own domain rather than yours. Most email platforms let you set up DKIM for your domain or add an SPF include. Until then, temporarily lower pct or return to p=none.
Do subdomains need their own DMARC record?
No. Without an sp= tag, subdomains follow the main domain's policy.
Check your domain for free. In under a minute and without an account, AttackScout checks your Google Workspace email setup, your certificate and your website, and gives you the next fix to make. Check my domain
Technical details
Exact configuration. A TXT record on the _dmarc name of your domain:
_dmarc.your-domain.com TXT "v=DMARC1; p=none; rua=mailto:[email protected]"Why. DMARC (RFC 7489) tells the receiving server what to do with an email that claims to come from your domain but passes neither SPF nor DKIM with that same domain name (alignment). p=none observes without blocking; p=quarantine sends to spam; p=reject refuses. rua receives the aggregate reports that show who sends in your name: tighten the policy only after reading them.
To check it yourself. Exactly one line must start with v=DMARC1:
dig +short TXT _dmarc.your-domain.comReference: https://www.rfc-editor.org/rfc/rfc7489
Sources
Accessed 12 November 2026.
- Google Workspace, Set up DMARC: https://knowledge.workspace.google.com/admin/security/set-up-dmarc
- Google Workspace, Recommended DMARC rollout: https://knowledge.workspace.google.com/admin/security/recommended-dmarc-rollout
- Google Workspace, Set up DKIM: https://knowledge.workspace.google.com/admin/security/set-up-dkim
- Google Workspace, Set up SPF: https://knowledge.workspace.google.com/admin/security/set-up-spf
- Google, Email sender guidelines: https://support.google.com/mail/answer/81126?hl=en
- Google, Trace an email with its full header: https://support.google.com/mail/answer/29436?hl=en
- MxToolbox, DMARC Policy Not Enabled: https://mxtoolbox.com/problem/dmarc/dmarc-policy-not-enabled
- Microsoft, Fix NDR error 550 5.7.515 in Outlook.com: https://support.microsoft.com/en-us/outlook/fix-ndr-error-550-5-7-515-in-outlook-com
- IETF, RFC 9989 (DMARC, May 2026): https://www.rfc-editor.org/info/rfc9989
- IETF, RFC 7208 (SPF): https://www.rfc-editor.org/rfc/rfc7208