When verifying your custom sender domain in Omnisend, you may encounter errors related to your SPF (Sender Policy Framework) record.
SPF is part of your domain’s DNS (Domain Name System) setup and helps email providers confirm that Omnisend is authorized to send emails on your behalf.
If the SPF record verification fails, domain verification will also fail, which can affect your email deliverability. This article explains what these issues mean and how to resolve them in your domain provider’s settings.
Before You Begin
If you haven't verified your sender domain yet, check the dedicated article.
To view your verification details, go to Store settings → Domain → click the three dots next to your domain → Open DNS records.
Common SPF Errors & Troubleshooting
Omnisend checks your domain’s SPF record during the verification process. If the SPF verification fails, Omnisend will display an error message explaining the issue, allowing you to quickly troubleshoot it.
Below are the two most common SPF errors you may encounter, along with instructions on how to troubleshoot them.
Note: In some cases, you may encounter both errors at the same time. If that happens, you’ll need to troubleshoot each issue separately using the instructions below.
Error: Multiple SPF Records Found
A domain can only have one SPF record. That means you can have only one TXT record in your DNS settings that starts with v=spf1.
If you have multiple SPF records, email providers won’t know which one to trust, and your SPF validation will fail automatically.
This issue typically occurs when multiple services (e.g., Google Workspace, Mailgun) each add their own SPF record instead of combining them into a single record.
Example of an invalid configuration:
v=spf1 include:spf.mailgun.org ~all
v=spf1 include:_spf.google.com ~all
Even though both records are valid individually, having two v=spf1 entries make the SPF invalid.
Troubleshooting Duplicate SPF Records
To resolve this issue, you need to merge all the SPF records you have into a single record.
Step 1. Open your DNS panel and find all TXT records that begin with v=spf1. Check the instructions below on how to open and edit your DNS panel.
Step 2. Combine all “include” parts into a single record. Omnisend will provide you with the correct merged SPF value you need to use.
Important: Omnisend may not be able to generate the merged SPF record when you have more than two SPF records or syntax errors in your DNS panel. In this case, we recommend contacting your domain provider or Omnisend Support Team for further guidance.
Step 3. Delete the extra SPF TXT records after merging, leaving only the combined one.
Note: After updating your DNS records, it may take up to 24 hours for the changes to propagate.
Error: Too Many DNS Lookups
Another possible SPF issue can occur due to too many DNS lookups. The SPF standard limits your record to a maximum of 10 DNS lookups. Each include:, a, mx, ptr, exists, or redirect mechanism in your SPF record counts as one lookup.
If your record exceeds this limit, SPF validation will fail even if the record itself appears correct.
In simple terms, your SPF record helps email providers verify if the sending service is allowed to use your domain. When you have many SPF lookups, you are asking the receiving mail server to check too many external DNS sources to confirm who can send on behalf of your domain.
As a result, the receiving server may skip SPF validation or reject the message entirely.
Example of a problematic record
v=spf1 include:_spf.google.com include:mailgun.org include:test1.net include:test2.com ~all
Each “include” tells the receiving server to perform another lookup. If there are too many, your SPF becomes invalid.
Troubleshooting SPF Lookups
To resolve this error, remove any unused or unnecessary include entries from your SPF record. For example, if you no longer use a specific email service, its include line should be deleted.
Keep only the entries for active services, such as Omnisend and your primary email provider.
💡 If you’re unsure which entries are needed, contact your domain provider or email services for guidance.
Example of a valid SPF record
v=spf1 include:_spf.google.com include:mailgun.org ~all
This version is shorter and stays well within the 10-lookup rule.
Note: If you need to keep multiple SPF entries because they’re all actively used, consider using a subdomain for Omnisend. When setting up a subdomain, ensure that you add MX records to it. If you're unsure which MX records to use, you can copy them from your root domain or contact your domain provider for assistance.
Locating Your SPF Record
You can edit your SPF record in your domain provider’s DNS settings (e.g., GoDaddy, Shopify, Cloudflare, Namecheap, etc.).
The DNS panel is where you manage all DNS records for your domain, such as SPF, DKIM, and CNAME entries. It should look something like this.
💬 If you don’t know who your domain or DNS provider is, you can find this information by looking up your domain name here.
Follow these steps to edit your SPF record:
Log in to your domain provider’s dashboard.
Find your DNS or “Zone Editor” section.
Locate the TXT record that contains your SPF.
Edit it according to the instructions above.
Save changes and allow time for DNS propagation.
Fixing SPF-related errors ensures your sender domain is verified correctly in Omnisend. A valid SPF record improves your email deliverability, builds trust with mailbox providers, and prevents your emails from landing in spam.
Need help? Our award-winning support team is here for you. Please feel free to reach out to us via in-app chat or email at [email protected].