Built for agencies and B2B sales teams.

Start free →

Free SPF Record Generator

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.

One SPF recordDNS lookup estimateCopy the TXT value
SPF Record GeneratorFreeExample result

Twilio SendGrid and Brevo use account-specific records, so there is no automatic preset. Follow the domain authentication instructions in the provider's dashboard and publish the records it shows.

EXAMPLE

Example: SPF record draft

v=spf1 include:_spf.google.com ~all
DNS record typeTXT
Host / name@ (the domain root)
Selected policy~all (SPF softfail)
This is a sample. Generate a record for your domain to see the lookup estimate and warnings.
Publish only one SPF record per domain, and merge senders into it.
How it works

Create, copy, publish, verify

  1. 01

    Create

    Enter your domain, select every provider that sends for it, add any custom include or IP address, and choose an ending policy.

  2. 02

    Copy

    Review the warnings and the lookup estimate, then copy the generated TXT value.

  3. 03

    Publish

    Add it at your DNS host. If an SPF record already exists, update that record instead of adding a second one.

  4. 04

    Verify

    Once DNS has updated, run the SPF Checker on the domain.

Supported terms

What this SPF record generator builds

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.

Provider presets

Google Workspace, Microsoft 365 (commercial), Mailgun and Zoho Mail, each added as an include.

One custom include

Add a single include domain from another sending service.

IPv4 and IPv6

Add one IPv4 and one IPv6 address or range as ip4 and ip6 terms.

An all policy

End the record with -all, ~all or ?all.

Lookup estimate

An estimate against the limit of 10, marked incomplete when included records cannot be fully read.

Existing record warning

Warns when your domain already publishes an SPF record, so you update it rather than duplicate it.

Provider examples

Illustrative SPF record examples

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.

Google Workspace

v=spf1 include:_spf.google.com ~all

Illustrative: assumes Google Workspace is the only sender and ends in softfail.

Exchange Online (Microsoft 365)

v=spf1 include:spf.protection.outlook.com -all

Illustrative: assumes commercial Microsoft 365 is the only sender and ends in fail. Other Microsoft clouds can use different values.

Twilio SendGrid and Brevo

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.

Policy choices

What -all, ~all, ?all and +all mean

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.

PolicySPF resultMeaningGuidance
-allSPF failUnlisted senders are not authorizedUse once every sender is covered
~allSPF softfailUnlisted senders are probably not authorizedA common starting point while you confirm senders
?allSPF neutralNo statement about unlisted sendersRarely useful
+allUnsafeAuthorizes every serverNot offered by this generator
Common mistakes

Common SPF mistakes and how to avoid them

Publishing multiple SPF records

A domain should publish one v=spf1 record. Merge new senders into the existing one.

Forgetting a sender

The generator cannot detect senders you do not select or enter.

Exceeding 10 lookups

Included records add their own DNS-querying terms. Remove providers you no longer use.

Ending with +all

It authorizes every server, which removes SPF's protection. This generator does not offer it.

A draft, not a guarantee

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.

Publish and verify

Publishing and verifying your SPF record

Publish at your DNS host

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.

Update, do not duplicate

If the tool warns that an SPF record exists, edit that record to include the new senders and keep one v=spf1 value.

FAQ

SPF Record Generator FAQ

Still unsure? Read the DevBoxy blog or contact the team.

What is an SPF record generator?

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.

How do I create an SPF record for my domain?

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.

Which SPF terms does this generator support?

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.

Can I publish multiple SPF records?

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.

What if my domain already has an SPF 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.

What is the SPF 10 DNS lookup limit?

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.

Why does the lookup estimate say it is incomplete?

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.

Should I choose -all or ~all?

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.

Why is +all not offered?

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.

What should I enter for Google Workspace or Microsoft 365?

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.

Why are SendGrid and Brevo not selectable?

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.

How do I verify the generated SPF record?

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.

Does SPF improve email deliverability?

It helps receivers verify who may send for your domain, but delivery also depends on DKIM, DMARC, sender reputation, content and list quality.

Pair DNS checks with list verification.

Healthy authentication protects your domain. Clean contacts protect your sender reputation. Cleaner outreach starts with better data.