Skip to content
DMARC Pulse

Email errors

DMARC fail: what it means and how to fix it

DMARC fail means no SPF or DKIM pass aligned with the From domain. See what receivers do with the message, why it happens and how to fix it.

What this means

DMARC fail means a message had no SPF or DKIM pass for a domain aligned with its visible From address. SPF lists the servers allowed to send for a domain. DKIM adds a signature tied to a domain.

Mail servers record the result in the Authentication-Results header. Microsoft documents this example, shown here with other domains. SPF and DKIM pass, and DMARC still fails:

Authentication-Results: spf=pass (sender IP is 198.51.100.10)
  smtp.mailfrom=bounces.example.net; dkim=pass (signature was verified)
  header.d=example.net; dmarc=fail action=oreject
  header.from=example.com;compauth=fail reason=000

The wording varies by mail server. dmarc=none means the domain has no DMARC record.

What happens after a DMARC failure

The p= tag in the domain's DMARC record states a preference. The receiver makes the final decision.

  • p=none: no preference. RFC 9989 says it must not change how the receiver already handles mail. Other filters can still send the message to spam.
  • p=quarantine: the owner considers the mail suspicious. Receivers may move it to spam or quarantine.
  • p=reject: the owner considers the use of its domain invalid. Receivers may refuse it.

RFC 9989 shows 550 5.7.1 Email rejected per DMARC policy for example.com as an example. The same code can mean a different refusal on another server, so read the text after it.

DNS authentication: DMARC fail

DNS Authentication: DMARC Fail is the label the University of Sussex shows under Policies Triggered when Mimecast holds a message there. If you received that notice, tell the sender, because the domain is theirs to fix. Ask your IT team if you need the message released.

Why it happens

Only an aligned pass counts. Aligned means the domains match or, in the default relaxed mode, share an organizational domain (usually the registered domain, such as example.com for news.example.com). That is why DMARC failed on a message showing spf=pass and dkim=pass: each check passed for a domain that does not align with From.

  • A sending platform is not set up for your domain. SPF and DKIM can pass, but only for its own domains. Amazon SES defaults to a MAIL FROM under amazonses.com.
  • Forwarding or a mailing list. The forwarder's IP address is outside your SPF record. DKIM generally survives plain forwarding, but a list's footer or subject tag breaks it.
  • Strict alignment. With aspf=s or adkim=s, bounces.example.com no longer aligns with example.com.
  • Spoofing. Someone else used your domain, and dmarc=fail is the correct result.

How to fix it

  1. Paste a failing message's full headers into the email header analyzer.
  2. Compare header.from (the visible From), smtp.mailfrom (the envelope sender that SPF checks) and header.d (the DKIM signing domain; some receivers show header.i). If header.from is not yours, only its owner can fix this.
  3. Find the source's IP address in your aggregate reports. They need a rua= tag in your _dmarc record, so add one if it is missing. Do not authorize a source you do not recognize.
  4. If a check failed for a source you recognize, correct its SPF record or DKIM key. Caution: edit the existing SPF record. A second record, or more than 10 terms that trigger DNS queries, makes SPF return permerror.
  5. In each real platform, publish the DKIM records it gives you, then turn on signing with your domain.
  6. If the platform allows it, set its MAIL FROM (bounce) domain to a subdomain of yours that handles no other mail, and publish the records it lists. Caution: some platforms require an MX record there, so never reuse a name that receives mail. An include: alone does not align mail whose MAIL FROM stays on the platform's domain.
  7. If strict alignment is the cause, change aspf=s or adkim=s to r in your DMARC record (TXT at _dmarc.example.com).
  8. Do not tighten the policy to clear the failure. Caution: p=quarantine or p=reject repairs nothing and can send real mail to spam or get it refused.

Confirm the fix

  1. Once the DNS change is visible, send a new message through the same platform to another mailbox you control.
  2. Paste its headers into the analyzer. You want dmarc=pass. Arrival alone proves nothing.
  3. Watch your aggregate reports for several days. Under <policy_evaluated>, <dkim> or <spf> should read pass for that source.

Some forwarded mail and spoofing will keep failing. That alone does not point to a setup error.

Check it now

Trace delivery and read SPF/DKIM/DMARC results

Analyzed in your session only. Headers are never stored.

Frequently asked questions

Was my email blocked if it shows dmarc=fail and p=none?
The DMARC policy did not block it. RFC 9989 says p=none must not change how the receiver already handles mail. The message can still land in spam through other filters, and Google notes that the cause may then be something other than the DMARC record. Gmail, Yahoo and Outlook accept p=none from bulk senders, yet each also requires alignment or a DMARC pass.
Why does DMARC fail when SPF and DKIM both pass?
DMARC needs a pass for a domain that aligns with the From address. If SPF passes for a MAIL FROM on another domain and DKIM signs with another domain in d=, both checks pass and DMARC still fails.
What does DNS Authentication: DMARC Fail mean?
It means a message failed DMARC and a mail filter held it. The University of Sussex, which filters mail with Mimecast, shows this label under Policies Triggered in the notice for a held message. Its guidance is to contact the sender so they can fix their DMARC setup and to ask the IT Service Desk to release the message, because there only an administrator can do it.
Should I change p=none to p=reject to fix it?
No. A stricter policy repairs nothing and asks receivers to act on the same failures, so real mail may reach spam or be refused. Fix your real senders first. RFC 9989 says domains whose users might post to mailing lists should not publish p=reject. If such a domain still wants it, the RFC says to first spend at least a month at p=none and an equally long period at p=quarantine, compare the results in aggregate reports, and restrict or warn users about posting to lists.
Does dmarc=fail mean someone is spoofing my domain?
Sometimes. It can also be your own sending platform, a forwarded message or a mailing list. A forwarder sends from its own IP address, so SPF most likely fails unless it rewrites MAIL FROM. DKIM signatures generally stay valid through plain forwarding, so an aligned signature usually keeps the pass. Check the sending IP in your aggregate reports, which RFC 9989 asks receivers to send at least every 24 hours. Fix the sources you recognize and leave the others failing.
What is the difference between dmarc=fail, dmarc=none and a DMARC error?
dmarc=fail means the domain has a DMARC record and the message had no aligned pass. dmarc=none means the domain has no DMARC record. dmarc=temperror and dmarc=permerror mean an error stopped the evaluation. When the DNS queries for the check do not complete, RFC 9989 says the message cannot be considered to pass or fail.

Sources consulted

RFC 8601 §2.7.1 DKIM
checked 2026-11-08

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.