Run a free DMARC check to validate your domain's DMARC record, see which policy you enforce, and find out what to fix to stop spoofing.
A DMARC record checker validates your domain's email authentication policy by querying DNS records at _dmarc.yourdomain.com and verifying syntax, policy configuration, and alignment with SPF and DKIM standards.
Automatically detect and validate your DMARC policy settings including none, quarantine, or reject enforcement levels.
Verify DMARC record syntax including proper formatting, required parameters, and semicolon placement.
Policy-based email authentication and reporting
When an email arrives, the receiving server checks SPF and DKIM authentication. DMARC requires at least one of these to pass with proper domain alignment.
The receiving server queries your DMARC record at _dmarc.yourdomain.com to determine how to handle emails that fail authentication.
Based on your policy (none, quarantine, or reject), the server takes action and sends you aggregate reports about authentication results.
Essential for email security and brand protection
DMARC prevents attackers from sending phishing emails that appear to come from your domain. This protects your customers and brand reputation from fraudulent messages.
DMARC reports show you exactly who is sending emails on your behalf, which authentication methods are passing or failing, and potential unauthorized use of your domain.
Email providers strongly favor domains with DMARC configured. Proper DMARC implementation significantly improves inbox placement rates and sender reputation scores.
DMARC is becoming mandatory for many organizations and industries. Major email providers are increasingly requiring DMARC for bulk senders and will enforce stricter policies.
Each tag in your DMARC record, in plain English
Receivers deliver failing mail as usual and only send you reports. The right place to start, but it doesn't protect you from spoofing.
Mail that fails DMARC goes to spam or junk. A good middle step once your reports show your own senders pass.
Mail that fails DMARC is refused outright. The strongest protection against spoofing. BIMI logos need quarantine or reject.
rua is where aggregate reports go: daily XML summaries of who sent as your domain. ruf requests per-message failure reports, which many providers no longer send.
pct applies your policy to only a share of failing mail, for example pct=25 to quarantine a quarter of it while you roll out. It defaults to 100.
DMARC passes only when SPF or DKIM passes and its domain matches your From domain. r (relaxed) allows subdomains to match; s (strict) requires an exact match.
_dmarc.yourdomain.com with v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com.Since February 2024, Gmail and Yahoo require anyone who sends around 5,000 or more messages a day to their users to meet these rules:
Sources:Google email sender guidelinesandYahoo sender best practices. Last checked October 2026.
Learn more about DMARC and email authentication
Complete guide to implementing SPF, DKIM, and DMARC for optimal email security.
Step-by-step guide to configuring all email authentication protocols including BIMI.
Learn how to properly warm up a new domain to build sender reputation.
Check all authentication records for full email security
Complete suite of free email tools
Everything you need to know about DMARC authentication
Need help with email authentication and deliverability? Mailwarm helps you build sender reputation and ensure your emails reach the inbox. Want the full picture? Run a free email deliverability test.