Email Spoofing
Forging an email's sender address to look like it came from someone else.
What it is
The practice of falsifying the visible 'From' address (and related headers) of an email so it appears to originate from a trusted domain or person. It exploits the fact that SMTP does not inherently verify the sender.
Why it matters
Spoofing underpins much phishing and fraud, which is exactly why authentication standards exist; confirming whether a message passed or failed those checks is a first step in email forensics.
In practice
A message whose 'From' shows a bank's domain but whose envelope sender and path point to an unrelated server.
What to look for
- SPF, DKIM or DMARC failures in the headers.
- From addresses that differ from the Return-Path.
- Your own domain sending mail you did not send.
Common mistake
Leaving DMARC at p=none forever. Monitoring is a start, but enforcement is what stops spoofing.
Use it in CyberKit
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Microsoft Defender for Office 365 Commercial
Filters phishing and malicious attachments in Microsoft 365 and lets you investigate messages.
-
Proofpoint Email Protection Commercial
A mail gateway that scores, rewrites and quarantines suspicious mail.
-
VirusTotal Commercial
A quick second opinion on a suspicious attachment or link.
Read next
- Sender Policy Framework: DNS record listing which servers may send mail for a domain.
- Domain-based Message Authentication, Reporting and Conformance: A policy tying SPF and DKIM to the visible From and reporting failures.
- Email Header Analysis: Reading an email's full headers to trace origin and authentication.