You added a new provider’s SPF record next to the old one, and now receivers return permerror for every message, from both providers. Two SPF records on one name make SPF fail for every sender.

The short answer

A domain name can have only one SPF record. When a receiver finds two or more TXT records that start with v=spf1 on the same name, the SPF result is permerror, for every message and every sender [1]. Merge them into one record: one v=spf1, every mechanism from both, one all at the end.

What it looks like

In the headers of a delivered message, written by the receiving server in the Authentication-Results format of RFC 8601 [3]:

Authentication-Results: mx.example.net;
       spf=permerror smtp.mailfrom=example.com

From the Python SPF library pyspf, whose source builds the message from 'SPF Permanent Error: ' and 'Two or more type TXT spf records found.' [5]:

SPF Permanent Error: Two or more type TXT spf records found.
Exact text from source [5]

From Gmail, when you send in bulk and your mail fails SPF [6]:

550 5.7.27 This message was blocked because it didn't pass SPF authentication. Gmail requires bulk email senders to authenticate their email with SPF. …
Exact text from source [6]

Why two SPF records break both

A receiver asks DNS for the TXT records on your domain, keeps the ones that start with exactly v=spf1, and throws the rest away [1]. If one is left, it evaluates it. If more than one is left, it stops and returns permerror without reading either [1]. RFC 7208 states the rule in section 3, “multiple SPF records are not permitted for the same owner name”, and again in section 3.2 [1]. Microsoft gives the same rule for Microsoft 365 domains: “only one SPF record is allowed per domain or subdomain” [4].

Nothing in the result tells the receiver which provider was meant, so mail from both fails. A permerror is no SPF pass, and DMARC only uses an SPF pass [2]. Until you merge, your mail passes DMARC only through an aligned DKIM signature [2].

How to find a duplicate SPF record

On macOS or Linux, list every TXT record on the name and count the ones that start with v=spf1:

dig +short TXT example.com
dig +short TXT example.com | grep -c 'v=spf1'

A count of 2 or more is the problem. On Windows, nslookup -type=TXT example.com returns the same records.

A typical result after adding Zendesk to a domain that uses Google Workspace, each with the record its setup guide shows [8][9]:

example.com.  TXT  "v=spf1 include:_spf.google.com ~all"
example.com.  TXT  "v=spf1 include:mail.zendesk.com -all"

Repeat the check on every name that sends mail, such as bounce.example.com. Each name has its own SPF record [1].

How to merge two SPF records

  1. Start a single record with v=spf1.
  2. Copy every mechanism from both records, in the order you want them tested: ip4:, ip6:, include:, a, mx. Drop exact duplicates.
  3. End with one all. If one record ends in ~all (softfail) and the other in -all (fail), pick one. Google recommends ~all [8]. RFC 9989 warns that -all can get a message rejected on SPF alone, before DMARC sees a valid DKIM signature [2].
  4. Publish the merged record and delete the old ones in the same change.

The example above, merged:

example.com.  TXT  "v=spf1 include:_spf.google.com include:mail.zendesk.com ~all"

This is the record Google lists for Google Workspace with Zendesk [8]. Zendesk shows the same merge, ending in -all [9]. It costs 2 DNS lookups, one per include, measured on 18 November 2026 [10]. Providers ask for this merge themselves: Cloudflare’s Email Routing setup says “If you have existing SPF records, merge them” and shows a record with both its include and Google’s [7].

After merging, count the lookups. More than 10 is a new permerror of its own: see SPF too many DNS lookups.

What is not a duplicate

  • One record split into several strings. "v=spf1 include:_spf.google.com " "include:mail.zendesk.com ~all" is one TXT record. Receivers join the strings without adding spaces [1]. Mind the space at the end of the first string.
  • Other TXT records on the same name. Site verification tokens and other TXT values do not start with v=spf1, and receivers ignore them for SPF [1].
  • SPF records on other names. bounce.example.com and example.com each get one record, and they never conflict [1].
  • The DMARC record. It lives at _dmarc.example.com and starts with v=DMARC1 [2].

Mistakes to avoid

  • Pasting one record after the other in the same TXT value. In v=spf1 include:_spf.google.com ~all v=spf1 include:mail.zendesk.com -all, receivers stop at the first all and ignore every mechanism after it [1]. Zendesk’s include is never tested.
  • Leaving two all terms. The same rule applies: the first all ends the record [1]. Put ~all or -all once, at the end.
  • Keeping redirect= from both records. redirect may appear only once in a record, or the result is permerror [1]. A record that ends in all ignores redirect anyway [1].
  • Publishing SPF as DNS record type “SPF”. Some DNS panels still offer it. SPF lives in TXT records only, and receivers query TXT only [1].
  • Changing ~all to -all while merging. A receiver that checks SPF before DMARC can reject a message on a -all fail alone [2]. Change one thing at a time.

If you are merging because you are moving to a new provider, switching email providers without losing mail covers the order of the DNS changes. Once SPF passes again, moving DMARC from p=none to p=reject is what stops forged mail. More SPF problems are on the SPF record page.

Check for duplicate SPF records

The SPF checker reads every TXT record on the name in your browser, flags a second v=spf1 record and explains the fix.

Check for duplicate SPF records

Runs in your browser. Your domain is not sent to this site or stored.

See it on a test domain

Check these names under badmail.dev to see this in a result, without checking your own domain.

All the test domains

Sources

  1. 1RFC 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1. Sections 3, 3.1, 3.2, 3.3, 4.4, 4.5, 5.1, 6, 8.7rfc-editor.org, IETF. Checked .
  2. 2RFC 9989, Domain-Based Message Authentication, Reporting, and Conformance (DMARC). Sections 4.4.1, 4.7, 4.10.2, 7.1rfc-editor.org, IETF. Checked .
  3. 3RFC 8601, Message Header Field for Indicating Message Authentication Status. Section 2.7.2rfc-editor.org, IETF. Checked .
  4. 4Set up SPF to identify valid email sources for your custom cloud domainslearn.microsoft.com, Microsoft. Checked .
  5. 5pyspf source code, spf.py (strings ‘SPF Permanent Error: ’ and ‘Two or more type TXT spf records found.’; latest PyPI release 2.0.14)raw.githubusercontent.com, pyspf project. Checked .
  6. 6Gmail SMTP errors and codesknowledge.workspace.google.com, Google. Checked .
  7. 7Domain configuration (Email Routing records, existing SPF records)developers.cloudflare.com, Cloudflare. Checked .
  8. 8Set up SPFknowledge.workspace.google.com, Google. Checked .
  9. 9Allowing Zendesk to send email on behalf of your email domainsupport.zendesk.com, Zendesk. Checked .
  10. 10Measurement: dig 9.10.6 against 1.1.1.1, +short TXT on _spf.google.com and mail.zendesk.com, n = 2 records, neither with a further lookup term, 18 November 2026 at 12:34 CET, counted with the rules of RFC 7208 section 4.6.4rfc-editor.org, Measurement. Checked .