One SPF record for every service that sends your mail, and nothing you forgot.
Import the record you already publish, tick the services you use, and get a single merged record. Existing senders are kept. New ones are added. The result tells you which is which.
It merges. It does not start over.
Most SPF mistakes are made by replacing a working record with a new one that leaves somebody out.
- Imports your live record
- Enter the domain and the generator looks up the SPF record currently in DNS. Every valid authorization in it is carried forward, in order; only the closing all is replaced by the one you choose.
- Adds providers by name
- Common mailbox, transactional, and marketing services, each with its include. Where a provider needs an account-specific value or no include at all, the generator says so instead of guessing.
- Shows preserved and added terms
- Two lists under the record: what came from your existing record and what is new. If something you rely on is not in either, you will see it before you publish.
- Skips duplicates
- A provider already present in your record is marked and not added twice. A redirect is converted to an include so the new senders can take effect.
- Validates addresses
- IPv4 and IPv6 ranges are checked as you type. Anything malformed is left out and listed in the warnings.
- Warns about the lookup limit
- The generator counts the lookup terms it writes. Nested includes inside each provider are counted by the SPF checker on the live record, against the limit of ten.
SPF is a guest list. The usual error is writing a new one from memory.
An SPF record names the servers allowed to send mail for a domain. One record, per domain, containing everyone. The trouble starts when a new service arrives with setup instructions that say “add this SPF record,” and somebody does, as a second record. Two SPF records are a permanent error. Receivers do not choose between them; they fail both. The correct move is always to add the new service’s include to the record you already have, which is the entire reason this tool starts by importing it.
The second constraint is the limit of ten DNS lookups, set by RFC 7208. Each include costs at least one, and large providers’ includes contain more includes. A record with five services can be over the limit without looking long. If yours is close, cut services you no longer use before adding anything, and consider sending marketing mail from a subdomain, which gets its own record and its own ten. Common SPF errors has the full list.
Finally, be clear about what SPF buys you. It authenticates the Return-Path domain, which for many services is the vendor’s own. That pass does not help DMARC unless the domain aligns with your From address. For most third-party senders, DKIM with your own domain is what makes DMARC pass, and SPF is supporting evidence. Read SPF vs DKIM vs DMARC, check keys with the DKIM checker, and once SPF and DKIM are in place, write the policy with the DMARC generator. Provider walk-throughs include SendGrid and Postmark.

What to watch for when you publish.
Adding the new record beside the old one
Edit the existing TXT record and replace its value with the merged record. If you created a second one by mistake, delete it; the checker will flag two records immediately.
A provider include that has changed
Include hostnames are set by each provider and are occasionally renamed. Confirm each against that provider's current setup page before publishing, and copy account-specific values from their console.
Over ten lookups after merging
Remove services you no longer send through. Replace includes that cover a fixed address or two with ip4 entries. Split bulk mail onto a subdomain.
A record longer than 255 characters
DNS stores TXT data in strings of at most 255 characters. Most hosts split long values automatically; a few require you to enter several quoted strings in one record.
Choosing -all too early
A hard fail on a record that is missing a sender means that sender's mail fails SPF outright. Use ~all until your DMARC reports confirm that every source is listed.
A service that sends but was never listed
You cannot list what you do not know about. DMARC aggregate reports show every source receivers saw using your domain. DMARC monitoring turns them into a list.
How to create an SPF record
Generate one SPF record that authorizes all of your sending services.
- 1
Import the current record
Enter your domain and import the SPF record already published, so existing senders are preserved.
- 2
Select your senders
Tick each service that sends mail as your domain and add any IP addresses or custom includes.
- 3
Copy the record
Review the preserved and added terms and the warnings, then copy the generated value.
- 4
Replace the TXT record
At your DNS provider, edit the existing SPF TXT record at the root of the domain, or create one if none exists. Then verify the lookup count with the SPF checker.
Questions about this tool
Straight answers. If yours is not here, ask us and a person will reply.
Not sure which services send as your domain?
That is the usual situation. Send us the domain and we will tell you what its current record authorizes and what looks stale.
- A person reads every message
- No sales sequence, no list rental
- Reply within one business day
A list of senders is a guess until the reports confirm it.
Create a free account to collect DMARC reports and see which sources are really sending mail as your domain, listed or not.
Related tools and guides
- SpoofKillerDocumentationSetup guides, feature references, and the API.Read
- DocsAlerts and NotificationsAlert types, severity thresholds, digests, and how duplicates are suppressed.Read
- DocsAPI ReferenceAuthenticate with API keys and read domains, health, sources, findings, and reports over REST.Read
- DocsData and PrivacyWhat SpoofKiller collects, why, how long it is kept, and how to export or delete it.Read
- SpoofKillerFeaturesDMARC analytics, sender identification, spoofing detection, DNS change monitoring, blacklist checks, and reports.Read
- FeatureSPF MonitoringScheduled SPF checks that count DNS lookups the way receivers do, walk every include, and warn you when a record breaks.Read
