Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 64
- Abstract
- 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.
- Publication Date
- 2014-04-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC7208- Link
- https://doi.org/10.17487/RFC7208
- Author(s)
- Scott Kitterman
- Keyword(s)
- Spoofing, SPF, Authentication
Latest version of IETF RFC 7208
Document Versions — IETF RFC 7208
-
▶ IETF RFC 7208 (2014-04-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- INCITS.X3.4.1968 — 1 EXTERNAL
- IETF RFC 1035 [Active, Amended*]
- IETF RFC 1123 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 3463 [Active*]
- IETF RFC 3864 [Active*]
- IETF RFC 3986 [Active, Amended*]
- IETF RFC 4291 [Active*]
- IETF RFC 5234 [Active, Amended*]
- IETF RFC 5321 [Active*]
- IETF RFC 5322 [Active, Amended*]
- IETF RFC 5598 [Active*]
- IETF RFC 5890 [Active*]
- RFC7001 — RFC7001 EXTERNAL
Bibliographic Reference(s)
- Levine, J., Crocker, D., Silberman, S., and T. Finch, "Bounce Address Tag Validation (BATV)", Work in Progress, May 2008. EXTERNAL
- Green, D., "Domain-Authorized SMTP Mail", June 2002, < http://www.mhonarc.org/archive/html/ietf-asrg/2003-03/ msg01525.html >. EXTERNAL
- Fecyk, G., "Designated Mailers Protocol" , Work in Progress, May 2004. EXTERNAL
- Vixie, P., "Repudiating MAIL FROM", 2002, < http://marc .info/?l=namedroppers&m=102298170127004&w=4>. EXTERNAL
- Danisch, H., "The RMX DNS RR and method for lightweight SMTP sender authorization", Work in Progress, May 2004. EXTERNAL
- IETF RFC 1034 [Active*]
- IETF RFC 1983 [Active*]
- IETF RFC 2308 [Active*]
- IETF RFC 2671 [Superseded*]
- IETF RFC 2782 [Active*]
- IETF RFC 3464 [Active*]
- IETF RFC 3696 [Active*]
- IETF RFC 3833 [Active*]
- RFC3834 — RFC3834 EXTERNAL
- IETF RFC 4033 [Active*]
- IETF RFC 4408 [Superseded*]
- IETF RFC 4632 [Active*]
- IETF RFC 4880 [Superseded*]
- IETF RFC 4954 [Active*]
- RFC5507 — RFC5507 EXTERNAL
- IETF RFC 5751 [Superseded*]
- RFC5782 — RFC5782 EXTERNAL
- IETF RFC 6409 [Active*]
- RFC6647 — RFC6647 EXTERNAL
- IETF RFC 6648 [Active*]
- IETF RFC 6652 [Active*]
- RFC6686 — RFC6686 EXTERNAL
- IETF RFC 6891 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7208.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1. Available at https://doi.org/10.17487/RFC7208
Snippet:
IETF RFC 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1. Available at https://doi.org/10.17487/RFC7208
HTML (ISO 690 compliant)
Preview:
IETF RFC 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1. Available at https://doi.org/10.17487/RFC7208
Snippet:
<span class="citation"><cite>IETF RFC 7208</cite>, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1. Available at <a href="https://doi.org/10.17487/RFC7208" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7208</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1
doi: 10.17487/RFC7208
url: https://doi.org/10.17487/RFC7208
doi: 10.17487/RFC7208
url: https://doi.org/10.17487/RFC7208
Snippet:
<li> <cite id="bib-rfc7208">IETF RFC 7208</cite>, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1 <span class="doi">10.17487/RFC7208</span> </li>
Referenced By
- IETF RFC 7372 [Active*]
- IETF RFC 8553 [Active*]
- IETF RFC 8616 [Active*]