Free SPF Record Generator

Q: Why Use an SPF Generator Instead of Writing the Record Yourself?

A generator builds the correct syntax and adds the right include value for your provider. This means fewer typos and no need to look up each provider’s details manually.

Q: Is the SPF Record Generator Free?

Yes, Warmy’s SPF record generator is free. You don’t need a subscription to use it.

Q: How Often Should You Update Your SPF Record?

Update the record after you add or remove a sending service. Keep a change log noting the date and the provider affected, then check that your active services pass the record after each edit.

Q: How Do I Check or Test My SPF Record?

To test an SPF record, send a message through your sending service to Gmail, click Show original, and check that the SPF result says pass. You can also paste the headers into our Email Header Analyzer.

Q: Can a Domain Have More Than One SPF Record?

No, because two policies at the same domain cause permerror (a permanent authentication error), and SPF fails for both. Merge them into one, then check the SPF record: start with v=spf1 and stay within 10 DNS lookups. Subdomains can each have their own.

Warmy’s free SPF record generator creates a valid record for your domain and email provider, ready to paste into the DNS settings.

1Domain

2ESP

3Email

4SPF value

Let's secure your domain! Enter the domain to set up SPF records

Incoming mail servers use SPF (Sender Policy Framework) records to check if the message comes from a legitimate server. Incorrect or missing SPF settings may cause even entirely valid emails to go to spam or be rejected. Our SPF record builder generates the value for your chosen provider without you having to write any syntax.

Trusted for Better Email Deliverability

Award-winning on G2

A white and teal triangle with black text.

What Is an SPF Record?

An SPF mail record is a DNS TXT entry that the Sender Policy Framework uses to identify the servers allowed to send email for your domain. Receivers look it up for the envelope sender domain, usually visible in the Return-Path header.

For example, a Google Workspace entry could look like this:

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

v=spf1 identifies the entry as an SPF policy.
include:_spf.google.com authorizes Google’s sending servers.
~all marks other sending sources as a soft fail.

An SPF entry is always a TXT record. The “a” you might see inside it is a mechanism for checking the A record, but the entry itself is not an A record.

Benefits of a Correct SPF Record

A correct configuration helps receiving servers verify your sending sources and may even reduce delivery failures and spam placement.

Sender Authentication

Your policy identifies the servers allowed to send email for your envelope sender domain. The receiving server checks whether that policy authorizes the sending server’s IP address. The verification happens for every message.

daniel@warmy.io

The sender of this email is using an authenticated domain

Hello Jane,

I noticed you're exploring ways to grow your affiliate business. We’ve tailored an exclusive offer designed to help you earn more on every sale and engage your audience effectively. Let me know if this resonates or if you’d like to learn more.

Protection Against Domain Spoofing

SPF helps receiving servers identify and filter emails sent from unauthorized servers using your domain. It achieves this by checking the domain in the message’s return address, which can differ from the From address recipients see. To protect that visible address, create a DMARC record, which tells receivers how to handle messages that fail the check.

SPF record blocking a spoofed phishing email before it reaches the inbox

Better Chances of Reaching the Inbox

Gmail and Yahoo require SPF or DKIM from all senders, and bulk senders (5,000+ messages a day) also need DMARC. Microsoft enforced similar requirements in May 2025. Proper authentication helps prevent spam placements or rejections caused by setup errors. Once it’s configured, run a free email deliverability test.

daniel@warmy.io

SPF Score 97%

Gmail82%
Outlook87%
Zoho mail95%
Yahoo90%

A Foundation for DMARC and BIMI

DMARC can use a passing SPF result when it aligns with your visible From domain. To set up BIMI for logo display in supported inboxes, DMARC needs to apply p=quarantine or p=reject with pct=100 across your domain and subdomains.

How to Create an SPF Record With the Generator

These are the four steps to create an SPF record:

Enter your domain
Use the domain you send email from and enter the name without https:// or a page address.
Choose your email provider
Select the service that sends your email. The generator uses that provider’s include to authorize its sending servers.
Enter your email address
Add the email address where you want to receive the newly created record.
Copy the value
Copy the complete line beginning with v=spf1. Keep the spaces intact and follow the publishing steps below.

The ending ~all marks unlisted senders as a soft fail. -all marks them as a fail; receiving servers may reject their messages.

Using More Than One Email Service

Warmy’s SPF generator handles one provider at a time. If services share a sending domain, add their include: values before ~all.

An SPF record for Google Workspace can look like this:

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

Here’s an example with SendGrid:

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

Keep one record per sending domain, with one v=spf1 and a final all. Validate the SPF record syntax and limit DNS lookups to 10. Never use +all; it authorizes everyone.

Email provider	Common include value
Google Workspace	`include:_spf.google.com`
Microsoft 365	`include:spf.protection.outlook.com`
SendGrid	`include:sendgrid.net`
Mailgun	`include:mailgun.org`
Amazon SES (custom MAIL FROM)	`include:amazonses.com`

Google Workspace
Common include value
include:_spf.google.com
Microsoft 365
Common include value
include:spf.protection.outlook.com
SendGrid
Common include value
include:sendgrid.net
Mailgun
Common include value
include:mailgun.org
Amazon SES (custom MAIL FROM)
Common include value
include:amazonses.com

Use your provider’s required DNS host. For Amazon SES, publish this value on the custom MAIL FROM subdomain alongside its MX entry.

Sending From a Service Not on the List

For a service that’s not listed, use the include: value from its official setup instructions and add it before the final all mechanism. If you send mail directly through your own server, add ip4: and its public sending IP.

How to Publish Your SPF Record in DNS

Publish the generated value as a TXT entry in your domain’s DNS settings.

Open your DNS settings
Log in to your DNS host, usually your registrar (GoDaddy, Namecheap, etc.), hosting provider, or Cloudflare.
Check existing entries
Look for v=spf1. If an SPF policy exists, edit it instead of adding another one.
Set the host and value
For the root domain, use @ or your host’s equivalent, not _spf. For a sending subdomain, use its specified name. Paste the complete value.
Save the change
The updates should appear in a couple of minutes or in a few hours.

Once an SPF record lookup confirms the change, send a test message and check the result in your email headers.

SPF is Set. Let Adeline Check the Rest

A passing SPF check doesn’t cover the whole setup. DKIM or DMARC errors on another sending platform can still affect delivery.

Adeline, our AI email deliverability agent, connects to sending platforms, including SendGrid and Mailgun, diagnoses authentication problems, and identifies what to fix first. Trained on billions of deliverability data points, she can guide you through the whole process.

Start Your Free Trial

FAQ

What Is an SPF Record Generator?

An SPF record generator creates a DNS value for your chosen sending provider. By supplying the syntax and authorization details, it gives you a complete line of text you can publish in your domain’s DNS.