ThisCalculator

Everyday

DMARC Failure: What It Means & How to Fix It

Updated · Standard formula, shown below

Average pace 5.00 min/km
Average speed
12.00 km/h
Result
Finish time
50 min
You entered
Distance
10 km
You entered

If you’re seeing “sending domain dmarc failure,” it means an email you sent failed DMARC authentication, which can cause your messages to be marked as spam or rejected. This guide explains what DMARC is, why failures happen, and how to fix them so your emails reach the inbox.

What Is DMARC?

DMARC (Domain-based Message Authentication, Reporting, and Conformance) is an email authentication protocol that helps prevent spoofing and phishing. It builds on SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) by telling receiving mail servers what to do if an email fails those checks—quarantine it, reject it, or deliver it anyway. DMARC also provides reports so domain owners can see who is sending email using their domain.

When you see a “DMARC failure,” it means the receiving server checked your email against your domain’s DMARC policy and found that it didn’t pass authentication. This often happens because SPF or DKIM failed, or because the email came from a subdomain or third-party service that isn’t aligned with your main domain.

How DMARC Works: SPF, DKIM, and Alignment

DMARC relies on two underlying authentication methods:

  • SPF checks that the sending server’s IP address is listed in your domain’s DNS records. If the email is sent from a server not listed, SPF fails.
  • DKIM uses a digital signature to verify that the email wasn’t tampered with and that it genuinely comes from your domain. The signature is validated against a public key in your DNS.

For DMARC to pass, at least one of these must pass and be aligned with the domain in the “From” address. Alignment means the domain used in SPF or DKIM must match (or be a subdomain of) the domain in the From header. If you send via a third-party service like a marketing platform, the service’s domain might be used for SPF/DKIM, causing misalignment and a DMARC failure.

Common Causes of DMARC Failure

Here are the most frequent reasons your emails might show a DMARC failure:

  • SPF misconfiguration: Your SPF record doesn’t include the sending server’s IP, or it has too many DNS lookups (the limit is 10).
  • DKIM signature missing or invalid: The email isn’t signed, or the public key doesn’t match the private key used by your sending service.
  • Alignment mismatch: The sending domain (e.g., mailer.example.com) is not the same as your From domain (e.g., example.com).
  • Third-party senders: Services like email marketing platforms or CRM tools often send from their own domains, which breaks alignment unless you configure custom DKIM/SPF.
  • Forwarding: When an email is forwarded, SPF often fails because the forwarding server’s IP isn’t in the original sender’s SPF record. DKIM may also be stripped.

How to Diagnose a DMARC Failure

To fix the issue, you need to identify which part is failing. Here’s a step-by-step approach:

  1. Check your DMARC reports (if you have a policy that sends them) to see which IPs and domains are failing.
  2. Use an online email authentication checker (like MXToolbox or Google’s Postmaster Tools) to analyze a sample email’s SPF, DKIM, and DMARC results.
  3. Look at the raw email headers. Most providers show “Authentication-Results” lines that detail SPF, DKIM, and DMARC status.
  4. Verify your DNS records: ensure your SPF record includes all sending IPs, and your DKIM key is correctly published.
  5. Test with a tool that simulates sending to a mailbox you control, then inspect the headers.

How to Fix DMARC Failure

Once you know the cause, the fix usually involves updating your DNS records or adjusting your sending setup. Here are the common solutions:

  • Update SPF record: Add the IP addresses or hostnames of all servers that send email for your domain. Keep the lookup count under 10.
  • Configure DKIM: Generate a DKIM key pair and publish the public key in your DNS. Then enable DKIM signing on your mail server or third-party service.
  • Align domains: If you use a subdomain for sending (e.g., mail.example.com), ensure your SPF and DKIM records use that subdomain, and that your DMARC policy is set for the parent domain. For third-party senders, you may need to set up a custom return-path or DKIM selector to align with your domain.
  • Use a subdomain for bulk email: Many organizations create a subdomain like “marketing.example.com” for promotional emails, with its own SPF and DKIM, so failures there don’t affect the main domain’s reputation.
  • Start with a permissive DMARC policy: Set p=none first to monitor, then move to quarantine, then reject once you’re confident all legit email passes.

What to Do If You Don’t Control the Sending Domain

If you’re receiving DMARC failure notifications for a domain you don’t own, it’s likely a spoofing attempt or a misconfigured third-party service. You can’t fix it directly, but you can:

  • Report the email as phishing/spam to your email provider.
  • Block the sending IP or domain in your mail filter.
  • If the domain is yours but you didn’t set up DMARC, you can add a DMARC record to stop spoofing.

Frequently Asked Questions

Why do my emails show DMARC failure even though SPF and DKIM pass?

This usually happens due to alignment failure. For example, if your From address is user@example.com but your SPF is set up for senders@sub.example.com, the SPF passes but isn’t aligned with the From domain. DMARC requires alignment, so it fails.

What is the difference between DMARC failure and DMARC rejection?

DMARC failure means the email didn’t pass authentication. DMARC rejection is what happens when the receiving server applies your DMARC policy (p=reject) to a failed email—it bounces the message. If your policy is p=none, failed emails are still delivered, but you’ll see failures in reports.

Can DMARC failure cause my emails to go to spam?

Yes. Many email providers treat DMARC failures as a sign of spam or spoofing. Even if your policy is p=none, the receiving server’s own spam filters may quarantine the message based on the authentication results.

How long does it take for DMARC changes to take effect?

DNS changes typically propagate within a few hours but can take up to 48 hours. However, receiving servers may cache DNS records, so it can take longer for all providers to see the updated DMARC policy.

Do I need DMARC if I have SPF and DKIM?

Yes. SPF and DKIM alone don’t tell receivers what to do with failed emails. DMARC gives you control and provides visibility. Without DMARC, spammers can still use your domain because there’s no policy to reject them.

Related

Formula used
in t | Finish time | min | 50 | 0
in d | Distance | km | 10 | 0
out pace | Average pace | min/km | t / d | 2
out speed | Average speed | km/h | d / (t / 60) | 2

Each line is one input (in, sel, list) or one result (out: label, unit, formula, decimals). How the calculators work

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.