SPF Record
SPF (Sender Policy Framework) records authorize specific IP addresses to send email on behalf of a domain — the foundational email authentication standard preventing domain spoofing and supporting deliverability.
Why This Matters
SPF record mechanics: domain owner publishes DNS TXT record listing authorized sender IPs (typically email service providers, internal mail servers, third-party tools); receiving mail servers check SPF record during message validation; messages from non-authorized IPs marked as suspicious. Most B2B email infrastructure requires SPF setup including: marketing automation platform IPs, transactional email service IPs, internal mail server IPs, and third-party tools sending email as domain. Misconfigured SPF causes deliverability problems; proper SPF setup foundational to email program success.
Frequently Asked Questions
Frequently Asked Questions
What goes in an SPF record?
Authorized sender IPs and IP ranges. For B2B SaaS: ESP IPs (HubSpot, Marketo, etc.), transactional email IPs (SendGrid, Mailgun), Google Workspace or Microsoft 365 IPs, and any third-party tool sending email as domain.
What happens with misconfigured SPF?
SPF failures trigger spam filter scrutiny, often resulting in spam folder placement or rejection. Major ESPs (Gmail) require SPF passage for inbox placement. SPF misconfiguration is common cause of deliverability problems.