A DMARC setup is the most effective way to stop other people sending email that pretends to come from your domain. It works together with two older records, SPF and DKIM, and it is no longer only a security nicety: Gmail, Yahoo and Outlook.com all enforce authentication rules for senders. The good news is that the whole job is a handful of DNS records, and you can do it safely in about eight weeks if you follow the right order.
My short answer: publish SPF, turn on DKIM, add a DMARC record with the policy set to monitor only, read the reports for two to four weeks, and only then move to quarantine and reject. The step people skip is checking every tool that sends email for you.
What Each Record Does
| Record | In plain language | Where it lives |
|---|---|---|
| SPF | A list of the servers allowed to send email for your domain | A TXT record on your domain |
| DKIM | A digital signature that proves a message was not altered and came from your domain | A TXT or CNAME record under a “selector” |
| DMARC | A policy that tells receivers what to do when SPF and DKIM fail, plus reports | A TXT record at _dmarc.yourdomain.com |
DMARC also checks alignment: the domain in the visible From address must match the domain that passed SPF or DKIM. A message can pass SPF and still fail DMARC if the domains do not align.
Why It Matters in 2026
- Gmail and Yahoo started enforcing bulk sender rules in February 2024, and Microsoft began enforcing them for Outlook.com, Hotmail and Live.com on May 5, 2025.
- For senders of roughly 5,000 or more messages a day to those consumer addresses, the rules require SPF, DKIM and a DMARC record of at least
p=none, with alignment, plus one-click unsubscribe on marketing email and low spam-complaint rates. - Smaller senders are not exempt from authentication: Google requires at least SPF or DKIM for all senders, and providers recommend all three for everyone.
- Cyber insurers ask about email controls too. See our guide to cyber insurance requirements.
Most small businesses send far fewer than 5,000 messages a day, so the real reasons to set this up are deliverability and protecting your brand from spoofing.
Before You Start (10 Minutes)
- List every system that sends email as your domain: your mailbox provider, marketing platform, helpdesk, CRM, invoicing tool, online store and website forms.
- Get access to your DNS, usually at your domain registrar or a service such as Cloudflare.
- Create a mailbox for reports, for example
dmarc-reports@yourdomain.com. - Save a copy of your current DNS records. A typo can break email, so you want a way back.
Step 1: SPF
SPF is one TXT record on your domain. You can only have one SPF record, so every sender goes inside the same one.
- Google Workspace:
v=spf1 include:_spf.google.com ~all - Microsoft 365:
v=spf1 include:spf.protection.outlook.com ~all - With a marketing tool added:
v=spf1 include:_spf.google.com include:[tool's include] ~all
Use the include value from each vendor’s own help page. The ~all ending is a soft fail, which is a good setting while you test, and many teams tighten it later.
Watch the limit: SPF allows at most 10 DNS lookups, and every include can add more. Check yours with a free SPF checker.
Step 2: DKIM
DKIM signs outgoing mail with a key stored in DNS.
- Google Workspace: in the Admin console, open the Gmail settings for email authentication, generate a key (choose 2,048 bits, which Google recommends), publish the TXT record at your DNS, then click to start authentication.
- Microsoft 365: in the Microsoft Defender portal, open the email authentication settings for DKIM, publish the two CNAME records it shows for your domain, then enable signing.
- Other tools: each marketing, helpdesk or invoicing platform gives you its own DKIM records to publish.
Menu names change from time to time, so follow your provider’s current help page.
Step 3: DMARC in Monitor Mode
Add a TXT record at _dmarc.yourdomain.com:
v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com
p=none means “do not block anything, just send me reports.” The rua address receives daily summaries in XML format, which are hard to read by eye, so use a free report analyzer or a DMARC reporting service.
Step 4: Read the Reports for Two to Four Weeks
The reports show every source sending mail as your domain and whether it passed. For each legitimate sender that fails, fix its SPF include or its DKIM record. Anything you do not recognise is either a forgotten tool or a spoofer.
Step 5: Move to Quarantine Gradually
When your legitimate senders pass, change the policy to p=quarantine with a percentage, and raise it over a few weeks:
v=DMARC1; p=quarantine; pct=25; rua=mailto:dmarc-reports@yourdomain.com
Go to 25%, then 50%, then 100%, and keep reading the reports.
Step 6: Move to Reject
When quarantine at 100% shows no problems, switch to p=reject. This is the setting that actually stops spoofed email from reaching recipients. Keep monitoring afterwards, because every new tool you adopt is a new sender.
A Safe Rollout Timeline
| When | Action |
|---|---|
| Week 0 | Publish SPF and enable DKIM for every sender |
| Week 1 | Add DMARC with p=none and reports |
| Weeks 1 to 4 | Read reports and fix failing legitimate senders |
| Weeks 5 to 6 | Move to quarantine at 25%, then 50%, then 100% |
| Week 7 onward | Move to reject and keep monitoring |
I would not compress this. The reports are what protect you from blocking your own invoices or newsletters.
Third-Party Senders: The Part People Forget
Most DMARC failures when you tighten the policy come from tools you forgot about. For each, set up custom domain authentication, so it signs with your domain:
- Email marketing platform: see our guide to email marketing software for e-commerce.
- Helpdesk: see our guide to helpdesk software.
- CRM, invoicing and online store: each has a domain or sender authentication page.
- Website contact forms: route them through an authenticated mail provider, not a plain server mail function.
How to Test It
Send a test email to a Gmail address, open the message, choose “Show original”, and look for SPF, DKIM and DMARC marked as PASS. Free tools such as MXToolbox and Google’s Admin Toolbox can also read your records.
Mistakes I Would Avoid
- Two SPF records on the same domain. Merge them into one.
- Going straight to
p=rejectbefore reading any reports. - Weak DKIM keys. Use 2,048 bits where your provider allows it.
- Forgetting subdomains. Use the
sp=tag if you send from subdomains and want a different policy. - Not editing DNS carefully. Mind the quotation marks and extra spaces, and keep your backup.
- Ignoring the reports after the first week.
What DMARC Does Not Do
DMARC protects other people from fake email that uses your domain. It does not filter phishing that arrives in your inbox. For that, you need email security software, so see our guide to the best email security software.
How I Researched This
I based the sender requirements on several independent 2026 guides covering the Google, Yahoo and Microsoft rules, and the record formats on the standard syntax for SPF, DKIM and DMARC. Admin menu names change often, and I have not configured every provider, so check the current help page of your mailbox provider before you change anything.
Frequently Asked Questions
Do I need DMARC if I send very little email?
It is still worth setting up. Providers recommend SPF, DKIM and DMARC for every sender, and it protects your domain from being spoofed.
What DMARC policy should I start with?p=none, which only monitors. Move to quarantine and then reject once your reports are clean.
Will DMARC break my email?
Not in monitor mode. Problems appear when you tighten the policy before fixing every legitimate sender, which is why the reports come first.
How long does the setup take?
Publishing the records takes under an hour. A safe rollout to p=reject usually takes six to eight weeks.
My Takeaway
If I had to reduce this guide to one habit, it would be to treat DMARC as a project with a timeline. Publish the records, read the reports, fix the senders and only then tighten the policy.
Disclaimer: This guide is informational. DNS changes can affect email delivery, so back up your records and check your provider’s documentation.

Leave a Reply