Setting up SPF Record Checks for Spam
  • 16 Sep 2022
  • 2 Minutes to read
  • Comment

Setting up SPF Record Checks for Spam

  • Comment

If you use your own sending domain to send email notifications to customers, you may need to update your DNS to avoid having your notifications flagged as spam.

For example, you use support@yourcompany.com* or john@yourbusinessname.com as the sender email for notifications your customers receive from Nexudus instead of no-reply@nexudus.com by default.

Tweaking your DNS records ensures smooth SPF record checks and helps you avoid having the email notifications you send automatically flagged as spam in customer inboxes.

This is a quick and easy way to make sure your customers receive all the email notifications you send.

You need to edit your domain's default SPF record and add two CNAME records to your domain provider's DNS or a DNS service such as Cloudflare.

Step 1. Adding Nexudus IPs to your SPF record

The first step is to add the following Nexudus IP addresses to your SPF record:

  • +ip4:52.51.79.206
  • +ip4:167.89.65.77

For example, if your current SPF record is v=spf1 include:spf.protection.outlook.com -all, add our IP addresses right after v=spf1. In this scenario, your SPF record should then be v=spf1 +ip4:52.51.79.206 +ip4:167.89.65.77 include:spf.protection.outlook.com -all

The way you access and edit your SPF record in your DNS is different for each domain provider. The tutorial for some of the most common providers are listed below:

GoDaddy (default provider if you use Outlook for Business)

Edit an SPF record

Google Domains (default provider if you use Gmail for Business and you didn't own your domain before signup)

Update your SPF record for added senders

Bluehost

Customizing SPF records

Cloudflare

Edit SPF records

Step 2. Adding CNAMES pointing to your Domain

You now need to add two CNAME records to your DNS, no matter which domain provider you use:

DNS Record Type Name Value
CNAME s1._domainkey.[ your domain ] s1.domainkey.u1696639.wl140.sendgrid.net
CNAME s2._domainkey.[ your domain ] s2.domainkey.u1696639.wl140.sendgrid.net
Make sure you replace [ your domain ] in the CNAME records Name field with your actual domain.

For example, if your domain is coworking.com, your CNAME records Name would be s1._domainkey.coworking.com and s2._domainkey.coworking.com.

The way you add the records to your DNS is different for each domain provider. The process for some of the most common providers are listed below:

GoDaddy (default provider if you use Outlook for Business)

TXT Records
CNAME Records

Google Domains (default provider if you use Gmail for Business and didn't own your domain prior to signing up)

CNAME and TXT Records

Bluehost

CNAME and TXT Records (Legacy)

Cloudflare

CNAME and TXT Records

Domain.com

CNAME and TXT Records

Once you've edited your SPF record and added the two CNAME records to your DNS, you've completed the setup. Email notifications you send to your customers through Nexudus should no longer be flagged as spam in their inboxes.

The update can take up to 72 hours to come into effect.

Was this article helpful?