Shadow Inbox/blog
Subscribe
← back to indexblog / cold email / do-you-need-dmarc-for-cold-email
● Cold Email

Do You Need DMARC for Cold Email? What Google Says

Google lists DMARC under its 5,000-a-day rules and Microsoft says smaller senders benefit too. What a founder sending 30 emails a day should publish.

A
ArthurFounder, Shadow Inbox
publishedNov 17, 2026
read7 min
Do You Need DMARC for Cold Email? What Google Says

You registered a fresh domain for cold outreach, connected two mailboxes, and your sending tool shows green ticks next to SPF and DKIM. Then it asks about DMARC, links a forty-minute explainer, and you close the tab. You send thirty emails

You registered a fresh domain for cold outreach, connected two mailboxes, and your sending tool shows green ticks next to SPF and DKIM. Then it asks about DMARC, links a forty-minute explainer, and you close the tab. You send thirty emails a day and the rule says five thousand. Reasonable instinct. It is also half right, which is the dangerous amount.

Here is the short answer. No published rule we found makes DMARC mandatory for a founder sending thirty emails a day, but the two providers that matter name p=none as the bare minimum for bigger senders, and publishing it takes one DNS line. Do it before you need it, because the day your domain crosses a threshold is a bad day to learn what alignment means.

Google lists DMARC only under the 5,000-a-day rules

Google's email sender guidelines split into two lists. Everyone sending to personal Gmail accounts needs SPF or DKIM. DMARC shows up only in the list for senders above 5,000 messages a day, with the reassuring line that your "DMARC enforcement policy can be set to none". The same page still says Google recommends that you "always set up SPF, DKIM, and DMARC for your domains."

Read the two lists together and a small sender is not on the hook for DMARC. That is our reading. Neither Google page says it as a sentence, so do not quote us as saying Google exempts you.

5,000+messages a day to personal Gmail accounts is where Google's DMARC requirement starts
p=nonethe minimum DMARC policy Google and Microsoft both accept from large senders
48 hoursGoogle Workspace's advice: let SPF and DKIM run this long before you add DMARC

Microsoft says smaller senders benefit, and it enforces on the same line

Microsoft's announcement for Outlook.com covers "domains sending over 5,000 emails per day". It asks for SPF to pass, DKIM to pass, and DMARC "at least p=none and align with either SPF or DKIM (preferably both)." Failing mail gets the 550 5.7.515 rejection we walked through in our Outlook rejection post.

Microsoft's FAQ even asks the question you are asking. Do you still need this under 5,000 a day? The answer: "While enforcement first targets large senders, all senders benefit from these best practices." That sentence does not exempt you and does not threaten you. It tells you which way the wind blows.

Google counts the whole domain, and bulk status never expires

The 5,000 is not a daily budget you can watch. Google's sender guidelines FAQ defines a bulk sender as one who sends "close to 5,000 messages or more" to personal Gmail accounts in 24 hours, and it adds up mail from the same primary domain, including subdomains. Anyone who reaches that line once is "permanently considered" a bulk sender, and the status "doesn't have an expiration date."

So the domain that sent one big newsletter, or that shares a primary domain with a company that did, may already count. We covered the arithmetic in our post on a separate domain for cold email. The DMARC consequence is simple: if your cold mail comes from anywhere under that primary domain, check whether the domain publishes a record at all.

The FAQ's enforcement table lists a missing DMARC record as a reason a bulk sender loses "delivery support or mitigations", and says Gmail has been ramping up enforcement on non-compliant traffic since November 2025. It also says that when mail fails DMARC and the domain has no policy, the mail "might be rejected or sent to spam", while a domain that published a policy generally gets that policy applied. A record turns a guess into a documented path.

What p=none does and what it leaves alone

SPF says which servers may send for your domain. DKIM signs each message with a key that lives in your DNS. DMARC adds the rule that ties them to the address your prospect sees. Google puts it this way: "The authenticating domain must be the same domain that appears in the message From: header." Only one of SPF or DKIM has to align, and the FAQ says so plainly.

