All specs
RFC 7208RFCMust KnowBack Office2014

Sender Policy Framework

Email·RFC Editor
WHY YOU NEED THIS

Without a correct SPF record, your domain's email will fail or be deferred by major receivers (Gmail, Outlook). Set correctly as part of basic email deliverability.

What It Defines

Defines SPF DNS TXT records that publish which mail servers are authorized to send email on behalf of a domain. Receiving MTAs check SPF to detect forged From addresses.

Canonical (Normative)

Convenient (Practical)

spfemaildeliverabilitydnsanti-spoofing
Standards Body
RFC Editor

The canonical publication point for finalized RFCs. If a protocol is standardized as an RFC, the RFC Editor text is the normative final reference. Published by the IETF, IRTF, IAB, and independent stream.

Visit

Related Specs

RFC 6376RFCMust Know

DKIM

DKIM is required to pass DMARC. Without it, your email won't be trusted by major providers. Set up alongside SPF as part of any serious email configuration.

Back OfficeEmail
Details
RFC 7489RFCMust Know

DMARC

DMARC is the final layer of email authentication. Without it, your domain can be spoofed in phishing. Google and Yahoo require DMARC for bulk senders.

Back OfficeEmail
Details
RFC 1035RFCMust Know

DNS Implementation

The record types (A, MX, TXT, CNAME) you configure in every DNS panel live in this spec. Know what you're setting.

Back OfficeProductNaming & Addressing
Details