Required DNS settings for Opensense

Overview

To make sure email branding and deliverability work properly, every Opensense customer must configure two DNS records: a new CNAME record, and an update to the existing SPF record. If you use Cloudflare, see Setting up the Opensense CNAME in Cloudflare before you add the CNAME record.

External and internal DNS

Apply these updates to your external DNS and, if applicable, your internal DNS too.

Why these records matter

• Consistent and secure brand presentation across emails
• Better email deliverability and authentication alignment
• Support for Opensense’s email signature and tracking infrastructure

DNS records required by Opensense

Setting	1. CNAME record	2. SPF record
Action	Create a new record	Modify your existing TXT record
Record type	CNAME	TXT (SPF)
Host or name	smart	@ or your domain root (for example, customer.com)
ValuePoints to, FQDN, or target	whs.sendergen.com	Add include:_spf.sendergen.com
Example	—None	v=spf1 include:_spf.google.com include:_spf.sendergen.com ~all

Updating your SPF record

1. Find your current SPF TXT record. It usually begins with v=spf1.
2. Add this include statement to the existing entry:

include:_spf.sendergen.com

The underscore in _spf.sendergen.com is critical. Make sure that it isn’t left out.

Only one SPF record

Don’t create a separate SPF record. There must be only one v=spf1 TXT record at the root level of each domain.

What’s next

• Verifying your Opensense DNS records: check that the records are in place.
• Setting up the Opensense CNAME in Cloudflare
• Opensense SSL certificates from Let’s Encrypt: CNAME and CAA requirements: if your domain uses CAA records.

For further help, contact Opensense Support at help@opensense.com.