Two SPF records
Two SPF records on the same domain break SPF. If two TXT records at the same name both start with v=spf1, receivers don't pick one: the result is permerror, and SPF can't pass for mail checked against that name. That's every sender using it, not just the one you added last. The fix is to merge both into a single v=spf1 record with one all at the end, then delete the extra one.
Why the standard forbids it, and the full merge walkthrough, are in Multiple SPF records (why that is invalid). This page is the quick diagnosis.
Is it really two SPF records?
A receiver looks up every TXT record at the name, keeps only the ones that begin with v=spf1, and if more than one record remains, the result is permerror.
So it counts as two SPF records only when both are true:
- they're TXT records at the same name, such as
example.com, and - each value begins with
v=spf1.
These don't count:
- Other TXT records at the same name, like site-verification strings. Receivers discard them.
- One record split into several quoted strings.
"v=spf1 include:_spf.mailhost.example " "include:spf.crm-vendor.example ~all"is one record. The strings are joined with no space added, so keep a space at the end of the first string. - Records at different names.
example.comandmail.example.comeach get their own single record. - A
v=spf10or other version string. It's discarded rather than conflicting, which also means it doesn't work.
SPF is published as a TXT record. The old dedicated SPF record type is discontinued, so a leftover one isn't your SPF record either.
To check, list the TXT records at the name with your DNS host or a DNS lookup tool, and count the values that start with v=spf1.
What it does to your mail
- The standard result is permerror: multiple SPF TXT records for the same domain or subdomain mean SPF can't be evaluated. The same cause sits next to the 10-lookup limit as a common reason SPF breaks.
- Each domain can have only one SPF record. If you have multiple SPF records, your email might end up in a recipient's spam folder, or be treated as a permanent error, depending on the receiver.
Whether a receiver rejects, junks, or just treats SPF as not passing is up to that receiver. For DMARC, SPF can't supply an aligned pass while the domain is in permerror. Mail with an aligned DKIM signature can still pass DMARC; mail that relied on SPF alone fails. Your DMARC aggregate reports show the SPF result per source, which is a practical place to spot it (A field-by-field walk-through of a DMARC aggregate report).
How it happens
- A new platform's setup page says "add this TXT record," and someone adds the vendor's whole
v=spf1... ~allline as a new entry instead of adding its include to the existing record. - A DNS host migration recreates a default SPF record next to the one you copied over.
- A move between mailbox providers adds the new provider's record while the old one is still there (Microsoft 365 or Google Workspace setup issues).
How to fix two SPF records
- Copy both values somewhere safe before you edit anything.
- Build one record. Start with
v=spf1, add everyinclude:,ip4:, andip6:you still need from both records (once each), and end with a singleall. For sending domains we use~all(Softfail vs fail (~all vs -all)); if the two records ended differently, pick one ending on purpose. - Drop senders you no longer use while you're there. Check your DMARC reports before removing anything (How to inventory sending sources).
- Recount lookups. Two records that were each under 10 can add up to more than 10 once merged, which is permerror again for a different reason (SPF permerror: too many DNS lookups).
- Update one record to the merged value and delete the other. Changes can take 24 to 48 hours to take effect.
Example for example.com, with placeholder includes:
Before (two records, permerror):
v=spf1 include:_spf.mailhost.example ~all
v=spf1 include:spf.crm-vendor.example ~all
After (one record):
v=spf1 include:_spf.mailhost.example include:spf.crm-vendor.example ~all
Use the include values from each provider's current documentation. Syntax details are in How to write an SPF record.
Mistakes worth avoiding
- Keeping two
allterms in the merged record, or pasting a vendor line into the middle so its~allends the record early. Nothing after the firstallis evaluated. - Losing a sender in the merge. Compare the merged record against both originals.
- Fixing the apex but not a sending subdomain that has the same problem.
- Adding the include for a vendor that bounces with its own domain. It costs lookups and does nothing for DMARC (SPF include vs DKIM from the vendor).
When you add the next vendor, follow How to add a third-party sender without breaking DMARC, and see Common SPF mistakes for other common SPF slips.
Free DMARC account
Not sure which sender is failing?
Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.
- Every sending source in one dashboard
- SPF, DKIM and alignment results per sender
- No XML files to read
FAQ
Can I have two SPF records?
No, not at the same name. Two v=spf1 records make SPF return permerror. Merge them into one.
Is a TXT verification record a second SPF record?
No. Only TXT records starting with v=spf1 count.
My record is split into two quoted strings. Is that two records?
No. It's one record, and the strings are joined before evaluation.
Can a subdomain have its own SPF record?
Yes. Each name can have exactly one.