Skip to content
DMARC Pulse

Email errors

Multiple SPF Records: Why It Fails and How to Merge Them

Multiple SPF records on one DNS name cause SPF permerror. Merge them into a single v=spf1 record with multiple includes, step by step.

What this means

Multiple SPF records means one DNS name publishes two or more TXT records that begin with v=spf1. SPF is the DNS record that lists which servers may send mail for a domain. RFC 7208 forbids this and requires the result permerror, meaning the published records could not be correctly interpreted. To authorize another sender, add it to the record you already have.

Every message checked against that name gets permerror. In message headers, look for spf=permerror.

Correctly listed senders get permerror too, and each receiver decides whether to reject or deliver. DMARC, the policy check built on SPF and DKIM signatures, can pass only through a valid DKIM signature aligned with the From domain.

Why it happens

A second record appears when someone creates a new v=spf1 entry instead of editing the existing one, for example when adding a mail service or splitting a long record. Other TXT records do not count, because receivers discard anything not beginning with v=spf1.

If only some sources get permerror, check the include targets. A target with duplicates returns permerror once the check reaches it. Too many DNS lookups can do the same.

How to fix it

  1. Find the name that was checked. In the headers of an affected message, read smtp.mailfrom= beside spf=permerror. That envelope sender, the address used during delivery, can differ from the From address. If a vendor owns it, ask the vendor to fix it.

  2. List every v=spf1 record on that name. Run nslookup -type=TXT example.com 1.1.1.1 to see them all. The SPF checker counts them but shows just one. If you find only one, repeat for each include target and report duplicates to its owner.

  3. Collect every source. Note each term between v=spf1 and all in all the records. Caution: a source you leave out will not pass SPF after the merge, so compare your list with recent DMARC aggregate reports first.

  4. Build one record. Use one v=spf1, every source once and one all at the end. Mechanisms after all are never tested, so two records pasted together lose the second half. Change any redirect= to include:, because all cancels it. List only services you use. Google documents this form for Google Workspace plus Microsoft 365:

    TXT
    v=spf1 include:_spf.google.com include:spf.protection.outlook.com ~all
  5. Choose the ending. Google recommends ~all. Microsoft recommends -all for Microsoft 365 domains with DKIM and DMARC. Start with ~all, even if the old records used -all. Caution: receivers may reject unlisted sources under -all, so move to it only after reports show every source passing.

  6. Publish in this order. At your DNS host, edit one record to hold the merged value, then delete the others. Caution: delete a record only after its sources are in the merged one.

How to add multiple SPF records for different services

New senders go in the same record, and an SPF record with multiple includes is valid. Give each service its own include: before all, with a space between terms. Use the value from the service's documentation. An -all inside an included record does not end the check.

Each include uses at least one of the 10 DNS lookups SPF allows, and includes nested inside it count too. Past 10, the result is permerror again, so read the count in the SPF checker. If you run out, Microsoft suggests moving non-Microsoft services to a subdomain with its own SPF record and lookup budget. Caution: keep the service's include in the main record until a test from the subdomain shows spf=pass.

Confirm the fix

  1. Google says SPF fixes can take 24 to 48 hours to take effect globally.
  2. Run the checker again. You want exactly one v=spf1 record on the name and 10 lookups or fewer.
  3. Send a test from each service to a mailbox you control. Each must show spf=pass in the Authentication-Results header.
  4. Read the next DMARC aggregate reports. Where they list an SPF result for those sources, it should change from permerror to pass.

Check it now

Validate SPF and count DNS lookups

Frequently asked questions

Can a domain have multiple SPF records?
No. RFC 7208 says a domain name must not have multiple records that would make a check select more than one, and Google and Microsoft also allow only one per domain. When more than one v=spf1 record comes back, the result is permerror. A receiver following the standard does not use the first one or combine them. A subdomain is a separate name, so it can have one record of its own.
How do I add multiple SPF records for several email services?
Keep one record and give each service its own include: term before the all term. Separate terms with a space. Take each value from that service's documentation. Google documents this form for Google Workspace plus Microsoft 365: v=spf1 include:_spf.google.com include:spf.protection.outlook.com ~all. List only services you use.
How many includes can an SPF record have?
RFC 7208 allows 10 terms that query DNS during one SPF check: include, a, mx, ptr, exists and redirect. Includes nested inside another include count too, so Microsoft notes that fewer than 10 include terms does not guarantee fewer than 10 lookups. Google's setup page states it as up to 10 include: tags. Past the limit, the result is permerror.
Do other TXT records or a record split into quoted strings count as extra SPF records?
No. Receivers discard every TXT record that does not begin with v=spf1 before counting, so domain verification entries can stay, although they add to the size of the DNS answer. One TXT record can also hold several strings, and receivers join them without adding spaces. Keep the space between two terms inside one of the strings, or the terms run together.
Will my mail bounce because of multiple SPF records?
That depends on the receiver. Multiple records return permerror, and how receivers handle permerror is local policy, so a message can be rejected or delivered. Codes and wording vary by server: Microsoft documents 550 5.7.23 for a missing or misconfigured SPF record. Google warns that the mail might end up in the spam folder.

Sources consulted

RFC 7208 §2.6.7 Permerror
checked 2026-11-08
RFC 7208 §3 SPF Records
checked 2026-11-08
RFC 7208 §3.4 Record Size
checked 2026-11-08
RFC 7208 §4.6.2 Mechanisms
checked 2026-11-08
RFC 7208 §5.1 all
checked 2026-11-08
RFC 7208 §5.2 include
checked 2026-11-08
RFC 7208 §8.7 Permerror
checked 2026-11-08
RFC 8601 §2.7.2 SPF results
checked 2026-11-08

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.