What the SPF Generator does
SPF (Sender Policy Framework) tells receiving servers which mail systems are allowed to send email for your domain.
If SPF is missing or wrong, you get softfails, permerrors, random spam placement, and sometimes DMARC failures because alignment breaks.
This free SPF record creator builds a clean v=spf1 record without the usual mistakes: duplicate records, unsafe includes, and exceeding the 10-lookup DNS limit.
Enter your domain, select the providers you send from (Google Workspace, Microsoft 365, SendGrid, Mailchimp, and others), add any custom IPs, choose an enforcement level, and generate the record.
If you are here because emails are failing:
- Run the full domain check to verify SPF, DKIM and DMARC together.
- Fix SPF/DKIM/DMARC alignment issues.
- Use FixKit for copy/paste recovery steps + a client-shareable PDF.
- Enable Monitoring so this doesn’t happen again.
When you should use this
- You are setting up a new sender like Amazon SES, Mailgun, Brevo, SendGrid, Google Workspace, or Microsoft 365.
- Your emails land in spam and the header shows
spf=fail, softfail, or permerror.
- You changed providers and now have multiple includes and you are not sure what is still needed.
- You see “Too many DNS lookups” or you suspect you are close to SPF’s 10-lookup limit.
How to use it
- Enter your domain (the one in your From address).
- Select the providers you send with (only what you actually use).
- Generate the SPF record and copy it.
-
Publish it in DNS as a TXT record on the root:
- Name/Host:
@ (or blank depending on DNS provider)
- Type: TXT
- Value: the generated
v=spf1 ... line
- Wait for DNS propagation (often minutes, sometimes hours) and verify with InboxGreen checker.
Common mistakes
- Multiple SPF records: you must have only one TXT record that starts with
v=spf1. Merge them. Step-by-step guide to merging SPF records.
- Using
+all: that basically tells the world “anyone can send for me”. Don’t.
- Too many DNS lookups: too many includes can cause
permerror. How to fix the SPF lookup limit.
- Forgetting subdomains:
news.domain.com and domain.com can need separate SPF depending on how you send.
- Wrong domain in the From address: SPF checks the envelope sender (Return-Path) domain, which can differ from From.
FAQ
How many SPF records can I have?
One. If you have more than one v=spf1 TXT record, SPF can break or behave unpredictably. Merge them into a single record.
Should I use ~all or -all?
Start with ~all if you are not 100% sure you listed every sender.
Move to -all when you have verified everything and want strict enforcement.
Why does SPF pass but DMARC still fails?
DMARC needs alignment. SPF can pass for a different domain (like a bounce domain) and DMARC still fails.
If that’s happening, check alignment using InboxGreen checker and your message headers.
What does “SPF permerror too many DNS lookups” mean?
SPF evaluation involves DNS lookups and there is a limit. Too many includes, redirects, and nested records can exceed it.
The fix is reducing includes or flattening, but do it carefully so you do not break legitimate senders.
How do I generate an SPF record for my domain?
Use the generator at the top of this page. Enter your domain name, check which providers you send from (Google, Outlook, SendGrid, etc.), add any custom IP addresses, set your enforcement level, and click Generate.
You will get a v=spf1 TXT record to add to your DNS at the root (@).
After publishing, validate with the InboxGreen checker to confirm it is live and correctly formatted.
Does generating an SPF record cost anything?
No. This SPF record generator is free. No account, no email address, and no signup required.
Generate as many records as you need.
What to do next
After publishing your record, run a full scan with InboxGreen checker.
If you are also setting DMARC, use the DMARC generator to generate a safe starting policy.