Sender Policy Framework
Also called SPF.
DNS record listing which servers may send mail for a domain.
What it is
An email-authentication standard that publishes, in DNS, the set of IP addresses authorized to send mail on behalf of a domain. Receiving servers check the envelope sender's source against that list.
Why it matters
SPF is a frontline defense against envelope spoofing and a key signal in header analysis, though it breaks on forwarding and only covers the envelope sender, which is why it is paired with DKIM and DMARC.
In practice
A receiving server rejecting mail because the sending IP is absent from the claimed domain's published SPF record.
What to look for
- spf=fail or softfail in Authentication-Results.
- SPF records over the 10 lookup limit.
- Records ending in +all, which allow anyone.
Common mistake
Thinking SPF protects the visible From address. It checks the envelope sender; DMARC ties them together.
Use it in CyberKit
- Email Header Analyzer
Walk the Received chain, and read the SPF, DKIM and DMARC verdicts.
- Phishing Case
A reported invoice email: pull the deciding values out of its raw headers, and say what they establish.
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
- DomainKeys Identified Mail: A cryptographic signature proving an email wasn't altered in transit.
- Domain-based Message Authentication, Reporting and Conformance: A policy tying SPF and DKIM to the visible From and reporting failures.
- Email Spoofing: Forging an email's sender address to look like it came from someone else.