That explains the DNS chores every sending tool hands you. A tool that signs with a key for your own domain passes alignment. A tool that signs only with its own domain, and sends under yours, does not.

At p=none you ask receivers for no enforcement. Google's rollout page, linked from its setup guide, describes it as no enforcement for 100% of messages. What you get in return is reporting: Google says the rua tag is optional but that it recommends always including it, and failing mail shows up in a daily report sent to that address.

DMARC at p=none asks nobody to do anything. It also lets every inbox that receives your mail tell you what it saw.

The record, the order and the check

Google's DMARC setup guide is the one we would follow, in this order:

  1. Turn on SPF and DKIM for the domain first. Google says to allow 48 hours before you add DMARC, and warns that publishing it without them will probably cause delivery problems.
  2. Add a TXT record at _dmarc.yourdomain.com, with v=DMARC1 first and p=none second, plus a report address: v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com
  3. Send a test to a Gmail address and an Outlook.com address, open the headers, and look for spf=pass, dkim=pass and dmarc=pass, with the passing domain matching your From address.
  4. Read the daily reports for a week. Google says a week is usually enough for the reports to show every stream of mail you send.

Use a dedicated mailbox or a group for the rua address. Google warns the tag "can potentially result in a high volume of report emails" and recommends against your own address. Some DNS hosts add your domain name to the host field automatically, so check the record after you save it.

Stricter than none is for your main domain, not your cold one

Google's rollout guide goes from none to quarantine on a small slice of messages, 10% for a small organization, then up to 100%. It offers reject as the alternative and warns that rejected mail is "never delivered", so be sure everything that sends for you passes first.

This is our opinion, not a provider rule: enforce on the domain that carries your invoices and customer mail, because spoofing there hurts people who trust you. On a cold domain with two mailboxes and a clean record, none of the pages we read ask for more than p=none. Moving to quarantine there protects you from forgers more than it earns you inbox placement, and nobody publishes a test that says otherwise. If you ever want a brand logo in Gmail, that is a different story, because Google's setup guide says BIMI will not work with p=none.

Authentication is the floor, not the ceiling. If your trouble is a spam rate near 0.3% or a pile of bounces, read the bounce rate numbers and the sending limits before you touch your policy. And if you worry that Gmail flags AI-written mail, our answer from Google's own docs is that the checks are authentication, complaints and volume.

Public replies skip the DNS entirely

Shadow Inbox is our product, and it has nothing to do with your DNS records. What it does is watch Reddit and Hacker News for people who asked for what you sell, so your first contact can be a public reply to a question they wrote an hour ago. A reply in a thread has no SPF, no DKIM and no DMARC to fail.

Cold email still earns its place once the signal is there, and then your record decides whether the email arrives. Publish the line, read the reports, and spend the saved afternoon on the message.

● FAQ

Do I need DMARC to send cold email?
Google's published rules list DMARC only for senders above 5,000 messages a day to personal Gmail accounts, and Microsoft frames its rule around the same number. Neither page says a small sender is exempt in so many words. A p=none record costs one DNS line and is the minimum both providers name, so publish it before you need it.
Is p=none enough for cold email?
For meeting Google's and Microsoft's bulk sender rules, yes. Google says the enforcement policy can be set to none, and Microsoft asks for at least p=none aligned with SPF or DKIM. A stricter policy protects your domain from spoofing. It does not earn you extra inbox placement in any page we read.
What is DMARC alignment in plain words?
The domain in the visible From address has to match the domain that passed SPF or the domain that signed the DKIM key. Google says only one of the two needs to align. This is why your sending tool asks you to add its DKIM records to your own DNS.
Do I need DMARC if I send from a subdomain?
A subdomain with no record of its own inherits the policy of the parent domain, according to Google's setup guide. So if your main domain publishes DMARC, a cold sending subdomain is covered. Google also counts subdomains toward the same primary domain when it decides who is a bulk sender.
What email address should I use for DMARC reports?
A dedicated mailbox or a group, not your own inbox. Google warns that the rua tag can produce a high volume of report emails and suggests a dedicated mailbox, a group, or a third-party service built for DMARC reports.
— share
— keep reading

Three more from the log.