Skip to content
startupcybersecurity
Email securityDMARC

How to Set Up DMARC: A Step-by-Step Guide for Startups

Set up DMARC in under an hour without breaking your email: the exact DNS records to publish, how to read reports, and when to move from p=none to p=reject.

Jay Dabhi

By , CISM · Cybersecurity Analyst

Updated

3 min read

To set up DMARC, publish a TXT record at _dmarc.yourdomain.com with a monitoring policy (v=DMARC1; p=none; rua=mailto:you@yourdomain.com), read the reports for one to two weeks, make sure every service that sends your email passes SPF or DKIM, then tighten the policy to p=quarantine and finally p=reject. Most startups can finish in a few days of elapsed time and under an hour of actual work.

Why DMARC matters for startups

DMARC tells receiving mail servers what to do with email that claims to come from your domain but fails authentication. Without it, anyone can send an invoice, a password reset or a "wire this today" email that appears to come from your CEO.

It also shows up early in enterprise security reviews, because a reviewer can check it in seconds. Since 2024, Google and Yahoo have required a DMARC record from bulk senders, so missing DMARC can also hurt your own deliverability.

Before you start: SPF and DKIM

DMARC builds on two other checks:

  • SPF lists the servers allowed to send your email.
  • DKIM adds a cryptographic signature to each message.

DMARC passes when either SPF or DKIM passes and the domain it checked matches the domain in the visible From address (this is called alignment). Turn on DKIM in Google Workspace or Microsoft 365, and in every tool that sends email for you: your product's transactional email provider, CRM, support desk and marketing platform.

You can check your SPF record, including the 10-lookup limit, with our free SPF checker.

Step 1: publish a monitoring record

Add this TXT record in your DNS provider (Cloudflare, Route 53, Google Domains and so on):

Type Name Value
TXT _dmarc v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

p=none means "report, don't block". rua is where daily aggregate reports go.

If the reporting address is on a different domain (for example a shared security inbox), that domain must publish an authorization record, or mail providers will silently drop the reports:

yourdomain.com._report._dmarc.otherdomain.com  TXT  "v=DMARC1"

Step 2: read the reports

Within 24–48 hours you'll start receiving zipped XML files from Google, Microsoft, Yahoo and others. Each one lists the IP addresses that sent email as your domain and whether they passed SPF and DKIM.

The XML is hard to read by hand, so use a free DMARC report viewer. Look for two things:

  1. Legitimate services that fail. Fix these by adding them to SPF or turning on DKIM for your domain in that service.
  2. Sources you don't recognize. These are often spoofing attempts, which is exactly what enforcement will block.

Step 3: enforce

When legitimate sources consistently pass, tighten the policy:

v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com

After another week of clean reports:

v=DMARC1; p=reject; rua=mailto:dmarc@yourdomain.com

p=reject is the goal: spoofed email is refused before it reaches anyone's inbox.

Common mistakes

  • Two DMARC records. Receivers ignore DMARC entirely when there's more than one. Keep exactly one TXT record at _dmarc.
  • Forgetting subdomains. By default subdomains inherit your policy. If you set sp=none, attackers can spoof billing.yourdomain.com.
  • pct below 100. pct=10 applies your policy to only 10% of failing email. Leave it out or set it to 100 once you enforce.
  • Staying at p=none forever. Monitoring alone doesn't stop spoofing. It's a step, not the destination.

Check your work

Run your domain through our free DMARC checker. It reads your record, explains each tag and flags anything that weakens protection.

Frequently asked questions

How long should I stay at p=none?

Usually one to two weeks of reports is enough to find every legitimate service that sends email for you. Once all of them pass SPF or DKIM with alignment, move to p=quarantine, then p=reject.

Do I need DMARC if I don't send marketing email?

Yes. DMARC protects your domain from being spoofed by other people, which has nothing to do with how much email you send. A domain that sends no email at all should publish v=DMARC1; p=reject.

Will DMARC stop email from my own tools?

Only at quarantine or reject, and only for tools that aren't set up with SPF or DKIM for your domain. That's why you start at p=none and read the reports before enforcing.

More guides