DMARC record

DMARC Checker

Check your domain's DMARC record and policy. DMARC ties SPF and DKIM together, tells receivers what to do with mail that fails, and is now required by Gmail and Yahoo for bulk senders.

One record is only part of it

MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, DNSSEC and BIMI all decide together whether your mail is trusted. The full report reads every one of them and hands you the fix.

Run the full domain check

About these results

This tool reads your domain's public DMARC (TXT) record at _dmarc.yourdomain at the moment of the check. Results reflect current public DNS and can be affected by caching and propagation (up to 24-48 hours). Guidance is general and not a substitute for your provider's official instructions. We don't store the domains you check.

Reference

How DMARC works

What the record is for, how to read the result, and what to do about each problem.

What is DMARC?

DMARC builds on SPF and DKIM. It tells receivers what to do with mail that claims to be from your domain but fails authentication, and sends you reports showing who is sending as you.

Policies

p=none - monitor only.
p=quarantine - failing mail to spam.
p=reject - failing mail blocked (strongest).
rua= - where aggregate reports are sent.

Safe rollout

Publish v=DMARC1; p=none; rua=mailto:you@yourdomain.
Review reports; confirm senders pass SPF or DKIM aligned.
Move to p=quarantine, then p=reject.

Questions

Frequently asked

What does p=none do in DMARC?

p=none is monitoring only: it collects reports but does not stop failing mail. Review the reports, then move to p=quarantine and finally p=reject.

Quarantine vs reject?

quarantine sends failing mail to spam; reject blocks it outright. reject gives the strongest protection against spoofing of your domain.

Do I need DMARC?

Yes, especially for bulk email. Since 2024 Gmail and Yahoo require a DMARC record for bulk senders, and DMARC is what actually stops others spoofing your domain.

Related checks