A DNS name can publish one SPF record. If two TXT records on the same name both start with v=spf1, receivers do not pick one and do not merge them. SPF returns a permerror, which DMARC treats as a failed SPF check. The fix is always the same: one record, with every sender you still use inside it.
How a second record appears
It usually happens during a setup. A provider's instructions say "add this TXT record", and the new value goes in next to the existing one instead of replacing it. Google Workspace, Microsoft 365, a newsletter tool and a help desk can each leave one behind. Some DNS hosts also keep an old record when you add a new one with the same name.
Find every SPF record on the name
Look the domain up with the SPF checker. It reports a second v=spf1 record as its own error. From a terminal:
dig +short TXT example.com | grep -i "v=spf1"Two lines of output means two records. One long record that your DNS host split into several quoted strings is still one record: the strings are joined before SPF reads them. That is not a duplicate.
Merge two records into one
Say the name has these two records:
v=spf1 include:_spf.google.com ~all
v=spf1 include:spf.example-newsletter.com ~allKeep one v=spf1 at the start, put every include, ip4 and ip6 in the middle, and end with a single all:
v=spf1 include:_spf.google.com include:spf.example-newsletter.com ~allThen delete the second record. Before you merge, drop any include for a service that no longer sends as the domain. Each include costs DNS lookups, and SPF allows 10 per check. The lookup limit guide covers what happens past that.
If the two records end differently
One record may end in ~all and the other in -all. A merged record can only have one. Use ~all while you are still confirming every sender, and move to -all once DMARC reports show nothing legitimate is failing. Never merge to +all: that lets any server pass SPF as your domain.
Records on different names are fine
The limit is one SPF record per name, not per domain. A record on example.com and another on mail.example.com or bounce.example.com do not conflict. SPF checks the envelope sender, the return-path domain, not the From address people see. SendPanda sends with a return-path subdomain, so its SPF record goes on the name the domain screen shows and does not need to be merged into your root record. The domain setup guide has the details.
Check it again
After the change, look the name up again. You should see one record, no duplicate error, and a lookup count under 10. DNS caches can serve the old pair for as long as their TTL, so a receiver may still see two records for a short time. SPF record syntax explains each term if you want to read the merged record line by line.
Next steps
- Quickstart for the full first-send walkthrough.
- Verify webhooks to learn when an email is delivered or bounces.
- Pricing: 3,000 emails a month free, no card.