When verifying your custom sender domain in Omnisend, you might see errors related to your SPF (Sender Policy Framework) record.

SPF is part of your domain's DNS (Domain Name System) setup. It tells email providers that Omnisend is authorized to send emails on your behalf.

If SPF verification fails, domain verification also fails, which can hurt your email deliverability. This article explains common SPF errors and how to fix them in your domain provider's settings.

Before You Begin

If you haven't verified your sender domain yet, see Set Up Your Email Domain in Omnisend.
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 verification. If SPF verification fails, Omnisend displays an error message explaining the issue.

Below are the two most common SPF errors and how to troubleshoot them.

Note: You may encounter both errors at once. If so, fix each issue separately using the instructions below.

Error: Multiple SPF Records Found

A domain can only have one SPF record. That means only one TXT record in your DNS settings can start with v=spf1.

If you have multiple SPF records, email providers won't know which one to trust. SPF validation will fail automatically.

This usually happens when multiple services (such as Google Workspace and Mailgun) each add their own SPF records instead of combining them.

Example of an invalid configuration:

v=spf1 include:spf.mailgun.org ~all
v=spf1 include:_spf.google.com ~all

Both records are valid individually, but having two v=spf1 entries make SPF invalid.

Troubleshoot 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. See how to Locate Your SPF Record below for more instructions.

Step 2. Combine all "include" parts into a single record. Omnisend will provide the correct merged SPF value.

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. Keep 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 tells email providers which services can send email on behalf of your domain. When you have too many lookups, the receiving mail server has to check too many external DNS sources. As a result, it may skip SPF validation or reject your message.

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.

Troubleshoot 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, delete its include line.

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, add MX records to it. If you're unsure which MX records to use, copy them from your root domain or contact your domain provider.

Locate 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.

💬 Not sure who your DNS provider is? Look up your domain at who.is.

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.

FAQ

Why did my SPF verification suddenly fail after working for months?

Your SPF record may have changed after it was initially verified. This usually happens for one of the following reasons:

Another app added a second SPF record to your DNS. A domain can only have one SPF record. If multiple SPF records exist, SPF validation will fail automatically.
Your DNS records changed. This can occur if your DNS provider reset records, or if you added new email services that caused your SPF record to exceed the 10 DNS lookup limit.

How to fix it