What does a DMARC checker test?
A DMARC checker looks up the TXT record at _dmarc.yourdomain.com and tests it against RFC 7489, the DMARC standard. DMARC (Domain-based Message Authentication, Reporting and Conformance) is a DNS record that tells receiving servers what to do with mail that fails authentication, and where to send reports about it.
This tool reports four things about the record:
| Test | Passes when | Why it matters |
|---|---|---|
| Record exists | One TXT record at _dmarc starts with v=DMARC1 | With no record, a forged message using your domain is judged with no instructions from you |
| Policy | p= is quarantine or reject | p=none only monitors and blocks nothing |
| Reporting | An rua= address is set | Without reports you cannot see who is sending as you |
| Coverage | pct= is 100 or absent | A lower value applies the policy to only part of failing mail |
How do you read a DMARC record?
A DMARC record is a list of tags separated by semicolons. Only v and p are required. Here is a record at full enforcement:
v=DMARC1; p=reject; rua=mailto:dmarc@example.com; adkim=r; aspf=r
| Tag | Meaning | Values |
|---|---|---|
v | Version. Must come first | DMARC1 |
p | Policy for mail that fails | none, quarantine, reject |
sp | Policy for subdomains | Same as p. Inherits p when absent |
rua | Where daily aggregate reports go | A mailto: address |
pct | Share of failing mail the policy applies to | 1 to 100. Default 100 |
adkim, aspf | How strictly DKIM and SPF domains must match the From domain | r relaxed (default), s strict |
What is the difference between p=none, quarantine and reject?
The p tag is the DMARC policy, and it has three levels. Each one tells a receiving server how to treat a message that fails DMARC.
| Policy | What the receiver does | Use it when |
|---|---|---|
p=none | Delivers as normal and sends you reports | You are starting and need to see who sends as your domain |
p=quarantine | Sends failing mail to spam | Reports show your real senders passing |
p=reject | Refuses failing mail outright | Every legitimate sender has passed for several weeks |
A message passes DMARC when SPF or DKIM passes and the domain that passed matches the visible From domain. That match is called alignment. It is the part most senders miss: a marketing platform can pass SPF and DKIM for its own domain while your From domain still fails DMARC.
Is a DMARC record required?
Yes, for bulk senders. As of November 15, 2026, Google's email sender guidelines require anyone sending 5,000 or more messages a day to Gmail accounts to publish a DMARC record, and Yahoo's sender best practices set the same rule. A policy of p=none meets the minimum.
Smaller senders are not exempt in practice. A domain with no DMARC record can be forged by anyone, and mailbox providers treat unauthenticated mail with more suspicion every year.
How do you move from p=none to p=reject without losing mail?
Move to p=reject in stages, using the aggregate reports to confirm each step. Jumping straight to reject is how companies block their own invoices and password resets.
- Publish
p=nonewith anruaaddress and collect reports for at least 2 weeks. - List every source in the reports. Fix SPF and DKIM alignment for each one you recognize.
- Move to
p=quarantine; pct=25, then raisepctto 100 over 2 to 4 weeks. - Move to
p=rejectonce no legitimate source has failed for 2 weeks. - Keep reading the reports. A new tool added next year will fail until it is aligned.
Check the two records DMARC depends on with the SPF record checker and the DKIM checker. We do this staged rollout as a fixed-scope job, described under DMARC setup and enforcement. To check every record at once, run the full email deliverability test.