Free DMARC Record Checker
Validate your DMARC policy, check alignment settings, verify reporting configuration, and detect duplicate records or missing authorization.
Check Your DMARC Record
Enter your domain to analyze your DMARC configuration and get actionable insights.
What is a DMARC Record?
A DMARC (Domain-based Message Authentication, Reporting & Conformance) record is a DNS entry that instructs receiving mail servers on how to handle emails that don't pass SPF or DKIM authentication checks. Think of it as a digital bouncer — ensuring only legitimate emails make it to your recipients' inboxes.
Without a DMARC record, anyone could impersonate your domain and send malicious emails. DMARC ties together SPF and DKIM into a unified policy, giving you control over what happens when authentication fails and providing visibility through aggregate and forensic reports.
Components of a DMARC Record
Version
Always v=DMARC1
Identifies this as a DMARC record.
Policy (p=)
none | quarantine | reject
How to handle emails that fail authentication.
Subdomain Policy (sp=)
Separate policy for subdomains
Optionally apply different rules to subdomains.
Aggregate Reports (rua=)
mailto:reports@example.com
Where to send summary authentication reports.
Forensic Reports (ruf=)
mailto:failures@example.com
Where to send detailed failure reports.
Alignment (adkim/aspf)
s (strict) | r (relaxed)
How strictly DKIM/SPF domains must match the From header.
Example DMARC record:
v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.com; ruf=mailto:dmarc-failures@example.com; adkim=s; aspf=s; Creating Your DMARC Record
Ensure SPF and DKIM are configured
DMARC builds on SPF and DKIM. Before creating a DMARC record, verify that both are properly set up for your domain. Use our free SPF checker to validate your SPF record.
Choose a policy
Start with p=none to monitor email traffic without affecting delivery. Once you're confident, move to quarantine or reject for full enforcement.
Define reporting addresses
Set up aggregate (rua) and forensic (ruf) report destinations to gain visibility into your email authentication landscape.
Specify alignment and publish
Choose strict or relaxed alignment for SPF and DKIM. Then add the record as a TXT entry at _dmarc.yourdomain.com in your DNS.
Verify and monitor
Use a DMARC testing tool to confirm your record is published correctly. Regularly review reports and adjust your policy as you gain confidence in your authentication setup.
Why Use a DMARC Generator?
Eliminate Syntax Errors
Generators ensure proper formatting, avoiding the misconfigurations that can silently break email authentication.
Save Time
Implementation time is reduced by up to 50% compared to manually crafting DMARC records from scratch.
Customization
Tailor policies for subdomains, set reporting preferences, and choose alignment modes to fit your organization's needs.
Reduce Phishing by up to 99%
Enforcing a reject policy can virtually eliminate domain impersonation in phishing attacks.
DMARC needs SPF — and SPF needs AutoSPF
DMARC alignment requires a passing SPF check. AutoSPF keeps your SPF record optimized and within the 10-lookup limit automatically.
What Our Customers Say
"AutoSPF Flattens SPF Records Seamlessly & Keeps Changes Logged - I am quite pleased with the product"
It does what it promises to do, and does it very well. I appreciate that it keeps a log of changes made, which prevents many mistakes. A client's SPF record would have way too many lookups, but AutoSPF makes that problem go away. The length of the SPF record is typically not the issue; it's the amount of lookups in the record that are. AutoSPF "flattens" the record, automatically expanding the defined lookups to IP addresses or ranges. And it auto-updates the record when the un-flattened lookups change.
Peter J.
President · Small-Business (50 or fewer emp.)
"Helped us go beyond capacity"
AutoSPF did exactly as described, it helped us get past our 10 lookup limit. Afterwards, we hit another limit regarding overall capacity and when contacted, they quickly provided us with a new solution to eliminate capacity issues entirely going forward, so now we can add as many SPF records as needed. They also provided us with a personalized support video explaining their new method in its entirety using our instance as the example.
Verified User
Financial Services · Mid-Market (51-1000 emp.)