Setting up SPF Record Checks for Spam
- 18 Aug 2024
- 1 Minute to read
- DarkLight
Setting up SPF Record Checks for Spam
- Updated on 18 Aug 2024
- 1 Minute to read
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
If you use your own sending domain, you need to add records to your domain provider's DNS (Domain Name System).
For example, support@yourcompany.com or johndoe@yourbusinessname.com.
These records enable Sender Policy Framework (SPF) record checks and help you avoid having your space's email notifications flagged as spam in customer inboxes.
Adding DNS records to your sending domain is a quick and easy way to make sure your customers receive all the notifications your space sends.
You need to add three records through your domain provider's DNS or a DNS service such as Cloudflare.
You first need to add two records that are the same across all providers:
| DNS Record Type | Name | Value |
|---|---|---|
| TXT | v=spf1 mx a include:_spf.nexudus.com | |
| 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 would be s1._domainkey.coworking.com and s2._domainkey.coworking.com.
The way you add the three records to your DNS is different for each domain provider. The procedure for some of the most common providers are listed below:
GoDaddy (default provider if you use Outlook for Business)
Google Domains (default provider if you use Gmail for Business and didn't own your domain prior to signing up)
Bluehost
CNAME and TXT Records (Legacy)
Cloudflare
Domain.com
Once you've added the three records to your DNS, you've successfully completed the setup and your emails should no longer be flagged as spam in customer inboxes.
The update can take up to 72 hours to come into effect.
Was this article helpful?