Call (703) Book ↗
On this page
SPF · RFC 7208 Sec 4.5

Multiple SPF Records & SPF PermError

Emails bouncing with SPF PermError? You cannot publish two v=spf1 records. Step-by-step RFC 7208 merge guide to combine includes into one valid record.

Emails Currently Bouncing?

Jump straight to our Free Email Deliverability Scanner to inspect your live SPF lookup count and check for duplicate v=spf1 records, or follow the step-by-step RFC 7208 merge guide below.

The problem: why two SPF records break email immediately

"Multiple SPF Records" is the single most common DNS failure causing an SPF PermError. Receiving mail servers immediately fail authentication if your domain returns more than one TXT record starting with v=spf1, or if resolving your record exceeds RFC 7208's strict 10-DNS-lookup limit.

RFC 7208 Section 4.5: the multiple-record prohibition

When you connect a new cloud platform (Microsoft 365, Google Workspace, Mailchimp, QuickBooks, or a CRM), its onboarding wizard says "Add this TXT record to your DNS." What it really means is: "Add our include: mechanism inside your existing SPF record."

Creating a second TXT record beginning with v=spf1 directly violates RFC 7208 Section 4.5. A domain MUST NOT publish multiple SPF records. Receiving servers do not merge them—they discard both records and return a fatal PermError.

Unpredictable Deliverability Failures

Multiple SPF records cause sporadic, hard-to-diagnose failures: some mail gateways hard-bounce messages with 550 5.7.1 SPF PermError while others silently route legitimate business invoices straight to spam.

Real-world troubleshooting example: broken vs. merged zone

Here is a typical small-business DNS zone we see every week after an office adds Microsoft 365, Mailchimp, and QuickBooks Online over time without merging their TXT entries:

BROKEN DNS ZONE (3 SEPARATE v=spf1 RECORDS = INSTANT PERMERROR)
; WRONG — Three separate TXT records at root (@)
@  3600  IN  TXT  "v=spf1 include:spf.protection.outlook.com -all"
@  3600  IN  TXT  "v=spf1 include:servers.mcsv.net ~all"
@  3600  IN  TXT  "v=spf1 include:secureserver.net ~all"

In the example above, secureserver.net was a leftover default record created automatically by the domain registrar years earlier. After confirming the company no longer sends mail through legacy registrar webmail, all active senders merge into strictly one TXT record:

FIXED DNS ZONE (SINGLE MERGED SPF RECORD — 2 LOOKUPS TOTAL)
; CORRECT — One single v=spf1 TXT record at root (@)
@  300   IN  TXT  "v=spf1 include:spf.protection.outlook.com include:servers.mcsv.net -all"

RFC 7208 Section 4.6.4: the 10-DNS-lookup limit

Even with a single SPF record, exceeding 10 recursive DNS lookups (RFC 7208 Section 4.6.4) also triggers an instant PermError. Every include, a, mx, ptr, exists, and redirect counts toward that ceiling—including nested lookups inside vendor records:

EXAMPLE MULTI-PROVIDER SPF RECORD (9 LOOKUPS)
v=spf1 a mx include:spf.protection.outlook.com include:sendgrid.net include:_spf.salesforce.com include:amazonses.com include:servers.mcsv.net ~all
  • a and mx consume 1 lookup each (2 lookups combined; RFC 7208 Section 4.6.4 also applies a separate 10-hostname per-mechanism A/AAAA resolution cap on mx, distinct from the 10-lookup limit).
  • include:sendgrid.net consumes 2 lookups (1 for the include + 1 nested include:ab.sendgrid.net).
  • include:_spf.salesforce.com consumes 2 lookups (1 for the include + 1 nested exists:%{i}._spf.mta.salesforce.com).
  • include:spf.protection.outlook.com, include:amazonses.com, and include:servers.mcsv.net currently consume 1 lookup each (3 lookups combined, with flat IP lists and 0 nested lookups).

That single merged record is already at 9 of 10 lookups. Adding one more multi-lookup vendor—or two single-lookup tools such as include:mail.zendesk.com (1) and include:spf.mandrillapp.com (1)—pushes the count to 11 > 10, triggering a fatal PermError across Gmail and Microsoft 365.

RFC 7208 Section 5.5: why the ptr mechanism must be removed

