Multiple SPF Records: Why They Break Email (and How to Fix It)

TL;DR: Your domain may only have one SPF record. If two or more v=spf1 TXT records exist, SPF evaluation returns PermError and most receivers treat it as a fail — so your mail gets junked or rejected. The fix is to merge them into a single SPF record. Scan your domain free to see if you have duplicates.

Why two SPF records break email

The SPF specification (RFC 7208 §3.2) is explicit: a domain must publish exactly one record starting with v=spf1. When a receiving server finds two, it can't decide which to trust, so it returns a permanent error. Combined with a DMARC policy at quarantine or reject, that error can quietly send your legitimate mail to spam.

Why it happens

• You added a new email tool (a CRM, newsletter or helpdesk) and it told you to "add this SPF record" — so you created a second one instead of editing the existing one.
• A migration or template left an old SPF record behind.
• Two teams each published their own.

It's one of the most common SPF mistakes, and it's invisible until your mail starts landing in spam.

How to check for duplicate SPF records

Look up the TXT records on your domain and count how many start with v=spf1 — more than one is the problem. The quickest way is a free scan: it flags duplicate SPF records instantly. Scan your domain and you'll see it in your grade.

How to merge them into one record

1. List every SPF record you currently have and note all the mechanisms (the include:, ip4:, a and mx entries).
2. Combine all the unique mechanisms into a single v=spf1 record, ending with one ~all or -all.
3. Delete the other SPF record(s) so only one remains.
4. Watch the 10-lookup limit — merging can push you over it; remove unused includes if so.

For example, two records like v=spf1 include:_spf.google.com ~all and v=spf1 include:sendgrid.net ~all become one:

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

FAQ

Can I keep two SPF records if they don't overlap?

No. The rule is one v=spf1 record per domain, regardless of content. Two always causes a PermError.

Do multiple TXT records break SPF, or only multiple SPF records?

Only multiple SPF (v=spf1) records. You can have other TXT records (DKIM, verification, DMARC is on a subdomain) — just not two SPF ones.

How fast does the fix take effect?

As soon as DNS propagates — usually minutes to a couple of hours. Re-scan to confirm only one SPF record remains.

Don't want to risk breaking your mail flow? Scan your domain, then reply to your report — we're developers and we'll merge your SPF records into one clean, valid record for you.