DMARC Checker

Check DMARC record for any domain. Validate DMARC policy mode, reporting URIs, SPF/DKIM alignment settings, and subdomain handling configuration.

Run a check to see results

APIPOST /api/v1/email/dmarc
4.7(13 votes)
10
checks performed
Try also: SPF Checker
Run Check

Key Features

100% Free

No registration required, unlimited checks

Instant Results

Real-time analysis with detailed output

REST API Access

Integrate into your workflow via API

Accurate Data

Live queries to authoritative sources

What is DMARC Checker?

The DMARC checker retrieves and validates the Domain-based Message Authentication, Reporting and Conformance (DMARC) record for any domain. DMARC is the policy layer that ties SPF and DKIM together — it tells receiving mail servers exactly what to do when an email fails authentication: accept it (none), send it to spam (quarantine), or reject it outright (reject). The tool parses the DMARC TXT record published at _dmarc.yourdomain.com and validates all policy components: the enforcement mode (p=none/quarantine/reject), SPF and DKIM alignment settings (strict vs relaxed), percentage of messages the policy applies to (pct), subdomain policy (sp), and reporting URIs for aggregate (rua) and forensic (ruf) reports.

This free DMARC record checker is critical for domain owners implementing email authentication, email administrators progressing from monitoring (p=none) to enforcement (p=reject), deliverability specialists diagnosing why emails fail DMARC checks, and security teams protecting their domain from email spoofing and phishing attacks. DMARC adoption has become effectively mandatory since Google and Yahoo began requiring it for bulk senders in 2024.

How to Use

  1. 1Enter the domain name to check its DMARC record (e.g., yourdomain.com)
  2. 2Click 'Run Check' to retrieve the TXT record at _dmarc.yourdomain.com
  3. 3Review the policy mode: none (monitor only), quarantine (send to spam), or reject (block unauthenticated email)
  4. 4Check alignment settings: relaxed (default, subdomain matches count) or strict (exact domain match required)
  5. 5Verify reporting URIs (rua/ruf) are configured to receive DMARC aggregate and forensic reports
  6. 6Review subdomain policy (sp) if your domain uses subdomains for sending email

Who Uses This

System Administrators

Monitor and troubleshoot infrastructure

Developers

Debug network issues and integrate via API

SEO Specialists

Verify domain configuration and performance

Security Analysts

Audit and assess network security

Frequently Asked Questions

What is a DMARC record and why is it important?
A DMARC record is a DNS TXT record published at _dmarc.yourdomain.com that defines your domain's email authentication policy. It tells receiving mail servers how to handle emails that fail SPF and DKIM checks — accept them, quarantine them (spam folder), or reject them entirely. DMARC is important because without it, anyone can send emails pretending to be from your domain (spoofing), and receiving servers have no policy to follow when authentication fails. DMARC also enables reporting, so you receive data about who is sending email using your domain and whether it passes authentication. Since 2024, Google and Yahoo require DMARC for domains sending over 5,000 emails per day.
How do I set up DMARC for my domain?
Add a TXT record at _dmarc.yourdomain.com with your DMARC policy. Start with monitoring mode: v=DMARC1; p=none; rua=mailto:dmarc-reports at yourdomain.com — this tells servers to send you reports but not enforce any policy. Monitor the reports for 2-4 weeks to identify all legitimate sending sources. Once you've confirmed all legitimate email passes SPF and DKIM, tighten to v=DMARC1; p=quarantine (send failures to spam), and eventually v=DMARC1; p=reject (block failures completely). Never jump straight to reject without monitoring first, as you may block legitimate email from services you forgot to authorize.
What is the difference between DMARC none, quarantine, and reject?
These are the three DMARC enforcement levels: p=none means take no action on failing emails but send reports to the domain owner — use this for monitoring during initial deployment. p=quarantine means send failing emails to the recipient's spam/junk folder — this is the intermediate enforcement step. p=reject means block failing emails entirely, preventing delivery — this is the strongest protection against spoofing and the recommended end-state. The standard progression is: deploy with p=none, monitor reports for 2-4 weeks, fix any legitimate sources failing authentication, move to p=quarantine, monitor for issues, then advance to p=reject.
What is DMARC alignment and why does it matter?
DMARC alignment checks whether the domain in the From header matches the domains used in SPF and DKIM authentication. There are two modes: relaxed alignment (default) allows subdomains to match the organizational domain — so SPF passing for mail.example.com satisfies DMARC for example.com. Strict alignment requires an exact domain match. Alignment matters because without it, an attacker could set up SPF for their own domain but spoof the From header to show your domain. DMARC alignment closes this gap by ensuring the authenticated domain matches what the recipient sees.
What are DMARC aggregate reports and how do I read them?
DMARC aggregate reports (rua) are XML files sent daily by receiving mail servers to the email address specified in your DMARC record. They contain data about every email received claiming to be from your domain: the sending IP, SPF and DKIM results, DMARC alignment outcome, and the count of messages. These reports help you discover all sources of email using your domain (legitimate and unauthorized), identify authentication failures, and track your progress toward enforcement. The raw XML is hard to read — use a DMARC report analyzer service to visualize the data in a dashboard.