A domain can have only one SPF record. If yours has two, mail systems treat SPF as broken for every message you send, which can push your real email to spam and make your domain easier to spoof.
Free, no sign-up. Checks SPF, DKIM, DMARC, mail servers and blacklists in one go.
Why two SPF records break SPF
The SPF standard says that when a mail system finds more than one TXT record starting with v=spf1 on the same domain, it must stop and return an error (“permerror”). It doesn’t pick one or combine them. Your SPF check simply fails.
This usually happens without anyone meaning to. A business sets up email with one provider, then adds a newsletter tool or switches providers, and the new setup instructions say “add this SPF record.” Someone adds it as a new record instead of editing the existing one. In our study of Santa Clara County small businesses, 15 of 366 domains had this exact problem.
How to find them
Run the check above. If you have more than one SPF record, it shows each one.
You can also look in your DNS host’s records list (GoDaddy, Cloudflare, Squarespace, Namecheap or wherever your domain is managed). Filter by type TXT and look at the records for @ or your bare domain name. Any value starting with v=spf1 is an SPF record. Other TXT records, such as Google or Microsoft verification codes, are fine to leave alone.
How to merge them into one
Take every include:, ip4:, ip6:, a and mx from all of the records, put them in one record, and end with a single all rule.
Example
Say a business moving from Microsoft 365 to Google Workspace still sends some email through both, and its domain has these two records:
v=spf1 include:_spf.google.com ~all
v=spf1 include:spf.protection.outlook.com -all
The merged record is:
v=spf1 include:_spf.google.com include:spf.protection.outlook.com ~all
Then:
- Edit the first record to the merged value.
- Delete the second record.
- Wait an hour or so, then run the check again to confirm you have one valid record.
Getting the merge right
- Keep one
v=spf1at the start and oneallrule at the end. Never two of either. - Choose one ending. If the records ended differently, use
~allwhile you confirm everything works, or-allif you’re sure the list is complete. Never use+all. - Drop services you no longer use. Merging is a good time to clean up. Each
includeuses part of SPF’s 10-lookup limit. - Watch the 10-lookup limit. Combining records can push you over it, which also breaks SPF. Our SPF checker counts lookups for you.
- Don’t confuse subdomains. A record on
mail.yourcompany.comis separate from one onyourcompany.com. The one-record rule applies to each name separately.
Common questions
Can I split a long SPF record into two to stay organized?
No. Two records on the same name is exactly the error this page is about. A single SPF record can be long. If it’s over 255 characters, many DNS hosts handle it automatically by splitting it into strings inside the same record, which is allowed.
What about the old “SPF” record type?
Some older DNS setups have a record with type SPF instead of TXT. That type was retired in 2014 and mail systems ignore it. Delete it and keep your TXT record.
After fixing SPF, what’s next?
Make sure DKIM is signing your email and that DMARC is set to block forgeries. Check them with our DKIM checker and DMARC checker, or follow the full guide for Google Workspace, Microsoft 365, Zoho Mail or GoDaddy.
Records break without anyone noticing
A website move, a new email tool or a DNS change can quietly undo this setup. MailWatchman checks your domain every day and emails you the moment something changes, with the fix. Plans start at $6 a month.