Email security

What Is DMARC? How It Stops Email Spoofing (and How to Set It Up)

DMARC is the DNS record that tells inboxes what to do with email pretending to be you. Here is how it works with SPF and DKIM, and a safe path to p=reject.

Cysoro Security TeamPublished · 3 min read
EMAIL SECURITY DMARC

Key takeaways

  • DMARC is a TXT record at _dmarc.yourdomain.com.
  • It only protects you once the policy is quarantine or reject.
  • Reach p=reject in steps: none → quarantine → reject, reading reports along the way.

DMARC (Domain-based Message Authentication, Reporting and Conformance) is an email standard that tells receiving mail servers what to do when a message claims to come from your domain but fails authentication. It is published as a DNS TXT record, and when set to "quarantine" or "reject" it stops most spoofed email that uses your exact domain.

Why DMARC exists

Email was designed without proof of who sent a message. Anyone can put your domain in the From address of an email, much like anyone can write any return address on an envelope.

SPF and DKIM were created to add proof. But on their own, neither one checks the From address people actually see in their inbox. DMARC closes that gap.

It also gives you something no other standard does: daily reports from mailbox providers showing every server that sent email using your domain.

How DMARC works with SPF and DKIM

When a message arrives, the receiving server runs two checks and then applies your DMARC policy.

  • SPF checks whether the sending server's IP address is listed in your domain's SPF record.
  • DKIM checks a cryptographic signature added by the sending server, using a public key in your DNS.
  • DMARC passes if SPF or DKIM passes and the domain they checked matches the visible From domain. This match is called "alignment".
Email arrivesFrom: you@acme SPF checksender IP allowed? DKIM checksignature valid? DMARCpass + aligned? Deliver to inbox p=quarantine → spam p=reject → blocked passfail
How a receiving server applies your DMARC policy. Illustration by Cysoro.

Because DMARC needs only one of SPF or DKIM to pass with alignment, mail forwarded through other servers can still pass thanks to DKIM.

What a DMARC record looks like

_dmarc.example.com  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]"
TagMeaning
v=DMARC1Version. Required and must come first.
p=Policy for failing mail: none, quarantine or reject.
rua=Where daily aggregate reports are sent.
sp=Policy for subdomains (defaults to p).
pct=Percent of failing mail the policy applies to.
adkim= / aspf=Alignment mode: r (relaxed, default) or s (strict).

p=none vs quarantine vs reject

p=none is monitoring only. Receivers deliver failing mail as normal but send you reports. It protects nothing, but it is the right first step.

p=quarantine asks receivers to put failing mail in spam or junk. This is where real protection starts.

p=reject asks receivers to refuse failing mail outright. It is the strongest setting and the goal for most domains.

Common mistakeMany domains publish p=none and never move on. That gives you reports, but spoofed email still reaches inboxes.

How to set up DMARC step by step

  1. Fix SPF first. Make sure you have one SPF record that lists every service that sends as you, within 10 DNS lookups.
  2. Turn on DKIM in every service that sends email for you: your mailbox provider, newsletter tool, CRM and helpdesk.
  3. Publish p=none with a reporting address: v=DMARC1; p=none; rua=mailto:[email protected]
  4. Read the reports for 2–4 weeks. Find any legitimate sender that fails and fix its SPF or DKIM.
  5. Move to p=quarantine. If you are unsure, start with pct=25 and raise it.
  6. Move to p=reject once nothing legitimate fails.

You can check your current record at any time with the free DMARC checker.

Reading DMARC reports

Aggregate reports arrive as zipped XML files, usually once a day from each large mailbox provider. Each one lists sending IP addresses, how many messages they sent, and whether SPF, DKIM and DMARC passed.

The raw files are hard to read by hand. A DMARC report service, or even a spreadsheet import, helps you spot which senders still fail.

What DMARC does not stop

DMARC protects your exact domain. It cannot stop an attacker who registers a look-alike domain such as yourcompany-billing.com and sends from there.

It also cannot help if a real account on your domain is compromised, because that mail passes authentication. Those risks need brand monitoring, multi-factor authentication and staff training.

DMARC and bulk-sender rules

Since 2024, Google and Yahoo require domains that send more than 5,000 messages a day to their users to publish a DMARC record, alongside SPF and DKIM. Even p=none meets that minimum, but it does not protect your brand.

Frequently asked questions

Is DMARC required?

It is not legally required, but Google and Yahoo require it from bulk senders, and it is the only standard that stops spoofing of your visible From address.

Can DMARC break my email?

Only if you move to quarantine or reject before every legitimate sender passes SPF or DKIM with alignment. That is why you start at p=none and read reports.

How long does DMARC take to work?

A DNS change usually spreads within minutes to a few hours. Moving safely from p=none to p=reject usually takes 4 to 8 weeks.

Do I need DMARC on domains that do not send email?

Yes. Publish v=DMARC1; p=reject together with an SPF record of v=spf1 -all, so nobody can spoof the unused domain.

Written byCysoro Security Team

The people who build Cysoro's scanners and free security tools. We write practical guides on email authentication, website security and everyday safety, checked against current standards and vendor documentation.

How we write and fact-check →

Free tools for this topic

No account needed.

See where your domain stands

Free for up to 3 domains. No card, no installs.

Start free