SPF
Also called: Sender Policy Framework
SPF (Sender Policy Framework) is a DNS TXT record that lists the servers allowed to send email for your domain, so receivers can spot mail from anywhere else.
A typical record looks like v=spf1 include:_spf.google.com ~all. Receivers check the server that delivered a message against the record for the envelope sender’s domain. -all says other servers are not authorised; ~all (softfail) is a weaker statement that they probably aren’t (RFC 7208).
SPF evaluation is limited to 10 DNS-querying terms such as include, a and mx. Going over makes SPF return a permanent error, which counts as a failure.
How it affects cold email
Gmail and Yahoo require SPF or DKIM from every sender, and both for bulk senders (Google, Yahoo). A broken SPF record is one of the most common reasons a new cold email domain lands in spam.
Every tool that sends as your domain needs to be in the record, but each include uses lookups. Remove services you no longer use.
How Inboxed handles it
- Inboxed sends through your own mailbox (Google Workspace, Microsoft 365, Zoho or any SMTP server), so the record you need is your mailbox provider’s. There is no Inboxed server to add.
- The free domain checker and the Mailboxes page look up your SPF record live and explain any problem in plain language.
Related terms
Sources
Sources checked on 8 November 2026. Rules change, so check the source before you rely on a detail.
- RFC 7208: Sender Policy Framework (SPF) · IETF / RFC Editor
- Email sender guidelines · Google, Gmail Help
- Sender Best Practices · Yahoo Sender Hub
Learn more in the deliverability guide, browse the full glossary, or start free: warmup and verification cost nothing.