Free DMARC Record Lookup & Checker
| Domain | Type | Primary NS | Responsible Person | Serial | Refresh | Retry | Expire | Minimum | TTL |
|---|
| Name Server | IP Address | TTL |
|---|
| Domain | Type | TTL | Record Value |
|---|
| Trace Result |
|---|
| Domain | Type | Record | Status |
|---|
| Domain | Type | Record | Status |
|---|
Check live DMARC DNS records, TTL values, and trace the full root-to-authoritative resolution path.
DMARC (Domain-based Message Authentication, Reporting & Conformance) Overview
What is a DMARC record?
A DMARC record defines policies for email authentication, helping to prevent email spoofing and phishing attacks.
Why do you need a DMARC record?
DMARC records ensure that emails from your domain are properly authenticated, enhancing email security and trustworthiness.
DMARC record structure
A DMARC record includes the domain name, TTL, record type (TXT), and the DMARC policy. Example: _dmarc.example.com. 3600 IN TXT "v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.com"
How to create a DMARC record?
DMARC lives in a TXT record at the special host _dmarc.yourdomain.com. Start with v=DMARC1; p=none; rua=mailto:you@yourdomain.com to collect reports without affecting delivery, then tighten the policy to quarantine and finally reject once your SPF and DKIM alignment checks out.
FAQs
DMARC Troubleshooting & Common Fixes
Legitimate emails bounce or go to spam after setting p=quarantine or p=reject
When you use third-party platforms (such as Mailchimp, SendGrid, Shopify, or Zendesk), emails pass SPF under the vendor's return-path domain (e.g. sendgrid.net). However, DMARC requires “Alignment”: the domain in the user-visible From: header must exactly match the authenticated SPF or DKIM domain. If neither aligns, DMARC fails and the receiver rejects or spams the email.
d=yourdomain.com), providing valid DKIM alignment even when SPF aligns with the vendor's envelope. Never jump directly to p=reject; start with p=none to monitor reports first.
DMARC lookup says “No DMARC record found” even after adding it
DMARC is not published at the apex domain like SPF. By specification (RFC 7489), DMARC must be a TXT record created at the specific host prefix _dmarc (for example, _dmarc.example.com).
_dmarc (with an underscore). If you accidentally named the host @ or dmarc without the underscore, receivers will not find your policy.
Not receiving DMARC daily aggregate XML reports (rua)
If your DMARC record specifies a reporting email on a different domain (e.g. your policy is on domain-a.com, but reports go to reports@domain-b.com), the receiving domain must explicitly grant permission to receive those reports.
domain-b.com) must publish a verification TXT record at domain-a.com._report._dmarc.domain-b.com with the value v=DMARC1. Without this External Report Verification record, mail providers drop the reports to prevent email spam.
