What is DMARC? How to stop criminals from sending email as you
Every one of our client domains is set to DMARC p=reject, which tells mail systems everywhere to refuse any message that falsely claims to come from that domain. What is DMARC? It’s a single line of text in your domain’s DNS that turns email authentication from a suggestion into a rule.
Since 2024, Google and Yahoo have required DMARC for bulk senders, and Microsoft followed for Outlook.com in 2025. Even if you never send bulk email, an enforced policy protects your clients from fake messages in your name and helps your real mail get delivered.
Key takeaways
- Three email settings, called SPF, DKIM and DMARC, work together to prove a message really came from your company’s domain.
- A DMARC setting of p=none only watches and reports. Fake mail sent in your name gets stopped only at the quarantine or reject setting.
- Gmail, Yahoo and Outlook.com now require DMARC from companies that send email in bulk.
- Tighten the setting in stages. DMARC reports show every service that really sends mail as you, so you can find them all before you start blocking.
Talk to an advisor
Ask about your own setup.
We ask what you’re trying to accomplish and tell you what we’d look at first. It costs nothing to talk, and no price comes up on this call.
What is DMARC, and where do SPF and DKIM fit?
Email was designed decades ago with no built-in way to prove who sent a message. Three DNS records add that proof:
- SPF (Sender Policy Framework) lists the servers and services allowed to send email for your domain, such as Microsoft 365, your billing system and your marketing platform.
- DKIM (DomainKeys Identified Mail) adds a digital signature to each message so the receiver can confirm it wasn’t altered and was sent by an authorized system.
- DMARC (Domain-based Message Authentication, Reporting and Conformance) ties them together. It checks that the domain in the visible From address lines up with SPF or DKIM, tells receivers what to do when a message fails, and sends you reports about who is sending mail as your domain.
The key part of a DMARC record is the policy: p=none (monitor only), p=quarantine (treat failures as suspicious, usually the junk folder) or p=reject (refuse failing messages).
What Google, Yahoo and Microsoft require
The big mailbox providers have moved from recommending authentication to requiring it:

| Provider | In effect | What it requires |
|---|---|---|
| Gmail | February 1, 2024 | Every sender must set up SPF or DKIM, use TLS and keep spam complaint rates below 0.3%. Senders of more than 5,000 messages a day also need SPF, DKIM and a DMARC record, with the From domain aligned, plus one-click unsubscribe for marketing mail. |
| Yahoo | 2024 | Bulk senders must publish a valid DMARC policy of at least p=none, align their From domain, support easy unsubscribe and keep spam rates below 0.3%. Yahoo urges every sender to publish DMARC. |
| Outlook.com, Hotmail and Live | May 5, 2025 | Microsoft began rejecting mail from domains sending 5,000 or more messages a day that lack SPF, DKIM and DMARC. |
Most small organizations don’t send 5,000 messages a day from their own domain. Your newsletter platform, billing system or appointment reminder service might, and messages that fail authentication are increasingly likely to land in spam or be rejected outright.
Why enforcement matters even if you’re not a bulk sender
Without an enforced DMARC policy, anyone can send email that shows your exact domain in the From line. That makes it easier to target your clients, vendors and staff with fake invoices and payment change requests.
$3B+
in business email compromise losses reported to the FBI in 2025, according to the IC3 2025 Internet Crime Report.
DMARC won’t stop every business email compromise. It doesn’t block lookalike domains (yourfirm-billing.com instead of yourfirm.com), and it can’t help if a real mailbox is taken over. What it does is remove the easiest trick: forging your real address. For firms that handle client funds, tax data, donor records or patient information, it is an inexpensive control worth having in your written security program. Our post on business email compromise covers the payment rules that handle the rest.
How to set up DMARC and reach p=reject without breaking your email
Microsoft’s own guidance is a gradual approach, with p=reject as the goal for every domain:
- List everything that sends email as you: Microsoft 365 or Google Workspace, your accounting software, CRM, website forms, scanners, phone system voicemail-to-email and marketing tools.
- Fix SPF. Make sure there is one SPF record that includes every legitimate sender and stays within the lookup limit.
- Turn on DKIM in Microsoft 365 or Google Workspace, and in each third-party service that supports it.
- Publish DMARC at p=none with a reporting address (rua=) so you start receiving aggregate reports.
- Read the reports for a few weeks. They show every server sending mail as your domain. Fix any legitimate sender that fails.
- Move to p=quarantine, optionally using the pct= setting to apply it to a portion of failing mail first.
- Move to p=reject once reports show only legitimate mail is passing.
- Protect domains you don’t send from. Parked or unused domains should have a p=reject DMARC record and an SPF record that allows nothing.
DMARC reports are XML files that are hard to read raw, so a reporting service or your IT provider should turn them into a readable list of senders. On Microsoft 365 there is one more reason to fix every sender first: Microsoft notes that outbound mail from a domain with a quarantine or reject policy that fails DMARC at the destination is routed through its high-risk delivery pool, which can hurt deliverability.
Common DMARC mistakes
- 01Stopping at p=none. It satisfies the bulk-sender rules and stops no spoofing.
- 02Publishing more than one SPF record on a domain, which causes SPF to fail.
- 03Forgetting a sender, so invoices or appointment reminders start landing in spam after you enforce.
- 04Ignoring the reports after enforcement. New tools get added, and each one needs to pass.
- 05Assuming DMARC covers inbound mail. It protects your domain from being forged. Filtering what comes in is a separate job, covered in our six steps to business email security and our cybersecurity services.
A quick DNS lookup shows whether your domain can be spoofed today, and we’re glad to read the results with you. Book a 15-minute call and we’ll check your SPF, DKIM and DMARC records together.
To see how one attack played out and what changed afterward, read our business email compromise case study.
Frequently asked questions
What is DMARC?
DMARC is a DNS record that tells receiving mail systems what to do with a message that claims to come from your domain but doesn’t pass SPF or DKIM checks lined up with the From address. It also sends you reports showing every server sending mail as your domain. Set to p=reject, it stops criminals from sending email with your exact address in the From line.
What is a DMARC record?
A DMARC record is a single line of text published in your domain’s DNS. Its most important part is the policy: p=none only monitors, p=quarantine sends failing messages to junk, and p=reject tells receivers to refuse them. It can also include a reporting address (rua=) where mail providers send aggregate reports.
What is the difference between SPF, DKIM and DMARC?
SPF lists the servers and services allowed to send email for your domain. DKIM adds a digital signature that proves a message wasn’t altered and came from an authorized system. DMARC ties them together: it checks that the visible From domain lines up with SPF or DKIM, tells receivers what to do with failures and sends you reports.
How do you set up DMARC?
List every service that sends email as you, fix your SPF record and turn on DKIM for each sender. Publish a DMARC record at p=none with a reporting address and read the reports for a few weeks. Once every legitimate sender passes, move to p=quarantine and then p=reject. Many small businesses get there in a few weeks to a couple of months.
Why would an email fail DMARC?
An email fails DMARC when it doesn’t pass SPF or DKIM in a way that lines up with the domain in the From address. Real mail usually fails because a sending service, such as a billing system, CRM or scanner, was never added to SPF or set up with DKIM. Spoofed mail fails because the sender isn’t authorized at all.
Sources
Next step
Let us handle this for you.
Licensing through our Microsoft partnership, migrations, and the security settings Microsoft leaves off.
- 15 minutes
Tell us which question brought you here and how your office runs.
We’ll tell you how it applies to you and what we’d look at first.
If we’re not the right fit, we’ll say so.
