Skip to content
  • There are no suggestions because the search field is empty.

Do you need DMARC for cold email?

Yes. If you send cold email from your own domain, publish SPF, DKIM and DMARC before the first message goes out. Gmail, Yahoo and Outlook.com require DMARC from anyone sending in volume. Even below those thresholds, a domain with no DMARC record is easier to spoof, and providers sometimes reject or junk its mail. But DMARC only proves the mail really comes from you. It doesn't make mail people didn't ask for land in the inbox.

Outbound teams often do things in the wrong order: buy a sending tool, connect a mailbox, start sending, then find out about authentication when mail bounces or lands in spam. This article covers what to set up first and where authentication stops helping.

Short answer: publish DMARC before you send

  • Bulk-sender rules. Gmail and Yahoo require bulk senders to publish a DMARC record, at least p=none, that passes with alignment. Outlook.com requires high-volume senders to its consumer mailboxes to pass SPF and DKIM and publish a passing DMARC record, and can reject or junk mail that doesn't. Details are in Google and Yahoo sender requirements and Microsoft and Outlook authentication rules.
  • Below those thresholds. Mailbox providers sometimes reject or junk mail from domains with no DMARC record. A record costs nothing to publish and reduces that risk.
  • Microsoft 365 recipients. When a domain has no authentication records, or only weaker ones such as SPF ending in ~all or a DMARC policy of p=none, Microsoft 365 can give the message a failing composite authentication result. That's a weaker starting point for mail to any business on Microsoft 365.
  • Alignment is what counts. DMARC passes only when SPF or DKIM passes for a domain aligned with the visible From address. A sending tool that authenticates with its own domain doesn't help your From domain. Identifier alignment for SPF and DKIM explains alignment.

What to set up before the first outbound message

  1. Send from your own domain. A free mailbox address has no domain you control, so you can't publish SPF, DKIM or DMARC for it.
  2. SPF. Add the sending tool to your SPF record only if it uses your domain as the return path (envelope sender). Keep one SPF record per domain, and add the tool's include: to the existing record rather than publishing a second one. Watch the 10-lookup limit. See How to write an SPF record, Multiple SPF records (why that is invalid) and The 10-lookup limit and SPF permerror.
  3. DKIM. Have the sending tool sign with your domain (often called custom DKIM in the tool's settings). If it signs with its own domain, DKIM passes but doesn't align. SPF include vs DKIM from the vendor compares the SPF include and vendor DKIM routes, and How to add a third-party sender without breaking DMARC covers adding any third-party sender safely.
  4. DMARC. Start at p=none with a reporting address, so you can see every source sending as your domain before you enforce anything. For example:

_dmarc.example.com TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"

How to publish the record step by step is on our DMARC setup page. 5. Check alignment in your reports. Once aggregate reports arrive, confirm the sending tool's mail passes aligned SPF or DKIM before you rely on it. How to inventory sending sources covers building the inventory and What visual DMARC analysis should show you what a visual view should show you. 6. Unsubscribe. Add one-click unsubscribe and a visible opt-out, and honor opt-outs within two days.

The right order: SPF, DKIM, DMARC, then BIMI explains why this sequence matters.

What authentication can't fix for cold email deliverability

Passing authentication gets your mail identified and accepted. Where it lands then depends on recipients. Authentication vs inbox placement explains the difference between "accepted" and "in the inbox".

  • Bad lead data. Invalid addresses bounce. Old addresses that have been abandoned can later be reused as spam traps. Lead data that's out of date can hurt your cold email deliverability even when every record is perfect.
  • Role-based addresses. Addresses such as info@, sales@ or support@ often reach several people at once, none of whom asked for your message, so they tend to draw complaints. In cold outreach, write to a named person with a real reason to hear from you.
  • Complaint rate. Keep it below 0.3% at Gmail and Yahoo, and ideally under 0.1% at Gmail. What is a spam complaint rate? explains how it's measured.
  • Volume. Increase it gradually. No provider publishes a safe daily number for cold email; How many emails can you send per day? explains the limits that do exist.

If you want to improve cold email deliverability, these are the levers: who you write to, how relevant the message is, how easy it is to opt out, and how fast you grow. Authentication is the floor under all of them.

Consent and the law

Many countries have anti-spam and privacy laws that cover unsolicited commercial email. The rules differ by country, and often by whether the recipient is a business or a consumer. Check the rules for every country you send to, and get legal advice for your situation. Whatever the rules, identify yourself truthfully as the sender and include an opt-out that works.

Move to enforcement to protect your sales domain

p=none meets the minimum for bulk-sender rules, but it doesn't stop anyone else sending as your domain. Once your reports show every legitimate source passing, move toward p=quarantine and then p=reject. The staged rollout is in A safe rollout: p=none to quarantine to reject, and the risks of staying at p=none are in Why staying at p=none is a problem.

BIMI comes only after DMARC enforcement and only affects how a logo is displayed. It doesn't improve inbox placement for cold email or anything else; see Why BIMI is not a deliverability shortcut.

Common mistakes

  • Sending outreach from a free mailbox address.
  • Leaving the sending tool on its own DKIM domain, so DKIM passes but doesn't align with your From address.
  • Publishing a second SPF record for the new tool instead of editing the existing one.
  • Publishing p=reject on day one, before reports show what's sending as the domain.
  • Buying lists or scraping addresses.
  • Treating "authentication passed" as "the campaign is fine".

If mail is already going to spam, start with Why are my emails going to spam.

Free DMARC account

Not sure which sender is failing?

Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.

  • Every sending source in one dashboard
  • SPF, DKIM and alignment results per sender
  • No XML files to read

Create a free DMARC accountTalk to an expert

FAQ

Do I need DMARC if I only send 50 cold emails a day?

Yes. It's free to publish, it reduces a common rejection risk, and it lets you see who else is sending as your domain.

Is p=none enough?

It meets the minimum for bulk-sender rules, as long as your mail passes with alignment. It doesn't protect the domain from spoofing, so plan to move to enforcement once your reports are clean.

Will DMARC stop my cold emails going to spam?

No. It proves the mail is from you. Whether recipients want it decides where it lands.

Can I use my sending tool's domain instead of mine?

You can send that way, but DMARC for your From domain won't pass unless the tool signs with your domain or uses your domain as the return path.

Is cold email legal?

It depends on the country and on who you're writing to. Check the rules where you send and get legal advice. In every case, identify yourself and give recipients a working way to opt out.