Skip to content
fixGuide

Multiple SPF records: why two v=spf1 TXT records is a permerror

RFC 7208 allows one v=spf1 TXT record per domain. Two or more is a permerror, and receivers do not merge them. Here is how extras appear, how to check, and how to combine includes.

You searched for

“multiple spf records”

Last verified: Oct 21, 2026Published: Oct 21, 2026

Two v=spf1 TXT records is not a more complete policy. RFC 7208 says a domain MUST have at most one SPF record. When a receiver finds two or more, evaluation ends in a permerror. Receivers do not merge the records. Every include: in both of them is ignored, so none of your legitimate senders are authorized.

That is a different permerror from too many DNS lookups. The lookup cap is about how deep one record goes. Multiple records is about publishing more than one record at all. You can hit either, and a sloppy merge can produce both.

For how SPF relates to DKIM and DMARC, see SPF vs DKIM vs DMARC.

Why receivers refuse to merge them

SPF asks whether this connecting IP may use this domain in the SMTP envelope (Return-Path / Mail-From). The receiver looks up TXT on that envelope domain, discards values that do not start with v=spf1, and needs exactly one remaining record.

  • Zero v=spf1 records: none (no policy).
  • One v=spf1 record: evaluate its mechanisms.
  • Two or more v=spf1 records: permerror.

A permerror is a permanent error in the published data. Soft fail (~all) and hard fail (-all) are policy choices inside a valid record. Permerror means the record set is unusable. DMARC then treats SPF as not having helped the message.

Other TXT records on the same name are normal. Domain-control tokens and site verification can sit next to SPF. They are ignored as long as they do not start with v=spf1.

How a second record usually appears

Almost nobody types two SPF records on purpose. The usual path is two setup wizards, each told to “add a TXT record,” and a DNS UI whose default button is Add, not Edit.

  1. Google Workspace (or Microsoft 365) walks you through publishing something like v=spf1 include:_spf.google.com ~all.
  2. An ESP, CRM, or billing tool later asks for its own TXT, often v=spf1 include:sendgrid.net ~all.
  3. You create a second TXT at the apex because that is what the wizard’s screenshot shows.

Each wizard is locally correct. Together they are invalid. The same thing happens when someone pastes a complete v=spf1 ... all line into a new record instead of inserting one include: into the line that already exists.

Less often, a bounce subdomain used as the envelope gets its own extra v=spf1 pair while the apex looks fine. SPF is checked on the envelope domain of that message, so look where mail actually bounces.

How to check for multiple SPF records

You are counting records, not mechanisms.

  1. Identify the envelope domain. Open a real sent message and read Return-Path / Mail-From. For many orgs that is the apex (yourdomain.com). If it is a subdomain, check that name too.
  2. List TXT records on that name in the DNS host. Count how many values start with v=spf1. The correct count is one.
  3. Confirm with a live lookup, not only the registrar’s editor. The free SPF checker reads published DNS and flags more than one v=spf1 record.

A common false alarm: one TXT whose value is stored as several quoted character-strings ("v=spf1 include:_spf.google.com" " include:sendgrid.net ~all"). RFC 7208 concatenates those strings. That is still one record. Two rows in the DNS UI, each starting with v=spf1, is the bug. Trust the record list, not a preview that joins everything into one blob.

dig TXT yourdomain.com prints one answer per record. Two answers that both begin v=spf1 is the permerror. Wait out TTL after edits before you treat the answer as final.

How to merge them into one record

The fix is one v=spf1 that lists every sender you still use, then a single all mechanism. Do not leave a second record “as backup.”

  1. Copy the mechanisms from every existing v=spf1 record: include:, ip4:, ip6:, and any a / mx you actually need.
  2. Drop duplicates. Drop vendors you no longer send through.
  3. Publish one TXT on the envelope domain, in this shape:
v=spf1 include:_spf.google.com include:sendgrid.net ~all
  1. Delete every other TXT whose value starts with v=spf1.
  2. Wait for TTL, then re-check until only one v=spf1 remains.
