Email Authentication

What is an SPF record, and why does your cold email need one?

Inboxlogy7 min readUpdated 2026-10-26

In short: An SPF record is a line in your DNS that lists which servers are allowed to send email for your domain. When a mailbox provider receives your mail, it checks the sending server against this list. If the server is not authorised, the message looks like spoofing and is far more likely to land in spam. SPF also has a hard cap of 10 DNS lookups, and going over it quietly breaks authentication.

What does an SPF record do?

SPF stands for Sender Policy Framework. An SPF record is a single DNS TXT record that starts with v=spf1 and names every server or service allowed to send email as your domain. When your message arrives, the receiving server reads the SPF record and checks whether the connecting server is on the list. If it is, the message passes SPF. If it is not, it fails, and failing SPF is one of the clearest signals of a forged sender.

Key point: SPF protects your domain from being spoofed and tells mailbox providers your real senders are legitimate. Without it, anyone can send email pretending to be you, and your genuine mail looks less trustworthy.

What does an SPF record look like?

A typical SPF record reads like this:

v=spf1 include:_spf.google.com include:sendgrid.net ~all

Breaking it down: v=spf1 declares the version, each include: authorises another service's servers, and the final ~all is the policy for everything else. ~all means "soft fail" (accept but mark suspicious), while -all means "hard fail" (reject). Most senders start with ~all and tighten to -all once they are confident every sender is listed.

What is the SPF 10-lookup limit?

This is the rule that catches most people out. SPF allows a maximum of 10 DNS lookups when it evaluates your record. Every include:, a, mx, ptr and redirect can trigger one or more lookups, and nested includes add up fast. Go over 10 and SPF returns a permerror, which means it fails even though your record looks fine. A good SPF Checker counts these lookups for you so you can catch the problem before mailbox providers do.

Why SPF matters most for cold email

Cold email sends from new domains with no reputation, so every trust signal counts. SPF is the cheapest, fastest one to get right. A domain that passes SPF, DKIM and DMARC looks like a real business. A domain failing SPF looks like a spammer spoofing someone else, which is exactly the profile filters are trained to catch. If you run outreach across several sending tools, SPF also keeps you honest about which services are actually authorised to send as you.

Check your SPF record free

Validate your SPF syntax, see the policy, and count your DNS lookups against the 10-lookup limit in one click.

Open the SPF Checker →All free tools

Frequently asked questions

Can I have more than one SPF record?
No. A domain must have exactly one SPF record. Two or more v=spf1 records cause a permerror and break SPF entirely. If you need to authorise multiple services, combine them into a single record using multiple include: statements.
What is the difference between ~all and -all?
~all is a soft fail: mail from unlisted servers is accepted but flagged. -all is a hard fail: mail from unlisted servers is rejected outright. Start with ~all while testing, then move to -all once you are sure every legitimate sender is included.
What happens if I exceed 10 DNS lookups?
SPF returns a permerror and effectively fails for every message, even legitimate ones. Reduce includes, flatten nested records, or remove unused services to get back under the limit. An SPF Checker shows your current lookup count.
Does SPF alone stop my email going to spam?
No single record does. SPF is one of three pillars alongside DKIM and DMARC. You need all three aligned for the strongest inbox placement. SPF on its own helps, but DMARC enforcement depends on SPF or DKIM passing and aligning with your domain.