05 Nov 20265 minutes read
How to Investigate a Fake Email and Block the Next One

Fake email overview:
- Until a domain reaches p=reject, a fake email that uses it can still reach recipients.
- To investigate a suspicious email, read the Authentication-Results header.
- A fake email gets through when DMARC is set to p=none, SPF ends in
+all, or a subdomain has a weak policy. - To block fake email, build a complete sender inventory, then move SPF to
-alland DMARC to p=reject.
Employees can spot a suspicious email in seconds, but authentication results sit in the message headers, which mail clients don’t show by default. That’s where a fake email succeeds.
When DMARC sits at p=none, nothing tells receiving servers to block or quarantine messages that fail authentication. A convincing fake email can still be delivered, with no warning to the recipient.
This playbook is for CISOs, IT administrators, and SOC analysts. It covers a triage process for a reported suspicious email and the fixes for the weaknesses that let it through.
Run your domains through Sendmarc’s DMARC record checker to see whether their SPF, DKIM, and DMARC records leave them open to fake email.
If you're at risk of impersonation, one of our experts will be in touch to assist.
Why Awareness Training Alone Won’t Stop a Fake Email
Awareness training teaches employees to look for typos, unusual sender names, and urgent language. That covers a narrow class of attack. A fake email that uses your exact domain, or a convincing lookalike, can look flawless.
Any server can put your domain in the “From” address. SPF, DKIM, and DMARC let receivers verify that claim, but only a DMARC policy of p=quarantine or p=reject asks them to act when a message fails authentication.
Until a domain reaches p=reject, a fake email that uses it can still reach recipients. In finance, that can mean a redirected wire transfer. In healthcare, it can mean a request for patient records. In telecoms, it can mean an altered provisioning workflow. Each reported suspicious email then becomes a manual investigation for an already stretched security team.
How to Check a Fake Email Against SPF, DKIM, and DMARC
Open the Authentication-Results header, which lists results for SPF, DKIM, and DMARC, such as pass or fail.
DMARC passes only when SPF or DKIM passes, and the authenticated domain aligns with the domain in the “From” header. A suspicious email can show spf=pass for a third-party domain and dmarc=fail, because that domain doesn’t match the “From” header. This is the most common pattern in a fake email that gets past user detection. Individual checks pass, alignment fails, and the policy never required action.
Next, check the policy of the domain in the “From” header with the Sendmarc DMARC record checker. A record such as v=DMARC1; p=none; rua=mailto:[email protected] means the domain owner collects data but requests no action. A record with p=reject asks receivers to reject messages that fail DMARC.
IT Triage Steps for a Suspicious Email
- Read the Authentication-Results header and note the DMARC result.
- If DMARC failed, determine whether SPF or DKIM passed or failed outright.
- Look up the DMARC policy of the “From” domain with the Sendmarc DMARC record checker.
- If the “From” domain belongs to another organization, report the message to them.
- If the “From” domain is yours, compare the sending IP against your SPF record, and its
includes. - If your own domain isn’t at p=reject, treat the delivery as a policy failure and begin remediation.
Common Causes of a Fake Email Reaching the Inbox
- p=none left in place: Monitoring is a diagnostic phase, not a security control. Many companies stay there because they lack confidence in their sender inventory.
- SPF ending in
+all: This tells receivers to accept email from any server. A fake email sent from anywhere can then pass SPF. - Inconsistent subdomain policy: Subdomains inherit the parent domain’s policy unless they publish their own record, or the parent domain's record includes an
sp=tag. A subdomain with its own p=none record, or ansp=nonetag, stays open to a fake email even when the parent is at p=reject.
How to Stop a Fake Email from Reaching the Inbox
- Build a complete sender inventory. Capture every legitimate source before changing policy, including marketing automation, HR systems, transactional email services, and CRM tools.
- Move to enforcement in stages. Progress from p=none to p=quarantine to p=reject, reviewing reports at each stage so critical communications keep flowing.
- Tighten the SPF policy in stages. End the record in
~all(softfail) while you confirm the sender inventory, then move to-all(fail) once every legitimate sender is listed. - Confirm subdomain coverage. Verify that each active and inactive subdomain inherits an enforcement policy or has its own.
How Sendmarc Can Help Stop Fake Email
Each step above depends on an accurate list of every sender authorized to use your domain. Keeping that list current across multiple domains, business units, and third-party tools takes time that stretched security and IT teams often don’t have.
The Sendmarc Platform helps in three ways:
- Visibility: DMARC Management identifies legitimate and unauthorized senders, including shadow IT, and surfaces SPF, DKIM, and DMARC misconfigurations before they become incidents.
- Enforcement without added workload: Sendmarc guarantees p=reject, with hands-on implementation support through each stage and ongoing monitoring and optimization afterward.
- Extended protection: Lookalike Domain Defense detects domains designed to impersonate your brand before they’re used in attacks. Breach Detection identifies compromised employee credentials.
Explore how Sendmarc’s platform helps your team build a complete sender inventory and provides hands-on support through each enforcement stage, so a fake email using your domain is blocked before it reaches an inbox.


