RFC 4408: Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7208.
Current version: RFC 7208 — Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1
In plain English — editorial summary, not part of the RFC
E-mail on the Internet can be forged in a number of ways. In particular, existing protocols place no restriction on what a sending host can use as the reverse-path of a message or the domain given on the SMTP HELO/EHLO commands. This document describes version 1 of the ender Policy Framework (SPF) protocol, whereby a domain may explicitly authorize the hosts that are allowed to use its domain name, and a receiving host may check such authorization. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC4408
- Published
- April 2006
- Authors
- M. Wong; W. Schlitt
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- —
- Pages
- 48
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4406Sender ID: Authenticating E-MailCurrent
April 2006
- RFC 4405SMTP Service Extension for Indicating the Responsible Submitter of an E-Mail MessageCurrent
April 2006
- RFC 4750OSPF Version 2 Management Information BaseCurrent
December 2006
- RFC 4871DomainKeys Identified Mail (DKIM) SignaturesObsoleted
May 2007
- RFC 3906Calculating Interior Gateway Protocol (IGP) Routes Over Traffic Engineering TunnelsCurrent
October 2004
- RFC 5452Measures for Making DNS More Resilient against Forged AnswersCurrent
January 2009
- RFC 6008Authentication-Results Registration for Differentiating among Cryptographic ResultsCurrent
September 2010
- RFC 6577Authentication-Results Registration Update for Sender Policy Framework (SPF) ResultsObsoleted
March 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?