Do small businesses need DMARC? The email sender rules explained
The short answer: if your business sends fewer than 5,000 emails a day, DMARC isn’t required of you by Gmail or Outlook.com. But every sender to Gmail and Yahoo must already have SPF or DKIM, and a DMARC record with p=none costs nothing, doesn’t change how your mail is delivered, and starts telling you who is sending email in your name. Set up SPF, then DKIM in your email provider, then DMARC, in that order. The rest of this post shows what each rule says, what it means for a small business, and the exact records to add.
Everything below was checked on the companies’ own pages and the standards on 19 November 2026; the links are at the end.
What the big mailbox providers require
Three providers set the rules most small businesses run into: Google (Gmail), Yahoo (Yahoo Mail) and Microsoft (Outlook.com, Hotmail and Live).
| Everyone who sends to them | Senders of more than 5,000 emails a day | |
|---|---|---|
| Gmail (from 1 February 2024) | SPF or DKIM, a secure connection, spam complaints below 0.3% | SPF and DKIM, a DMARC record (p=none is allowed), the From address matching SPF or DKIM, one-click unsubscribe on marketing email |
| Yahoo (from February 2024) | SPF or DKIM, spam complaints below 0.3% | SPF and DKIM, DMARC of at least p=none that passes, one-click unsubscribe. Yahoo says “bulk senders” and gives no number. |
| Microsoft Outlook.com, Hotmail, Live (from 5 May 2025) | The 2025 rules cover high-volume senders only | SPF and DKIM must pass, DMARC of at least p=none matching SPF or DKIM |
A few details matter:
- Google counts per domain, and it’s permanent. Mail from the same main domain counts toward the 5,000, and Google says a sender that reaches the bulk level once is treated as a bulk sender for good. Since November 2025 Gmail has been stepping up enforcement on mail that doesn’t meet the rules, which can mean temporary or permanent rejection.
- Microsoft sends non-compliant bulk mail to Junk first, and says it will reject it at a date not yet announced.
- These rules are about mail sent to personal accounts (@gmail.com, @yahoo.com, @outlook.com and so on). Google says its sender guidelines don’t apply to mail sent to Google Workspace business accounts.
What this means for a business of 1 to 10 people
Most small businesses send a few dozen to a few hundred emails a day: quotes, invoices, replies, maybe a monthly newsletter. That puts you under the 5,000 line, so the strict rules don’t apply to you. Two things still do:
- The rule for everyone. Gmail and Yahoo require every sender to have SPF or DKIM. If your quotes or invoices go to customers’ Gmail accounts without either, they are the ones most likely to land in spam or not arrive.
- Someone else can send as you. Without DMARC, nothing tells receiving mail servers what to do with an email that claims to be from
[email protected]but wasn’t sent by you. A fake invoice from your own address is a common scam, and your customers are the ones who get it.
Most mail problems at small businesses come from the services that send for you without you thinking about it: the newsletter tool, the invoicing app, the booking system, your website’s contact form. Each one needs to be covered by your SPF record or sign with DKIM for your domain, or its email can fail the checks.
What to set up, in order
You add these at the company that runs your domain’s DNS: usually where you bought the domain, or Cloudflare if you use it. Our free email security check reads what you have now, names your email provider when it recognises it, and gives you the records to copy.
1. SPF: one record listing everyone who sends for you
SPF is a single TXT record on your domain listing the servers allowed to send your email. If you use Google Workspace, Google’s own example is:
v=spf1 include:_spf.google.com ~all
For Microsoft 365, Microsoft’s example is:
v=spf1 include:spf.protection.outlook.com -all
If more than one service sends for you, put them all in one record, for example Google’s own example for using both:
v=spf1 include:_spf.google.com include:spf.protection.outlook.com ~all
Rules worth knowing:
- Only one SPF record per domain. Two records make SPF fail everywhere. Merge them.
- No more than 10 DNS lookups. Each
include:(anda,mx,exists,redirect) counts; past 10, SPF fails with a permanent error. Long lists of includes are the usual cause. - How it ends.
~all(soft fail) and-all(fail) both work. Google recommends~all; Microsoft recommends-all.
Your newsletter or invoicing service will tell you its own include: value in its help pages, or ask you to set up DKIM instead.
2. DKIM: switch it on in your email provider
DKIM signs each email so the receiver can check it really came from you and wasn’t changed. You don’t write this record yourself: your email provider makes the key, you publish it in DNS, then you switch signing on.
- Google Workspace: in the Admin console, go to Apps › Google Workspace › Gmail › Authenticate email, generate a key (2048-bit if your DNS host supports it), add it as a TXT record at
google._domainkey, then press Start authentication. - Microsoft 365: Microsoft doesn’t sign mail from your own domain until you turn it on. In the Microsoft Defender portal, open Email authentication settings › DKIM, add the two CNAME records it shows you (
selector1._domainkeyandselector2._domainkey), then turn on signing. - Every other service that sends for you (newsletter, invoicing, booking) has its own DKIM setting, usually under “domain authentication” or “sender authentication”. Turn it on for each.
3. DMARC: start with p=none, move to quarantine
DMARC is one TXT record at _dmarc.yourbusiness.com. Start with this, using an address at your own domain that you can read:
Host: _dmarc
Type: TXT
Value: v=DMARC1; p=none; rua=mailto:[email protected]
p=nonetells receivers to handle your mail exactly as before. Nothing gets blocked.rua=is where receivers send daily reports (XML files) listing every server that sent mail using your domain, and whether it passed. They’re hard to read by hand; a DMARC report service turns them into a list.
After a few weeks, when the reports show that all your real senders (your mailbox, newsletter, invoicing) pass, change the policy:
v=DMARC1; p=quarantine; rua=mailto:[email protected]
p=quarantine asks receivers to put mail that fails into spam; p=reject asks them to refuse it. Don’t jump straight to quarantine: if your invoicing app isn’t set up yet, your own invoices go to your customers’ spam folders.
The DMARC standard changed in May 2026
DMARC was first written up in RFC 7489 in 2015, an informational document rather than a formal standard. In May 2026 it was replaced by RFC 9989, a proposed standard that obsoletes RFC 7489. For a small business, the records above still work the same way: v=DMARC1, p=none, p=quarantine, p=reject and rua= are all still there. One change you may notice in older guides: the pct= tag (apply the policy to only a percentage of mail) is gone, replaced by a t= tag for testing. The starter record above uses neither.
Check what you have
- Run the free email security check on your domain. It reads SPF, DMARC, MX and DKIM from public DNS, says what’s missing in plain words, and gives you records to copy, including a starter DMARC record with
p=none. - Run the free site health check on your website. It includes the same email checks, plus your SSL certificate and domain expiry dates, so nothing quietly runs out.
Neither check sends email or changes anything; they read public records, the same ones every mail server reads.
Questions
Do I need DMARC if I send fewer than 5,000 emails a day?
Gmail and Outlook.com don’t require it below that level, and Yahoo only requires it of bulk senders. It’s still worth adding a p=none record: it changes nothing about delivery and shows you who sends email as your domain.
Will adding DMARC break my email?
Not with p=none. Receivers keep handling your mail as before. Problems only start if you move to p=quarantine or p=reject before every service that sends for you passes SPF or DKIM.
Can I have two SPF records, one for each service?
No. A domain may have only one. Combine the include: parts into one record that starts with v=spf1 and ends with one ~all or -all.
Sources (checked 19 November 2026)
- Google, Email sender guidelines and Email sender guidelines FAQ: the rules for all senders and for senders of more than 5,000 messages a day, permanent bulk status, enforcement from November 2025.
- Yahoo, Sender best practices: requirements from February 2024; no number given for bulk.
- Microsoft, Outlook’s new requirements for high-volume senders: over 5,000 emails a day, from 5 May 2025, Junk first and rejection later.
- Google, Set up SPF and Set up DKIM; Microsoft, Set up SPF and Set up DKIM: the example records, the 10-lookup limit,
~alland-all. - RFC 9989, DMARC (May 2026, proposed standard), which obsoletes RFC 7489 (2015). RFC 7208, SPF: one record per domain.
From OOO Works, which is building done-for-you services for small businesses worldwide. Nothing is on sale yet; the free tools are open to anyone.