Email authentication

SPF Merge Tool

Merge multiple SPF records into one valid, de-duplicated record. Fix the "two SPF records" permerror and combine providers — free, with instant DNS-lookup checks.

Merge SPF records

Paste two or more SPF records, one per line. The merged record updates instantly.

What this SPF merge tool does

Combines multiple SPF records into one RFC-valid record

De-duplicates repeated include, ip4, ip6 and other mechanisms

Resolves conflicting -all / ~all policies safely

Counts direct DNS lookups against the 10-lookup limit

Drops dangerous +all and warns you about it

One-click copy, ready to paste as a single TXT record

Common use cases

1Fixing a domain that wrongly has two SPF records
2Combining SPF from several email providers into one
3Consolidating records after a migration or acquisition
4Removing duplicate mechanisms that bloat your record
5Standardising SPF across multiple sending services
6Preparing a single clean record before publishing

About merging SPF records

A domain may publish only one SPF record. If two v=spf1 records exist, receivers return a permerror and SPF stops working — a common mistake when a second email provider adds its own record instead of extending the existing one. Merging combines every authorized sender into a single valid record.

When you merge, duplicate mechanisms are removed and the strictest-but-safe all policy is chosen. Remember there can still be only one all mechanism, and the combined record must stay within the 10-lookup limit — check the merged result before publishing it as your single TXT record.

More Free Tools Where This Came From

This utility is one of dozens of free, no-login tools for DNS, email, SEO and developers — all instant and private.

See All Tools Talk to Our Team

HostCloud.in · Pune, India · Serving 34,987+ Websites Since 2020

FREQUENTLY ASKED QUESTIONS

Got Questions? We Have Answers.

Why can I only have one SPF record?

RFC 7208 permits exactly one v=spf1 record per domain. If a receiver finds two, it returns a permerror and ignores SPF entirely — so multiple records must be merged into one.

How does merging handle duplicate mechanisms?

Identical mechanisms (the same include, ip4, ip6, a or mx) are collapsed to a single entry, keeping the record short and within the DNS lookup limit.

What happens when records have different -all policies?

The tool keeps the least strict policy so no legitimate sender is newly rejected, and warns you about the conflict so you can set your intended policy deliberately.

Does merging count my DNS lookups?

Yes. It counts the direct DNS-querying mechanisms in the merged record. Because includes can nest, run the merged record through the SPF Lookup Counter for the full recursive total.

Will the merged record drop a +all?

Yes. "+all" authorizes every server on the internet to send as your domain, disabling SPF. The tool removes it from the merge and flags a warning.

How do I publish the merged record?

Delete your existing SPF TXT records and publish the single merged record as one TXT record on your root domain. Verify it afterwards with an SPF checker.