Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1
RFC 7208
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['spoofing', 'spf', 'anti-forgery', 'authentication']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "S. Kitterman": changed name from "Scott Kitterman" to "S. Kitterman", cleared country (was "United States of America") |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2020-01-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'Email on the Internet can be forged in a number of ways. In particular, existing protocols … Received changes through RFC Editor sync (changed abstract to '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.') |
|
2015-10-14
|
(System) | Notify list changed from spfbis-chairs@ietf.org, draft-ietf-spfbis-4408bis@ietf.org to (None) |
|
2014-04-25
|
(System) | RFC published |