Opens in a new tab

Multiple SPF records: why two records make SPF fail

A domain may publish exactly one SPF record. With two TXT records starting v=spf1, receivers cannot tell which one you meant, and the result is permerror for every message.

Syntaxtwo TXT records starting v=spf1
Resultpermerror
FixMerge into one record
Defined inRFC 7208 §4.5

What it does

It usually happens when a second service’s setup guide says “add this SPF record”, and it is added next to the existing one instead of into it.

A long record split into several quoted strings inside one TXT record is not the same thing — that is one record, and receivers join the strings together. The problem is two separate TXT records that each start with v=spf1.

Examples

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

Two records: both fail.

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

The same senders, merged into one record.

See what your own SPF record says

Every term of your published record, read and explained — including this one.

Common mistakes

  • Merging by adding a second v=spf1 inside the first record, or keeping two all terms.

What we recommend

Keep one v=spf1 at the start, every include and ip term in the middle, and one all at the end.

Build a merged SPF record →

Sources

Checked on 25 September 2026 against these official sources:

Know when your records change

Add your domain and we monitor its SPF, DKIM and DMARC every day, read the DMARC reports receivers send you, and email you when a record changes or a sender starts failing. Free for your first domain.

Create a free account