SPF generator
SPF Record Generator & Builder
Select services using this domain in MAIL FROM, add your servers and build a draft SPF record. Verify live DNS before publishing.
What to do with the result
Your lookup estimate is below 8
The real count can be higher or lower: the generator uses fixed estimates, without DNS queries. Before publishing, check each include in the SPF Checker; its count plus one is the cost of including it. Add those costs and any a or mx terms. Stay within 10.
- Preserve senders you still use and edit your existing SPF record. A second record causes
permerror. - With no existing record, create one TXT at your sending domain.
- After its TTL expires, confirm the full record in the SPF Checker and test mail from every service.
Your lookup estimate is close to 10
The estimate is 8 to 10; the real count can differ. Fixed estimates may miss changes in a provider’s nested includes. Check each include before publishing: its SPF Checker count plus one is its cost in your record.
Remove services only after confirming they no longer send. ip4 and ip6 add no lookups; a and mx each count toward the limit. If the total exceeds 10, use the next case. Publish one record, then confirm its full count and test every sender.
Your lookup estimate is over 10
Confirm the count before changing senders: the estimate can be higher or lower than live DNS. Check each include in the SPF Checker and add one to its count. Include any a and mx terms. If the total exceeds 10, do not publish it: SPF returns permerror when evaluation reaches the excess term.
- Remove services that no longer send.
- Move a service to a dedicated envelope-sender subdomain with its own SPF record.
- Copied provider IPs need ongoing updates. Prefer preserving includes; stale ranges make legitimate mail fail.
A sender is missing from the record
A notice about invalid entries means the generator dropped what it could not read. The record keeps no trace of them, so compare it with your list. The IP field takes addresses or ranges such as 198.51.100.0/24. The includes field takes a bare domain, without the word include:.
A result like v=spf1 ~all lists no sender, even with a count of 0. Only a domain that never sends mail should publish an empty record, using the fail option. For any other domain, fix the form and generate again. Mail from a sender you leave out will not pass SPF.
Your record ends in -all
With -all, every unlisted server gets an SPF fail. Some receiving servers reject that mail during the SMTP conversation, before DMARC runs. RFC 9989, section 7.1, warns that this can refuse a message that would have passed DMARC through DKIM, and that the rejection never shows in aggregate reports. A forgotten sender or a forwarded message can be lost that way.
While you audit your senders, prefer ~all (softfail): receivers should not reject on that result alone. If no DMARC record exists, create one at p=none with a rua reporting address. Otherwise add reporting to the existing record and preserve its policy; do not create a second record. Consider -all or an enforcing policy (p=quarantine, p=reject) only after the reports show your legitimate mail passing.
Explained
One record, every sender
SPF authorizes servers for the envelope sender (MAIL FROM / Return-Path), which can differ from visible From. Combine services using the same MAIL FROM domain in one record. A service using its own domain or a dedicated bounce subdomain needs its own documented flow.
About the lookup estimate
The count uses fixed estimates. Provider DNS and nested includes can change; verify the full record in the SPF Checker before publishing. Confirm each preset with your account and region: the IONOS preset is for Europe. Account-specific TXT/MX or CNAME instructions take precedence.
Frequently asked questions
What does an SPF record look like?
v=spf1 include:_spf.google.com include:spf.protection.outlook.com ~all. Preserve any other authorized senders and verify the live lookup count.Why isn’t my provider in the list?
Do I need SPF for a domain that doesn’t send email?
v=spf1 -all so nobody can pass SPF with that domain.Is SPF enough to stop spoofing?
Keep it healthy
Know the moment something breaks
Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.
Free plan: 1 domain, no credit card.
Related tools