How to set up DMARC step by step (from p=none to p=reject)
A safe, step-by-step DMARC rollout: publish p=none, read the reports, fix your senders, then move to quarantine and reject.
Updated
DMARC tells receiving mail servers what to do with email that claims to come from your domain but fails authentication — and it sends you reports about who is sending as you. Since February 2024, Gmail and Yahoo require a DMARC record for bulk senders, and Microsoft Outlook followed in 2025. Even small senders benefit: without DMARC, spoofing your domain is much easier.
How DMARC passes
An email passes DMARC if SPF or DKIM passes and is aligned with the domain in the visible From address. Aligned means the domains match (in relaxed mode, subdomains count as a match). That's why a newsletter tool must sign with DKIM for your domain — passing SPF for the tool's own domain isn't enough.
Step 1: List everything that sends email as you
- Your mailbox provider (Google Workspace, Microsoft 365, …).
- Newsletter and marketing tools, CRM, helpdesk, invoicing software, your shop or website (contact forms, order emails).
- Make sure each one has DKIM set up for your domain and, if needed, is in your SPF record.
Step 2: Publish a monitoring record (p=none)
Add a TXT record at _dmarc.yourdomain.com:
v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com; fo=1;p=none changes nothing for delivery — it only turns on reporting. Use a mailbox you can read, or a DMARC report service, because the daily XML reports aren't meant for humans.
Step 3: Read the reports for 2–4 weeks
Look for legitimate services that fail SPF/DKIM alignment and fix them (usually by setting up DKIM in that service). Unknown senders failing everything are often spoofing attempts — exactly what DMARC will block later.
Step 4: Enforce — quarantine, then reject
v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@yourdomain.com;With p=quarantine, failing email goes to spam. If nothing legitimate breaks after a few weeks, move to the strongest policy:
v=DMARC1; p=reject; rua=mailto:dmarc-reports@yourdomain.com;Common mistakes
- Publishing two DMARC records — receivers then ignore DMARC completely.
- Jumping straight to
p=rejectbefore all services sign with DKIM — invoices or password resets may disappear. - Forgetting the
ruaaddress, so you never learn what fails. - Leaving
p=noneforever: it gives visibility but no protection.
Check your page in seconds
Free, no signup: see what's wrong and get the exact DNS records to fix it.
Check your domain with the free SPF, DKIM & DMARC checker →