DMARC Record Checker: Add a Safe Policy for Domain Email
Learn how to check for a DMARC record, where it belongs in DNS, and why even a basic p=none policy is better than no DMARC record.
DMARC gives receiving mail servers instructions for messages that fail SPF and DKIM alignment. It is published as a TXT record at _dmarc.yourdomain.com.
A missing DMARC record does not usually stop inbound email, but it can weaken domain protection and make authentication harder to understand.
Where DMARC belongs
DMARC is not placed on the root domain. It belongs on the _dmarc subdomain, such as _dmarc.example.com.
A simple starter record can use p=none while you observe results. Stricter policies such as quarantine or reject should wait until you know legitimate mail is passing authentication.
Why p=none can still be useful
A p=none policy tells receivers that the domain has DMARC and can request reports without asking receivers to quarantine or reject messages yet.
For small businesses, this is often the lowest-risk first step before tightening the policy later.
DMARC depends on SPF and DKIM
DMARC works best when SPF or DKIM passes and aligns with the visible From domain. A DMARC checker should not treat the record as isolated from the rest of the email setup.
If SPF is duplicated or DKIM is missing, fix those authentication records before moving DMARC to a strict policy.
Quick checklist
- Check TXT records at _dmarc.yourdomain.com.
- Confirm the record starts with v=DMARC1.
- Use p=none as a safe starting policy if you are unsure.
- Add reporting addresses only when someone will review the reports.
- Tighten policy after legitimate mail is passing SPF or DKIM alignment.