Skip to content

Multiple SPF records found

A name with two SPF records gets permerror, so SPF fails for everything that depends on it until you merge them into one record.

Last updated:

What the checker reports

Critical spf.multiple_records

More than one SPF record

A name may have only one v=spf1 TXT record. Here the domain, or a domain its record points to, has two or more, so receivers return permerror and SPF fails for everything that depends on that record.

How to fix: Merge the records into one: keep a single v=spf1 at the start, combine the mechanisms, keep one all at the end, and delete the other records.

What this error means #

A domain name may have only one SPF record. When a receiving mail server looks up the TXT records at your name, it throws away every record that doesn’t begin with exactly v=spf1, then expects one to be left. If two or more are left, it doesn’t pick one. It returns permerror, and SPF fails for the domain.

The standard puts the rule on the publisher too: a domain name must not have multiple records that would cause an authorization check to select more than one (RFC 7208 §3.2).

A few details decide what counts as a second record:

  • Only TXT records are read. SPF’s old dedicated record type, code 99, is no longer used for SPF version 1, and a check asks for type TXT only (RFC 7208 §14.1, §4.4). A leftover type 99 record isn’t a duplicate, but it doesn’t help either.
  • The version section has to be exactly v=spf1. A record starting with v=spf10 is discarded, and so is any TXT record that doesn’t start with v=spf1 at all, so other TXT records at the name don’t count.
  • One record split into several quoted strings is still one record, because the strings are joined without spaces (RFC 7208 §3.3). Two separate records that both start with v=spf1 are two records, whatever else they hold.

The same rule applies wherever a receiver looks. If your record has include:spf.mailer.example and that name publishes two SPF records, the nested check returns permerror, and an include whose target returns permerror returns permerror too (RFC 7208 §5.2). The failure then shows up on your domain, but only that service can fix it, so report it to them.

When a service’s setup guide asks you to publish an SPF record and you already have one, don’t add a second record. Add the service’s include to the one you have.

How receivers treat it #

Standard: RFC 7208 §4.5

If the resultant record set includes no records, check_host() produces the “none” result. If the resultant record set includes more than one record, check_host() produces the “permerror” result.

A permerror means the published records couldn’t be correctly interpreted, and RFC 7208 §2.6.7 says it definitely requires DNS operator intervention. What a receiver does next is its own local policy (§4.2). If it rejects the message during the SMTP conversation, §8.7 says it should use reply code 550 with, if supported, the enhanced status code 5.5.2.

DMARC gets nothing from it. RFC 9989, which replaced RFC 7489 in May 2026, only treats a domain as an SPF-authenticated identifier when SPF passes (§4.10.2), and a permerror isn’t a pass. Your mail can still pass DMARC through an aligned DKIM signature (§5.3.5).

Broken and fixed record #

two-records.zone
example.com.  TXT  "v=spf1 include:spf.mailer.example ~all"
example.com.  TXT  "v=spf1 ip4:192.0.2.25 include:spf.helpdesk.example -all"

Each record is fine alone. Published together at the same name, they make one permerror. The fix is one record that holds every term from both, with a single v=spf1 at the start and a single all at the end:

one-record.zone
example.com.  TXT  "v=spf1 ip4:192.0.2.25 include:spf.mailer.example include:spf.helpdesk.example ~all"

Merging means reading the records term by term. Every term except all moves across, and redirect and exp may each appear only once (RFC 7208 §6). The all is the one term you choose rather than copy. This example keeps ~all from the first record, which makes a server you haven’t listed softfail. The second record’s -all would make it fail outright (RFC 7208 §4.6.2). Mechanisms written after all are ignored (§5.1), so a stray all in the middle would hide everything behind it.

How to fix it #

  1. List every TXT record at the name, in your DNS host’s control panel or with any DNS lookup tool, and note each one that starts with v=spf1.
  2. Write one record that starts with v=spf1 and holds the terms from all of them. Keep each include once, because every include counts toward the limit of 10 DNS lookups (RFC 7208 §4.6.4), and the merged record has to stay under it.
  3. End the record with one all, and choose ~all or -all on purpose instead of keeping both.
  4. Delete the other SPF records, so only one v=spf1 record is left at that name.
  5. If the same error shows up on a name your record includes, tell the service that owns that name.
  6. Run the SPF Record Checker on your domain and confirm it finds one record.

Check your domain

Records look right? Check the list next.

Kavik.email checks every address on your list, so what you send reaches real inboxes.