> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nexudus.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SPF Records

> Update your DNS records to include Nexudus in your SPF policy and authenticate the domain you use for email notifications.

## Overview

If your location sends email notifications from a custom domain, inbox providers may treat those messages as spam unless you authenticate the sending domain.

> [!NOTE]
>
> For example, you use [support@yourcompany.com](mailto:support@yourcompany.com) as the sender for email notifications from Nexudus instead of [no-reply@nexudus.com](mailto:no-reply@nexudus.com).

This usually means updating your domain's SPF record and adding DKIM CNAME records. Nexudus can then be included in your sending domain's authorised mail sources without changing the way your team sends notifications in the dashboard.

You'll need to configure these settings from the domain provider that sends your notifications.

## 1. Add Nexudus to your SPF record

Add this fragment to your SPF record:

`include:_spf.nexudus.com`

For example, if your current SPF record is:

`v=spf1 include:spf.protection.outlook.com -all`

update it to:

`v=spf1 **include:_spf.nexudus.com** include:spf.protection.outlook.com -all`

The way you access and edit your SPF record in your DNS is different for each domain provider. You can find links to tutorials for some common providers below.

### Common domain provider guides

* [GoDaddy](https://uk.godaddy.com/help/edit-an-spf-record-19219)
* [Bluehost](https://www.bluehost.com/help/article/spf-records-vps-dedicated#Customizing)
* [Cloudflare](https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/)

## 2. Add the DKIM CNAME records

Add these two CNAME records to your DNS:

| DNS Record Type | Name | Value |
| - | - | - |
| CNAME | `s1._domainkey.[your domain]` | `s1._domainkey.mail.nexudus.com` |
| CNAME | `s2._domainkey.[your domain]` | `s2._domainkey.mail.nexudus.com` |

For example, if your domain is `coworking.com`, the Name fields should be:

* `s1._domainkey.coworking.com`
* `s2._domainkey.coworking.com`

### Common DNS provider guides

* [GoDaddy: Add a CNAME record](https://uk.godaddy.com/help/add-a-cname-record-19236)
* [Bluehost: Add or edit DNS records](https://www.bluehost.com/help/article/dns-management-add-edit-or-delete-dns-entries)
* [Cloudflare: Manage DNS records](https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/)
* [Domain.com: Update DNS records](https://www.domain.com/help/article/dns-management-how-to-update-dns-records)

> [!WARNING]
>
> DNS changes can take up to 72 hours to fully propagate.

## Related pages

* [Settings and configuration](https://learn.nexudus.com/platform/settings/overview.md)
* [Custom domains](https://learn.nexudus.com/platform/settings/domains.md)
* [Email templates](https://learn.nexudus.com/platform/settings/email-templates.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.