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
Email 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 "MAIL FROM" of a message or the domain given on the SMTP HELO/EHLO commands. This document describes version 1 of the Sender Policy Framework (SPF) protocol, whereby ADministrative Management Domains (ADMDs) can explicitly authorize the hosts that are allowed to use their domain names, and a receiving host can check such authorization. This document obsoletes RFC 4408.
Document record
- Document ID
- RFC7208
- Published
- April 2014
- Authors
- S. Kitterman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 64
- Also known as
- —
- Obsoletes:
- RFC 4408
Topics
Referenced by
3 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 7073A Reputation Response Set for Email IdentifiersCurrent
November 2013
- RFC 7072A Reputation Query ProtocolCurrent
November 2013
- RFC 7071A Media Type for Reputation InterchangeCurrent
November 2013
- RFC 7070An Architecture for Reputation ReportingCurrent
November 2013
- RFC 6686Resolution of the Sender Policy Framework (SPF) and Sender ID ExperimentsCurrent
July 2012
- RFC 6651Extensions to DomainKeys Identified Mail (DKIM) for Failure ReportingCurrent
June 2012
- RFC 7001Message Header Field for Indicating Message Authentication StatusObsoleted
September 2013
- RFC 7601Message Header Field for Indicating Message Authentication StatusObsoleted
August 2015
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?