Provider presets
Google Workspace, Microsoft 365 (commercial), Mailgun and Zoho Mail, each added as an include.
Built for agencies and B2B sales teams.Built for lead generation agencies and B2B sales teams. Manage contacts, automate email sequences, and handle replies in one workspace.
Start free →Create an SPF TXT record for your domain using supported email providers, IPv4 and IPv6 addresses, and custom SPF includes. Review the generated record, check the DNS lookup estimate, and verify your configuration before publishing.
Example: SPF record draft
Enter your domain, select every provider that sends for it, add any custom include or IP address, and choose an ending policy.
Review the warnings and the lookup estimate, then copy the generated TXT value.
Add it at your DNS host. If an SPF record already exists, update that record instead of adding a second one.
Once DNS has updated, run the SPF Checker on the domain.
It builds include, ip4 and ip6 terms and ends the record with an all policy. It does not build a, mx, exists, redirect or exp terms.
Google Workspace, Microsoft 365 (commercial), Mailgun and Zoho Mail, each added as an include.
Add a single include domain from another sending service.
Add one IPv4 and one IPv6 address or range as ip4 and ip6 terms.
End the record with -all, ~all or ?all.
An estimate against the limit of 10, marked incomplete when included records cannot be fully read.
Warns when your domain already publishes an SPF record, so you update it rather than duplicate it.
These are illustrative configurations, not universal records. Your domain may have other senders, and providers can change their values, so confirm them in your provider documentation.
Illustrative: assumes Google Workspace is the only sender and ends in softfail.
Illustrative: assumes commercial Microsoft 365 is the only sender and ends in fail. Other Microsoft clouds can use different values.
These use records tied to your account, so there is no automatic preset. Follow the account-specific domain authentication instructions in the provider dashboard, publish the DNS records it shows, and add any include it supplies as a custom include.
The ending tells receivers how to treat mail from senders you did not list. Receivers decide what to do with the result, so SPF alone does not decide delivery or rejection.
| Policy | SPF result | Meaning | Guidance |
|---|---|---|---|
| -all | SPF fail | Unlisted senders are not authorized | Use once every sender is covered |
| ~all | SPF softfail | Unlisted senders are probably not authorized | A common starting point while you confirm senders |
| ?all | SPF neutral | No statement about unlisted senders | Rarely useful |
| +all | Unsafe | Authorizes every server | Not offered by this generator |
A domain should publish one v=spf1 record. Merge new senders into the existing one.
The generator cannot detect senders you do not select or enter.
Included records add their own DNS-querying terms. Remove providers you no longer use.
It authorizes every server, which removes SPF's protection. This generator does not offer it.
The generator creates DNS text only and never changes your DNS. It cannot confirm that every sending service is covered, and SPF alone does not guarantee inbox placement. Check Google's current sender guidelines, which call for SPF, DKIM and DMARC for high-volume senders.
Add a TXT record. The host or name is usually @ for the domain root, though some DNS hosts want the full domain name. Paste the value exactly as generated.
If the tool warns that an SPF record exists, edit that record to include the new senders and keep one v=spf1 value.
After DNS updates, run the SPF Checker. Then review DKIM and DMARC, or see all three in the Email DNS Checker.
It builds the SPF TXT value for your domain from the providers, include domains and IP addresses you choose, so you do not have to write the syntax by hand. It does not change your DNS.
Enter your domain, select the providers that send email for it, add any custom include or IP address, choose a policy and generate. Copy the TXT value, publish it at your DNS host, then verify it with the SPF Checker.
It builds include, ip4 and ip6 terms and ends the record with an all policy. It does not build a, mx, exists, redirect or exp terms, and it takes one custom include, one IPv4 value and one IPv6 value.
No. A domain should publish one v=spf1 record. If your domain already has one, review it and merge the new senders into it instead of adding a second record.
The generator looks up the current TXT records when DNS answers and warns you if an SPF record exists. It does not merge anything for you. Update your existing record by hand and keep a single v=spf1 value.
SPF evaluation allows at most 10 DNS-querying terms, such as include, a, mx, ptr, exists and redirect. The records you include can add their own terms, so the total can be higher than the number of includes you wrote.
The estimate expands included records over DNS. If a lookup fails or an included record cannot be read, the estimate is marked incomplete and the real count may be higher. Treat it as unconfirmed and check the published record with the SPF Checker.
Many domains start with ~all (softfail) while they confirm every sender, then move to -all (fail) once the list is complete. Receivers decide what to do with the result, so SPF alone does not decide delivery or rejection.
A +all ending authorizes every server to send for your domain, which removes the protection SPF is meant to give. The generator does not offer it.
Select the provider. Google Workspace uses include:_spf.google.com and Microsoft 365 (commercial) uses include:spf.protection.outlook.com. Other Microsoft clouds can use different values, so confirm them in your provider documentation.
Their SPF and domain authentication records are tied to your account, so a generic include would not be reliable. Use the DNS records shown in the provider dashboard, and add any include they give you as a custom include.
After you publish it and DNS has updated, run the SPF Checker to confirm that one record is found, the policy is what you chose and the lookup count is within the limit.
It helps receivers verify who may send for your domain, but delivery also depends on DKIM, DMARC, sender reputation, content and list quality.
Healthy authentication protects your domain. Clean contacts protect your sender reputation. Cleaner outreach starts with better data.