Legitimate mail vs spoofing in reports
A failing row in a DMARC report doesn't automatically mean someone is spoofing you. Failing mail comes from three places: your own services that aren't set up for alignment yet, indirect mail such as forwarders and mailing lists, and unauthorized use of your domain. You tell them apart by matching each source to services you know you run and by reading its authentication pattern. Even then, the patterns are clues, not proof. And some impersonation never shows up in your reports at all.
Failing mail streams may be a combination of illegitimate uses of the domain, such as spoofing or other attempted abuse, and legitimate uses that fail because their authenticated identifiers are unaligned or missing entirely.
Three buckets, and what each looks like
These signals are working heuristics. Confirm them with the people who own the systems.
| Bucket | What it tends to look like in reports | What to do |
|---|---|---|
| Your own mail, misconfigured (a vendor, app, or device) | An IP or network you can tie to a service. Raw SPF or DKIM passes but the aligned result fails, because the vendor uses its own bounce domain or signs with its own d=. Or there's no DKIM and the IP isn't in SPF. Volume follows your business activity |
Fix alignment before enforcement: custom DKIM at the vendor, an aligned bounce domain, or SPF where appropriate (Third-party mail fails alignment, How to add a third-party sender without breaking DMARC) |
| Indirect mail (forwarders, aliases, mailing lists) | The IP belongs to a forwarding host or list server. SPF fails, because that IP isn't in your SPF. DKIM may still pass and align if the message wasn't changed. Receivers may record a reason of mailing_list, trusted_forwarder, or local_policy |
Usually nothing to change in your SPF. Make sure your mail is DKIM-signed with an aligned domain (Forwarded mail fails DMARC, DKIM and mailing lists or forwarders). ARC and SRS are measures on the forwarder's and receiver's side (Email forwarding, SRS, and ARC) |
| Unauthorized use (exact-domain spoofing) | IPs and networks you can't tie to any service or owner. No aligned DKIM, often no DKIM at all, or DKIM from unrelated domains. Volume unrelated to your own sending | Don't authorize it. Once your legitimate sources align, an enforcement policy asks receivers to quarantine or reject it (A safe rollout: p=none to quarantine to reject) |
The difference between raw and aligned results, which drives the first column, is explained field by field in A field-by-field walk-through of a DMARC aggregate report. Why the envelope domain and the From domain differ is in Envelope From vs Header From.
Spotting spoofing in DMARC reports
Spoofing is the bucket you reach by elimination. Before you file a source there, check whether it's yours:
- DKIM domain and selector. Does it match a vendor you've contracted, or a key you published?
- SPF (
envelope_from) domain. Is it a known vendor bounce domain? - Owner confirmation. Ask marketing, sales ops, finance, and IT. Check SaaS subscriptions and your DNS change history.
- Pattern over time. A legitimate stream recurs with your business cycle. One-off bursts from unrelated networks are more suspicious.
If it's still unclaimed after that, the inventory method in How to inventory sending sources and the troubleshooting steps in Reports show sources we do not recognize cover what to do next.
Why the signals can mislead
- You see the last hop.
source_ipis the IP that connected to the receiver. Forwarded mail shows the forwarder, not you. - Receivers disagree. Different paths, timing, and local policy can give different results for the same source on the same day.
- Reports can be forged. Report data itself can be forged, for example to influence your decisions. Trust sources that appear consistently across many reporters more than a single odd report.
- A pass isn't always yours. Overly permissive SPF can make unauthorized mail pass DMARC. If your SPF authorizes broad shared infrastructure, someone else on that infrastructure may pass as you. Keep SPF tight and prefer DKIM.
What DMARC reports can't show you
Some impersonation never reaches your reports, so don't go looking for it there:
- Lookalike domains and display-name tricks. DMARC does not address the use of visually similar domain names or abuse of the human-readable display name in the From header. Mail from
examp1e.exampleis reported, if at all, to whoever ownsexamp1e.example. - A compromised mailbox. An attacker using one of your real accounts sends authenticated, aligned mail. It passes DMARC and looks legitimate in reports. That's an account-security incident, not a DMARC failure.
- Inbound spoofing inside your own mail platform. How your tenant treats mail it receives is a platform configuration topic, separate from your reports.
After enforcement
Once you're at quarantine or reject, reports keep showing unauthorized attempts, now with a disposition of quarantine or reject. That's expected. It shows those receivers applied your policy request. It doesn't prove every receiver did, because receivers make the final decision. What actually happens to failing mail is in What happens to failing mail under each policy, and why staying at p=none leaves this mail unhandled is in Why staying at p=none is a problem.
Mistakes worth avoiding
- Adding an unknown IP to SPF to "fix" a failure. You may be authorizing a spoofer.
- Treating forwarders and mailing lists as attacks and trying to fix them in your SPF.
- Ignoring low-volume legitimate failures, such as a scanner or a web form. They'll start failing outright at enforcement.
- Investigating a spoofing complaint from a screenshot. Get the full message headers.
- Assuming a customer's "scam invoice" came from your domain. It may be a lookalike.
- Copying shortcut rules. Microsoft's report-reading table says "High count from unknown IP = potential spoofing" and, for unknown IPs where everything fails, "No action needed. Your DMARC policy is protecting recipients." That only holds at enforcement, and only after you've ruled out your own unconfigured senders. At
p=none, nothing is being blocked.
Free DMARC account
Turn raw DMARC reports into a readable dashboard
Point your rua address to our platform and read the results by sender and source instead of opening XML files.
- Results grouped by sending source
- SPF, DKIM and alignment results per sender
- The original XML reports are still there to download
FAQ
Does a failing source in my report mean I'm being spoofed?
Not necessarily. It could be your own misconfigured service or a forwarder. Check the DKIM domain, SPF domain, and owners first.
Someone is sending emails from my email address. Will DMARC reports show it?
If they're using your exact domain in the From address and the receiver sends reports, yes, as a source you can't account for. If they're using a lookalike domain, a display name, or one of your real accounts, no.
Will DMARC show me lookalike domains impersonating us?
No. DMARC covers your exact From domain only.
A customer got a fake invoice from "us". Is DMARC broken?
Get the full headers. The From domain may be a lookalike, the display name may be the only thing that's "you", or a real account may be compromised. DMARC doesn't address any of those.
Can spoofed mail pass DMARC?
It can if your SPF authorizes broad shared infrastructure the attacker can also use. Keep SPF tight and rely on aligned DKIM.