Under RFC 7208 Section 5.5, the ptr mechanism is formally discouraged. It slows DNS resolution, stresses root lookups, and is penalized by strict filters. Always replace ptr mechanisms with explicit ip4: / ip6: blocks or verified vendor includes.

Step-by-step merge guide: combining multiple SPF records

  1. List every existing v=spf1 TXT recordQuery your authoritative DNS zone and copy every TXT record beginning with v=spf1.
  2. Combine unique mechanisms into one stringMerge every legitimate include:, ip4:, and ip6: mechanism into a single line—dropping retired services you no longer send from.
  3. Enforce valid RFC syntaxStart once with v=spf1, place all authorized senders in the middle, and terminate once with -all (hard fail) or ~all (soft fail).
  4. Delete the duplicate TXT record(s)Remove all secondary SPF TXT entries so strictly one v=spf1 record remains at the root domain.
  5. Validate total nested lookup depthVerify the final record evaluates to ≤ 10 total DNS lookups using our Free Email Security Check.
CLEAN MERGED SINGLE SPF RECORD EXAMPLE (2 LOOKUPS)
v=spf1 ip4:192.0.2.1 include:_spf.google.com include:spf.protection.outlook.com -all

Provider-specific DNS merge notes

Platform / DNS HostWhere Duplicates Happen & How to Merge Cleanly
Cloudflare DNS Filter DNS → Records by Type TXT and search spf1. Edit the single root (@) record in place—Cloudflare automatically handles quotes and string splitting if a record exceeds 255 characters. Delete any second @ record beginning with v=spf1.
GoDaddy DNS GoDaddy routinely pre-populates v=spf1 include:secureserver.net -all on new domains. When admins follow Microsoft 365 or Google setup guides and click Add New Record, they accidentally publish a second SPF TXT entry. Delete secureserver.net if you do not use GoDaddy cPanel/webmail, and consolidate into one @ TXT record.
Microsoft 365 Microsoft's domain wizard displays a full standalone string (v=spf1 include:spf.protection.outlook.com -all). If an SPF record already exists, only insert include:spf.protection.outlook.com before the trailing ~all/-all.
Google Workspace Insert include:_spf.google.com into your single existing TXT record (currently 1 lookup, as Google serves a flattened IP list). Still avoid leaving both Microsoft and Google includes active after finishing a migration—retiring unused providers preserves lookup headroom and narrows who is authorized to send as your domain.

Verify your fix from the command line

After saving DNS (and waiting for your prior TTL to expire), confirm that public resolvers return strictly one line starting with v=spf1:

MACOS / LINUX (DIG) & WINDOWS (NSLOOKUP)
# macOS / Linux — should output EXACTLY ONE "v=spf1 ..." line
dig +short TXT yourdomain.com | grep -i "spf1"

# Windows PowerShell / Command Prompt
nslookup -type=txt yourdomain.com 1.1.1.1

Common merge pitfalls to avoid

  • Two all qualifiers in one record: Writing v=spf1 include:spf.protection.outlook.com -all include:servers.mcsv.net ~all breaks Mailchimp immediately—receiving servers stop reading at the first -all. Keep strictly one ~all or -all at the very end.
  • Splitting long records into two TXT rows: DNS TXT strings max out at 255 bytes per quoted chunk. If a valid merged record exceeds 255 characters, split it into two adjacent quoted segments inside one TXT record ("v=spf1 ..." " include:... -all"), never two separate TXT records.
  • Forgetting the old TTL window: If the deleted duplicate record had a 14400s (4-hour) or 86400s (24-hour) TTL, remote mail servers may cache the broken duplicate until that timer expires.

Alternative strategy: isolate senders on a subdomain

If your legitimate cloud tools still exceed 10 lookups, move marketing or automated app email onto a dedicated subdomain such as mail.yourdomain.com or notify.yourdomain.com. Because SPF evaluates per sending domain, each subdomain gets its own clean 10-lookup budget and protects your root corporate reputation.

Want Our Engineers to Fix Your DNS Cleanly?

One stray character in SPF or DMARC can bounce every invoice your company sends. Let Enuclea audit your senders, flatten SPF safely, align 2048-bit DKIM, and configure DMARC cleanly starting at $250 flat. Test your domain free, book a 15-minute call (24-hr notice) ↗, or call (703) 239-4620.