RFC 7208: Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1

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…

Read RFC 7208 on the RFC Editor

Outgoing relationships (2 related RFCs)

Obsoletes — RFC 4408: Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1
Informative reference — RFC 6648: Deprecating the "X-" Prefix and Similar Constructs in Application Protocols

Incoming relationships (13 related RFCs)

Updated by — RFC 7372: Email Authentication Status Codes
Updated by, Informatively referenced by — RFC 8553: DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names
Updated by — RFC 8616: Email Authentication for Internationalized Mail
Normatively referenced by — RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC)
Normatively referenced by — RFC 8460: SMTP TLS Reporting
Normatively referenced by — RFC 7960: Interoperability Issues between Domain-based Message Authentication, Reporting, and Conformance (DMARC) and Indirect Email Flows
Normatively referenced by — RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC)
Informatively referenced by — RFC 8805: A Format for Self-Published IP Geolocation Feeds
Informatively referenced by — RFC 7505: A "Null MX" No Service Resource Record for Domains That Accept No Mail
Informatively referenced by — RFC 7601: Message Header Field for Indicating Message Authentication Status
Informatively referenced by — RFC 9170: Long-Term Viability of Protocol Extension Mechanisms
Informatively referenced by — RFC 8904: DNS Whitelist (DNSWL) Email Authentication Method Extension
Informatively referenced by — RFC 9671: Sieve Email Filtering: Extension for Processing Calendar Attachments