Free SPF record builder
Create an SPF DNS record, ready to publish.
Enter the IPs and include domains your provider documents, choose a final policy, and copy a DNS-ready TXT value with lookup-count warnings. No account required.
Empty
Add the IPs and includes your ESP documents, pick a policy, and generate a draft SPF record for review.
How to use this tool
Make one small, informed decision.
- 1.List the IPs and include domains your ESP documents for your sending setup.
- 2.Choose a final policy (~all soft-fail or -all hard-fail) and generate the draft TXT.
- 3.Publish the record in DNS, then verify with the SPF checker before you scale outbound.
What the result means
This builds a draft record from your inputs — it does not look up live DNS. After publishing, use the SPF checker to confirm lookup count, policy, and include chains on the domain you send From.
Limitations and privacy
Record generation runs locally in your browser. Nothing is uploaded or stored on our servers.
Go deeper
Why this matters
Domain setup is part of safer outbound.
What this generates
A draft v=spf1 TXT string from the mechanisms you enter. It does not look up live DNS or prove a specific server is authorized.
The 10-lookup limit
Each include, a, and mx counts as one lookup term. Nested includes at publish time can push you over RFC 7208’s limit of 10.
Policy choices
~all is a soft fail, -all is a hard fail, ?all is neutral. We do not offer +all — it authorizes any sender.
One record only
A domain may publish exactly one v=spf1 TXT record. Replace the record you already have — do not add a second one — and merge any other provider’s include: into it.
Publish carefully
Copy the record into DNS as TXT on the apex (or bounce domain), then verify with a live SPF checker before you scale outbound.
Related tools
Common questions
SPF Record Generator FAQ
Is this the same as an SPF checker?
No. This builds a draft record from your inputs. The SPF checker resolves what is already published and walks includes live.
Why can’t I select +all?
+all authorizes every host. That is unsafe for outbound domains, so it is not offered here.
Can I publish this next to my existing SPF record?
No. A domain may have exactly one v=spf1 TXT record; two is a permerror under RFC 7208 §4.5, which fails SPF for every message you send and cascades into DMARC. Replace your existing record with this one, and if you also send through another provider, merge its include: into this record rather than publishing both.
Will this configure my ESP?
No. You still need to publish the TXT in DNS and complete any provider-side setup they require.
Next step
Record drafted. Ready to run outreach you approve first.
OmniReach drafts personalized LinkedIn and email sequences. You review the first touch — nothing sends without a deliberate launch.
Free forever tier · No credit card required · Setup in 2 minutes