Free tool · DNS & authentication

Free SPF Record Generator

Tick the services that send email as your domain, add any servers of your own, and get a valid SPF TXT record to paste into your DNS. Everything runs in your browser.

Services that send email as your domain

Each entry follows the vendor's own setup guide, checked on 13 Nov 2026. Several services need no change to this record at all, and the list says so.

One domain per line, from the setup guide of a service not listed above.

IPv4 or IPv6, single addresses or CIDR ranges, for mail servers you run yourself.

Your own servers
Mail from any other server

+all is not offered: it authorises every server on the internet to send as your domain, which is the opposite of what SPF is for.

Type: TXTHost / name: @ (the domain itself; for a subdomain, enter the subdomain's name)
v=spf1 ~all

Checks

  • No DNS lookups used. ip4 and ip6 entries and the all mechanism do not count toward the limit of 10.
  • No senders listed yet. Tick a service or add an include or IP address. For a domain that never sends email, publish "v=spf1 -all".
  • Ends with ~all (soft fail): mail from servers not listed is accepted but marked as suspicious. A safe setting while you confirm every sender is listed.
  • A domain must have exactly one SPF record. If the domain already has a TXT record starting with v=spf1, merge these entries into it instead of adding a second record: two records make SPF fail with a permanent error.

The lookup count here covers only the entries in this record. After publishing, run the SPF checker to follow every nested include and get the true total.

How to use the SPF generator

  1. Tick every service that sends email as your domain. Think beyond your mailbox provider: help desk, CRM, invoicing and newsletter tools all send mail with your address in the From line.
  2. Add servers you run yourself. Enter their IP addresses or ranges, or tick mx if the servers that receive your mail also send it.
  3. Choose the ending. Keep ~all while you are still finding senders. Tighten it to -all later.
  4. Copy the record and create a TXT record on the host @ in your DNS. If a record starting with v=spf1 is already there, edit it instead of adding another.
  5. Verify it with the SPF checker a few minutes later. The checker follows every nested include and reports the true lookup count.

The parts of an SPF record

TermMeaningDNS lookups
v=spf1Version. Required and must come first.0
include:Authorises every server in another domain's SPF record, usually a provider's.1, plus any nested inside it
ip4: / ip6:Authorises one address or a CIDR range.0
aAuthorises the addresses in the domain's own A or AAAA record.1
mxAuthorises the servers named in the domain's MX records.1
~all / -allWhat to do with every other server: soft fail or hard fail. Must come last.0

Why some services need no SPF include

Receivers check SPF against the Return-Path domain (the envelope sender), not the address in the From line. Many email platforms put their own domain in the Return-Path, or ask you to point a subdomain at them with a CNAME record and manage SPF behind it. In both cases your root record is never consulted for that mail, so adding the platform's include only spends one of your ten lookups.

The generator follows each vendor's own setup guide. Where the guide asks for an include, ticking the box adds it. Where it does not, the service is marked "no SPF include needed" with the reason and a link to the vendor's page. For those services DMARC passes through an aligned DKIM signature instead, so finish the DKIM step in the vendor's setup and confirm the key with the DKIM checker.

If your service is not listed, look for "SPF" in its domain authentication guide and paste the documented include under extra includes. Vendors change their setup over time, so the vendor's current page is the authority, not this list.

Staying under the limits

  • 10 DNS lookups. The count shown by the generator covers only the terms in your record. Provider includes usually contain further includes, so a record with five or six services can already be over. See how to fix SPF PermError for too many DNS lookups.
  • 255 characters per string. A longer record is still one TXT record, but it has to be published as several quoted strings. The generator shows the split version when you need it.
  • One record per domain. Each subdomain that sends mail needs its own record, and each name may hold only one.

When a record gets crowded, move a service to its own subdomain, such as news.example.com for marketing mail. Every subdomain has its own SPF record and its own budget of ten lookups, and problems with one mail stream stop affecting the others. The details are in using a subdomain for sending email.

Common mistakes

  • Adding a second v=spf1 record when a new service says "add this SPF record". Merge the include into the existing record.
  • Leaving includes for services you stopped using. Each one still costs a lookup and still authorises that provider's servers.
  • Writing include=, adding a space after the colon, or ending a domain with a dot. Any syntax error invalidates the whole record.
  • Listing a very large IP range to be safe. Everyone inside the range can then send as your domain.

After SPF: DKIM, DMARC and list quality

SPF alone does not protect the address your recipients see. Sign your mail with DKIM, then publish a policy with the DMARC generator; the three work together, as explained in SPF, DKIM and DMARC explained. Authentication proves the mail is yours. Mailbox providers also watch how much of it bounces, so verify your list before a campaign to keep invalid addresses out of it.

Frequently asked questions

Verify your list before you send

InboxSure checks every address with syntax, MX and SMTP mailbox checks, and flags catch-all, role-based and disposable addresses. Free to start.