PowerMTA.inEmail Infrastructure & Deliverability
LATESTGmail Sender RequirementsSMTP TLS ExplainedPTR & Reverse DNSDeliverability ChecklistAuthentication Troubleshooting

What Is DMARC?

Practical note: Technical information should be validated against your mail provider, DNS configuration and current standards before production changes.
Abhishek SharmaEditor & email infrastructure writerView author profile →
Last reviewed: 12 August 2026 Editorial and source check
Topic cluster · Email Authentication

What this guide covers

  • How SPF and DKIM feed DMARC
  • The difference between policy and alignment
  • How aggregate reports can guide rollout
  • A practical path from monitoring to enforcement
Editorial review: Reviewed on 12 August 2026 for clarity, internal consistency and alignment with the cited primary sources. Technical standards, vendor features and legal requirements can change; verify the current source before production or compliance decisions.
DMARC is the policy and alignment layer that connects domain identity with SPF and DKIM. This guide focuses on the decisions a domain owner actually has to make: alignment, policy, reporting and a safe path from monitoring toward enforcement.

The Simple Definition

DMARC (Domain-based Message Authentication, Reporting and Conformance) is a policy layer that sits on top of SPF and DKIM. It does two things: tells receiving mail servers what action to take when a message fails SPF or DKIM checks, and sends you reports showing exactly who is sending email using your domain — including anyone spoofing it.

Why DMARC Is Necessary on Top of SPF and DKIM

SPF and DKIM alone don't tell a receiving server what to actually do with mail that fails their checks — that decision is left entirely up to the receiving provider's own judgment. DMARC removes that ambiguity by letting you, the domain owner, explicitly set the policy.

The Three DMARC Policies

DMARC Policy Levels

p=noneMonitor only — failed mail is delivered normally, but you receive reports. The right starting point.
p=quarantineFailed mail is sent to spam/junk folders instead of the inbox
p=rejectFailed mail is rejected outright and never delivered — full enforcement

The recommended path is to start at p=none, review your reports for a few weeks to confirm all your legitimate mail sources pass, then move to p=quarantine and eventually p=reject once you're confident nothing legitimate will be blocked.

Why Enforcement Matters Beyond Deliverability

A domain sitting at p=none indefinitely gets the reporting benefit but none of the actual protection — anyone can still spoof your domain in phishing emails, since nothing is blocking failed mail. Moving to enforcement (quarantine or reject) is also a hard requirement before you can set up BIMI, which displays your brand logo in supporting inboxes.

Build your record Use our free DMARC Generator to build a correctly formatted record with the right policy and reporting settings for your domain.

Frequently Asked Questions

What DMARC policy should I start with?

Start with p=none to monitor without affecting delivery, review your DMARC reports for a few weeks, then move to p=quarantine and eventually p=reject once you've confirmed all legitimate mail sources pass.

Do I need both SPF and DKIM for DMARC to work?

You need at least one of them to align with your DMARC record, though having both properly configured gives more reliable protection and is the standard recommended setup.

Is DMARC required for using BIMI?

Yes. BIMI requires DMARC enforced at p=quarantine or p=reject — p=none is not sufficient for BIMI to work.

Quick Summary

Sources & references

Primary and authoritative references used when preparing or reviewing this article. Product features, policies and standards can change, so verify current requirements before making production changes.

  1. RFC 7489 — DMARC
  2. Gmail Email sender guidelines
A
Written by Abhishek
Founder & Editor, PowerMTA.in

Runs PowerMTA.in alongside his own email marketing and affiliate operations targeting Indian audiences — hands-on with bulk sending infrastructure, live campaigns, and content properties. Read more →