Free tools · Email domain setup
Multiple SPF Records: How to Review and Fix Them
Two separate SPF policies at the same DNS name create an SPF configuration error. Other TXT records can stay. First identify which records start with v=spf1, then review the senders they authorise.
Real public DNS lookup. No signup, mailbox connection or API key needed.
Check your published SPF record
Enter your own public domain. The illustrated examples below are not preloaded and no lookup runs until you submit.
Look up your public SPF record.
Enter your domain to see the published record and any issues found. Results appear here after a real DNS lookup.
SPF record generator
Create a TXT record from the settings you choose. This builder runs in your browser and produces text for you to review. It does not update DNS.
Your TXT record
Add the settings you intend to publish, then generate the text. Compare it with your existing record before making changes with your DNS provider.
What to do next
1. Find the separate policies
Run the checker for the sending domain. Count separate TXT records beginning with v=spf1. A verification token or another TXT record is not an extra SPF policy.
2. Confirm the required senders
Check both policies against the services that send for this exact domain. Use each provider's current instructions; do not assume every old include is still needed.
3. Prepare one reviewed policy
Combine the confirmed mechanisms into one policy with one version marker and an appropriate final all mechanism. Simply pasting two whole records together does not create a valid policy.
4. Replace the duplicates in DNS
Have the domain administrator publish the reviewed single policy, preserving unrelated TXT records. Check the lookup limit and test mail from all authorised services after the change.
Two separate policies at one name
example.com TXT: v=spf1 include:mail-a.example.com ~all example.com TXT: v=spf1 include:mail-b.example.com ~all
This fictional configuration has two SPF policies. It demonstrates the error, not a ready-made replacement. The correct combined policy depends on which senders the domain actually uses.
TXT chunks are different
A DNS host can split one long TXT record into several quoted character strings. Those strings are joined for the record value; that is different from publishing two separate v=spf1 records.
Check the exact DNS name
A root domain and a sending subdomain can have different policies. Review the name your service actually uses instead of removing a valid policy from another name.
Questions
Can I delete every TXT record and start again?
Keep unrelated verification and service records. Only replace the duplicate SPF policies after you have confirmed the authorised senders and prepared their replacement.
Will merging records guarantee delivery?
No. A valid SPF policy is one part of authentication. Alignment, DKIM, reputation and the receiving provider's handling still matter.
Checking sends your public domain to AskQuokka. Record generation and copying run in this tab. No DNS settings are changed and no email is sent. Domain inputs and lookup results are not included in tool analytics.
Official references
References checked 23 October 2026. Use your provider's current domain-specific values.
More setup and troubleshooting guides
SPF Too Many DNS Lookups: Find the Cause
Review SPF lookup-limit findings, understand nested includes and plan a change using your actual sending services. Includes a free DNS checker.
Google Workspace SPF Record: Setup and Check
Check Google Workspace SPF, review the Google-only policy and account for other sending services before changing DNS. Free checker and record builder.