SPF Records for Custom Domains and BigCommerce

The following addresses how to update a Domain Name Service (DNS) record to use SPF with your custom domain in BigCommerce.

To utilise a custom domain, the BigCommerce provider requires an SPF TXT record be added to the DNS record. This TXT record is then used by DNS to recognise email servers allowed to send messages on behalf of your custom/third-party domain. To determine whether a correspondence from the specified domain comes from an authorized messaging server, the recipient system relies on the implemented SPF TXT record. At that point, the message is either accepted, quarantined, or rejected by the email receiving system.

To implement SPF authentication for your domain, you will need access to your DNS records in the domain hosting account. Important: If you already have an SPF record, then you should modify that existing record. You must not have more than one SPF record.

For convenience, be sure to log in to your BigCommerce account to verify your domain and copy your TXT records. BigCommerce utilises an include mechanism during the set-up process. For example, if you do not have an SPF record on your domain, the following scenario is the most common and would pass SPF:

v=spf1 include:_spf.bigcommerce.com ~all

If you do already have an SPF record on your domain, simply add the following to it:


To create an SPF record for your domain name, follow these steps:

1. Log in to your domain host account

2. Navigate to your domain host’s DNS/Name Server management page (e.g. cPanel)

3. In TXT Value field, create a TXT record with the following (example) specifications:

v=spf1 include:_spf.bigcommerce.com ~all

4. Decide how you want to enforce SPF failures:

~all results in a soft fail (not authorized, but not explicitly unauthorized)

-all results in a hard fail (unauthorized)

?all is neutral (similar to no policy)

As shown above, enter your choice after v=spf1 include:_spf.bigcommerce.com

5. Save changes

Last updated byChris Grant (he/him)Chris Grant (he/him) on 4th April 2022