Email DMARC Record Generator
Build a DMARC TXT record to publish for your domain in seconds. Protect your brand from spoofing and improve deliverability.
Configure Your DMARC Policy
Start with "none", then tighten as you verify.
Where DMARC reports are sent.
Start at 10-25% while monitoring.
Your DMARC TXT Record
Why DMARC Matters
DMARC tells receiving mail servers what to do with emails that fail SPF and DKIM checks. Without a published DMARC record, spammers can impersonate your domain and your legitimate email can be delivered to spam.
Google and Yahoo require senders of bulk email to publish DMARC with at least a "none" policy to maintain inbox placement. Publishing a policy also gives you visibility through aggregate reports into who is sending from your domain.
Not sure how SPF, DKIM and DMARC fit together? See our email authentication guide and the DMARC glossary term.
How to Roll Out DMARC Safely
The safest approach is staged. Publish with p=none and pct=100 first, monitor your aggregate reports for 2-4 weeks, fix any SPF or DKIM failures, then move to quarantine at pct=25 and increase gradually. Only move to reject once you are confident all legitimate senders pass authentication.
Common Mistakes
The most common errors are publishing a reject policy before third-party senders (marketing platforms, transactional providers) are authenticated, using a non-existent report email, or failing to align the domain in SPF and DKIM. Check your authentication health before tightening your policy.