DMARC Record Checker:
Validate and Fix Your Record
A missing or misconfigured DMARC record leaves a domain open to phishing and impersonation, even if the organization believes protection is in place. Many teams publish a record once during setup and never check it again, so drift goes unnoticed until an audit, a delivery problem, or an incident forces the question.
Sendmarc’s DMARC record checker reads the live record published in a domain’s DNS and flags exactly what’s wrong, so a team can fix it before it becomes a bigger problem.
Enter your domain below and select Test record to view the configuration and any issues found.
What Is a DMARC Record Checker?
A DMARC record checker is an online diagnostic tool that reads the DMARC record published in a domain’s DNS and checks whether it’s present, correctly formatted, and configured with the intended policy.
IT and email administrators use it to confirm a record is published correctly after a DNS change. Security and compliance teams use it to verify enforcement status ahead of an audit or before making the case for stricter policy. Marketing and communications teams use it to rule out authentication as the cause of a delivery failure.
_dmarc.yourdomain.com · TXT
v=DMARC1; p=quarantine; rua=mailto:[email protected];
Why DMARC Record Checks Matter
Receiving servers can’t block unauthenticated email sent as the domain unless a DMARC record tells them to. Regular checks confirm the record is still published, still correctly formatted, and still set to the policy the organization intends.
Records also drift silently. A routine DNS migration, a new sending platform, or a bulk edit can overwrite or reset the record without anyone noticing, until reports stop arriving or a mailbox provider starts rejecting messages.
Common reasons to run a check:
Catch configuration
errors
Catch Spam placement
risk early
Confirm alignment with
provider requirements
What Sendmarc’s DMARC Record Checker
Shows You
Presence
Confirms whether a DMARC record exists at _dmarc.yourdomain.com and is correctly published.
TXT · v=DMARC1; p=quarantine; rua=mailto:[email protected];
Policy configuration
Identifies whether the record is set to p=none, p=quarantine, or p=reject.
Reporting addresses
Surfaces the aggregate and forensic addresses configured to receive DMARC reports.
rua=mailto:[email protected]
ruf=mailto:[email protected]
How to Use Sendmarc’s DMARC Record Checker
- Enter the domain. Type the domain name into the field.
- Review the record. The tool fetches the DMARC TXT record from the DNS and displays it in a readable format.
- Check the results. Confirm whether a record is present, review the policy setting, and verify the reporting addresses.
- Fix and recheck. If the checker flags an issue, update the DNS record and run the check again to confirm the fix.
Run a check any time DNS settings change, or on a regular schedule, rather than waiting for a delivery problem or a failed audit to surface a misconfiguration.
Check your recordDMARC Record Checker FAQs
What is a DMARC record?
A DMARC record is a DNS TXT record that defines a domain’s DMARC policy. It tells receiving email servers how to handle unauthenticated messages and includes the policy setting (p=none, p=quarantine, or p=reject) and the reporting addresses.
What does a valid DMARC record look like?
A valid DMARC record includes required tags and correct syntax, for example:
| Host | Type | Value |
|---|---|---|
_dmarc.yourdomain.com | TXT | v=DMARC1; p=quarantine; rua=mailto:[email protected]; |
What happens if my DMARC record is misconfigured?
A misconfigured DMARC record may get ignored by receiving email servers, leaving the domain exposed to phishing and impersonation. It can also cause legitimate email to land in Spam or get rejected.
How do I fix a DMARC misconfiguration?
Fixing a DMARC misconfiguration starts with using a DMARC record checker tool to identify the syntax or policy error, updating the DNS record, and rerunning the checker to confirm the fix.
Can a domain have more than one DMARC record?
No, a domain should have only one DMARC record. Multiple DMARC records cause processing errors and can result in the policy being ignored entirely.
Is DMARC still necessary if SPF and DKIM are already configured?
Yes, DMARC is still necessary even with SPF and DKIM in place. DMARC builds on both by adding policy enforcement and reporting, which SPF and DKIM don’t provide on their own.
Does a DMARC record checker stop phishing emails from being sent?
No. A DMARC record checker validates configuration. Only a policy set to p=reject blocks unauthenticated email from reaching inboxes.
Why use Sendmarc’s DMARC record checker specifically?
Sendmarc’s DMARC record checker reads the live record directly from the DNS and checks presence, syntax, policy, and reporting addresses in one pass.