Visual RFC.
ALL RFCs / RFC 7208
Read the RFC ↗
RFC 7208 / MECHANISM GUIDE

Publish and find the record

02

A DNS TXT record beginning with v=spf1 carries the policy.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 3.1 ↗
RFC 7208 · § 3.1EXAMPLE
3 / 3
Publish and find the recordA DNS TXT record beginning with v=spf1 carries the policy.Publish and find the recordexample.org TXTv=spf1 ip4:192.0.2.10 -allTwo SPF policy records → permerror
03
Reject ambiguity

Do not choose arbitrarily between two competing SPF policy records.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Only TXT is used by this specification; the older SPF RR type is discontinued.

  • Only TXT is used by this specification; the older SPF RR type is discontinued.
  • Multiple SPF records for one owner name cause a permerror.
  • A TXT record can contain multiple character strings that are concatenated.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Which identity SPF checks
  2. Publish and find the record
  3. Mechanisms and qualifiers
  4. DNS work and errors
  5. Forwarding and result meaning
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