Multiple SPF records (why that is invalid)
A domain can have only one SPF record. If two or more TXT records at the same name start with v=spf1, the standard result isn't "the receiver picks one." It's permerror: SPF can't be evaluated, so it can't pass for any of your mail at receivers that follow the standard, not just for the newest tool. The fix is to combine everything into one record with one all at the end. Other TXT records at the same name are fine, and subdomains can each have their own single SPF record.
Why multiple SPF records are invalid
Multiple SPF records are not permitted for the same name. A domain must not have more than one record that an authorization check could select.
Here's what a receiver does. It looks up all TXT records at the domain, throws away every one that doesn't begin with exactly v=spf1, and if more than one record remains, the result is permerror. Permerror is a permanent error that needs someone to fix DNS.
The usual way it happens: you already have SPF for your mailbox provider, a new platform's setup page says "add this SPF record," and the DNS form creates a second TXT entry. Every new entry in that form is a separate record.
What counts as "an SPF record"
Only a TXT record at that exact name whose value starts with v=spf1. That rules a lot out:
- Other TXT records are fine. Site verification codes and similar records can sit next to your SPF record; receivers discard them during selection. (They do still add to the size of the DNS answer.)
- DKIM keys aren't at the same name. They live at selector names like
selector1._domainkey.example.com. - Subdomains are separate names.
example.comandnews.example.comcan each have one SPF record. Only one SPF record is allowed per domain or subdomain. - One record split into several quoted strings is still one record. The strings are joined without spaces before evaluation.
- Old record types. A leftover
v=spf2.0(Sender ID) record or an old SPF-type DNS record isn't selected by SPF v1, but you should delete them anyway.
What happens to your mail
The standard result is permerror: the receiving system can't determine which record to evaluate, so SPF can't pass. Some receivers may try to guess which record is correct, but most won't. Mail can still be delivered or land in spam, depending on the receiver. The honest summary is that SPF won't reliably pass anywhere, and what that does to delivery depends on the receiver.
For DMARC, permerror isn't a pass, so SPF can't contribute an aligned pass for that domain. Mail can still pass DMARC through aligned DKIM. DMARC aggregate reports show the SPF result per source, which is a practical place to spot the problem (A field-by-field walk-through of a DMARC aggregate report).
How to combine SPF records into one
- List every
v=spf1value at that name. Your DNS host's TXT list, or a DNS lookup, will show them. - Build one record. Start with
v=spf1, add every neededinclude:,ip4:, andip6:from all the old records (once each), and end with oneall. - Choose the ending deliberately. If the old records ended differently, don't keep both. Everything after the first
allis ignored. We recommend~allfor sending domains; see Softfail vs fail (~all vs -all). - Recount lookups. Merging two records often pushes the total past 10, which gives permerror again for a different reason. If it does, drop retired senders or move one platform to a subdomain (The 10-lookup limit and SPF permerror).
- Replace, then delete. Update one record to the merged value and delete the others. Allow for DNS caching; changes can take 24 to 48 hours to show up everywhere.
An example, using common vendor includes:
Before (invalid, two records at example.com):
v=spf1 include:_spf.google.com ~all
v=spf1 include:servers.mcsv.net ~all
After (valid, one record):
v=spf1 include:_spf.google.com include:servers.mcsv.net ~all
The checker message "multiple SPF records found" means exactly this situation. The short troubleshooting version is in Two SPF records.
How to add multiple SPF records (merge them into one)
If you searched for how to add multiple SPF records for one domain, the answer is that you don't. You add more senders to the one record you have. For a new platform:
- Take only the
include:(or the IP ranges) from the vendor's instructions, not the wholev=spf1 ... ~allline. - Put it before your
all. - Recount lookups.
Even better, where the vendor supports it, set up DKIM signing with your domain so its mail can pass DMARC without touching your SPF record at all (SPF include vs DKIM from the vendor). The full process for adding a vendor is in How to add a third-party sender without breaking DMARC.
Mistakes worth avoiding
- A DNS host form that creates one TXT entry per value. Each entry is its own record.
- Merging badly. Two
v=spf1tokens inside one string is a syntax error (permerror). Twoallterms means the second half of your record is dead. - Pasting a vendor's sample record into the middle of yours, so its
~allends your record early. - Not recounting lookups after the merge.
- Leaving an old
v=spf2.0record because it "probably doesn't hurt."
Preventing it next time
Give the SPF record one owner, and make every new tool go through that person (Who usually owns SPF, DKIM, and DMARC). Other common slips are in Common SPF mistakes, and record syntax is in How to write an SPF record.
Free DMARC account
Turn raw DMARC reports into a readable dashboard
Point your rua address to our platform and read the results by sender and source instead of opening XML files.
- Results grouped by sending source
- SPF, DKIM and alignment results per sender
- The original XML reports are still there to download
FAQ
Can you have multiple SPF records?
Not at the same name. Two v=spf1 records give a permanent error. Merge them into one.
Can I have other TXT records too?
Yes. Only records starting with v=spf1 count as SPF records.
Do subdomains count as multiple SPF records?
No. Each subdomain is its own name and can have its own single SPF record.
How do I add a new email platform to SPF?
Add its include: to your existing record, keep one all at the end, and recount lookups. Or authenticate it with aligned DKIM.
Is a long record split into two quoted strings "two records"?
No. It's one record; the strings are joined before evaluation.