# Before: two TXT records on the apex (invalid)
v=spf1 include:_spf.google.com ~all
v=spf1 include:sendgrid.net ~all

# After: one TXT record (valid)
v=spf1 include:_spf.google.com include:sendgrid.net ~all

Keep a single all at the end. If one leftover used ~all and the other used -all, pick one qualifier. ~all (soft fail) is the usual choice while you are still discovering senders. -all (fail) is the usual choice once every real sender is listed.

Use the include hostname the vendor documents today. Some tools still show a legacy include next to a current one. Putting both in wastes lookups and can still miss the host they actually send from.

Do not create a second record

When the next ESP’s docs say “add this TXT record,” open the existing v=spf1 and add their include: there. A new row with its own v=spf1 ... all recreates the permerror you just fixed. If the DNS host makes a long TXT awkward to edit, that is still an edit of one record.

Do not SPF-include a forwarder

Forwarding happens after the original delivery. The forwarder’s IP is not a mail system you operate. Putting that domain (or IPs from a DMARC report that are Gmail, Outlook, or a list server) into SPF authorizes that infrastructure to send as you.

SPF is supposed to fail on many forwards. An aligned DKIM signature can still satisfy DMARC when the IP check cannot. If reports show forwarded mail, fix DKIM alignment for your From domain rather than growing SPF to chase recipient-side hops.

The 10-lookup limit still applies after a merge

Each include:, a, mx, ptr, and exists costs a DNS lookup, including nested includes inside a vendor’s record. ip4:, ip6:, and all do not. Stitching two small records together can push the combined tree over RFC 7208’s cap of 10. Past that, receivers permerror the merged record too.

After the extra TXT is gone, count lookups on the remaining record. If you are over 10, trim unused includes before you flatten anything. The steps live in SPF permerror: too many DNS lookups.

Confirm it is fixed

Run the SPF checker against the envelope domain. You want exactly one v=spf1 record, the senders you intend, one all mechanism, and a lookup count at or under 10. Send a test and confirm the Return-Path you checked is still the one mail uses. If a subdomain sends with its own envelope, it needs its own single record; merging the apex does not cover it.

Confirm the fix

Run the free check to confirm

Applied the fix above? Run the freeSPF Checkeragainst your domain and see your grade update in real time.

Run the free check: SPF Checker

Common follow-up questions

How many SPF records can a domain have?

At most one TXT record whose value starts with v=spf1, on the envelope domain SPF evaluates. Other TXT records (site verification, BIMI, and similar) do not count. A second v=spf1 record is a permerror under RFC 7208.

Do mailbox providers merge two SPF records into one policy?

No. Receivers must not concatenate or union multiple v=spf1 records. If more than one qualifies, evaluation stops with a permanent error, so none of the includes in either record authorize anyone.

Is a long SPF TXT split into quoted chunks the same as two records?

No. DNS TXT values are made of character-strings. Several quoted chunks inside a single TXT record are concatenated and are valid. Two separate TXT records that each start with v=spf1 are the failure. Count records in the DNS host's record list, not a preview that joins strings.

Should I add a second SPF record when a new ESP asks me to?

No. Open the existing v=spf1 record and add that provider's include: (or ip4:/ip6:) there, then keep a single all mechanism at the end. Creating another TXT with its own v=spf1 is how most duplicate records start.

Can I SPF-include a forwarder so forwarded mail still passes?

No. A forwarder's IP is not a sender you operate. Including it authorizes that infrastructure to send as your domain. Forwarding is expected to fail SPF; an aligned DKIM signature is what can still satisfy DMARC after a forward.

Where do I look up the SPF record: apex or somewhere else?

Look up TXT on the envelope-from (Return-Path / Mail-From) domain of a real message. For many domains that is the apex. If mail bounces through a subdomain, that subdomain needs its own record. Checking the wrong name will hide a duplicate or a miss.

After I merge, why might SPF still return permerror?

The usual leftover is a second v=spf1 TXT that was not deleted, or the merged record now triggers more than 10 DNS lookups. Recheck live DNS after TTL, confirm exactly one v=spf1, then count lookups. See the too-many-lookups guide if the count is over 10.