How to Check and Fix Your DMARC Record
DMARC (Domain-based Message Authentication, Reporting, and Conformance) is the policy layer that makes SPF and DKIM useful. Without DMARC, a receiving server knows when authentication fails but has no instructions on what to do about it. DMARC provides those instructions and sends you reports about who is sending email from your domain.
Checking your DMARC record is the first step to understanding your domain's email authentication posture. Use our free DMARC lookup tool to see your current record instantly.
What a DMARC record looks like
A DMARC record is a DNS TXT record on the subdomain _dmarc.yourdomain.com. Here is a typical example:
v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com; pct=100
| Tag | Value | Meaning |
|---|---|---|
v | DMARC1 | Identifies this as a DMARC record (required) |
p | quarantine | Policy: quarantine messages that fail both SPF and DKIM |
rua | mailto:dmarc@yourdomain.com | Where to send aggregate reports |
pct | 100 | Apply the policy to 100% of failing messages |
How to check your DMARC record
Enter your domain in the Cleanbox DMARC Lookup tool. It retrieves and parses your DMARC record, showing each tag and its meaning. If no record is found, your domain has no DMARC policy — which means receivers make their own decisions about spoofed email from your domain.
You can also check manually via the command line:
dig TXT _dmarc.yourdomain.com +short
Understanding the three DMARC policies
| Policy | What happens to failing email | When to use |
|---|---|---|
p=none | Nothing — deliver normally, just report | Initial monitoring phase to discover all sending sources |
p=quarantine | Send to spam/junk folder | After confirming legitimate email passes SPF/DKIM |
p=reject | Reject entirely — do not deliver | Full protection after thorough testing |
The progression should be: none → quarantine → reject. Each step gives you more protection but also more risk of blocking legitimate email if your authentication is not fully configured. For more on the trade-offs, see why strict DMARC rejection is not always right.
Common DMARC problems and fixes
No DMARC record at all
This is the most common issue. Without a DMARC record, your domain has no spoofing protection and you receive no reports. The fix: add a monitoring record immediately:
v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com
This does not block anything yet. It starts collecting data about who sends email using your domain, so you can safely tighten the policy later.
Policy set to none indefinitely
Many domains set p=none during setup and never progress beyond it. A none policy provides reporting but zero protection — spoofed email from your domain is still delivered. If your reports show that all legitimate email passes authentication, upgrade to quarantine or reject.
Missing rua tag
Without an rua (reporting URI for aggregate reports) tag, you get no visibility into who is using your domain. Even with p=reject, you are flying blind. Always include an rua address.
SPF or DKIM not aligned
DMARC requires that at least one of SPF or DKIM both passes and aligns with the visible “From” domain. A common failure: SPF passes for your sending service's domain but not for yours, because the envelope sender (Return-Path) uses the service's domain, not yours.
Fix this by ensuring DKIM signing uses your domain (most email services let you configure a custom DKIM domain). For the full explanation, see DMARC alignment explained.
Subdomain policy missing
By default, subdomains inherit the parent domain's DMARC policy. If you want a different policy for subdomains (common when you use subdomains for marketing or transactional email), add the sp tag:
v=DMARC1; p=reject; sp=quarantine; rua=mailto:dmarc@yourdomain.com
DMARC and email forwarding
DMARC creates a known problem with email forwarding. When someone forwards email from your domain, the forwarding server's IP is not in your SPF record, so SPF fails. If the forwarding service does not preserve the DKIM signature, DKIM also fails. The result: your legitimate email gets rejected by the final recipient.
This is why technologies like SRS (Sender Rewriting Scheme) exist — they rewrite the envelope sender during forwarding to maintain SPF alignment. Cleanbox uses SRS for all forwarded email to prevent this breakage.
Setting up DMARC properly
- Check your current state — Use the DMARC lookup tool to see if you have a record and what it says
- Verify SPF — Use the SPF checker to confirm your SPF record is valid and lists all sending sources
- Verify DKIM — Use the DKIM checker to confirm your sending services sign with your domain
- Start with monitoring — Publish a
p=nonerecord withruaand collect reports for at least two weeks - Review reports — Check that all legitimate email passes. Fix any authentication gaps
- Tighten the policy — Move to
p=quarantine, thenp=rejectonce you are confident
For the full picture of how SPF, DKIM, and DMARC work together, see our complete email authentication guide.
Protect your inbound email too
DMARC protects your domain from being spoofed outbound. But what about the spam, phishing, and malware that arrives in your inbox? Cleanbox filters every incoming email through Rspamd, DNSBL reputation, ClamAV, and AI classification before it reaches you — the inbound counterpart to your outbound authentication.
Ready to take control of your inbox?
Start protecting your email with Cleanbox — free plan available, no credit card required.
Get started free