Domain Setup

Verifying a domain proves you own it and lets Sendr send authenticated emails on your behalf. This improves deliverability and prevents your emails from being flagged as spam.

Required DNS records

Sendr requires three DNS records:

Record	Purpose
SPF	Authorizes Sendr's mail servers to send for your domain
DKIM	Signs outgoing emails to prevent spoofing
DMARC	Defines policy for handling unauthenticated mail

Step 1: Add your domain

Via the API:

const domain = await sendr.domains.create({ name: "acme.com" });

Or in the dashboard under Domains → Add Domain.

Sendr returns the exact DNS record values to add.

Step 2: Add DNS records

Log in to your DNS provider and add the three records. The exact steps vary by provider:

Cloudflare

1. Go to your domain → DNS → Records
2. Click Add record for each of the three records
3. For SPF and DMARC, set type to TXT
4. For DKIM, set type to TXT
5. Set Proxy status to DNS only (orange cloud off) for all three

AWS Route 53

1. Open the hosted zone for your domain
2. Click Create record for each record
3. For simple routing policy, paste the value directly

Namecheap

1. Go to Domain List → Manage → Advanced DNS
2. Under Host Records, click Add New Record
3. Select record type, enter host and value

GoDaddy

1. Go to DNS Management for your domain
2. Click Add and select the record type
3. Enter the host (without the domain suffix) and value

SPF record

Type:  TXT
Host:  @  (or your root domain)
Value: v=spf1 include:spf.sendr.dev ~all

If you already have an SPF record, add include:spf.sendr.dev to it:

v=spf1 include:spf.sendr.dev include:other-provider.com ~all

Do not create two separate SPF TXT records — only one SPF record is allowed per domain.

DKIM record

Type:  TXT
Host:  sendr._domainkey  (i.e., sendr._domainkey.acme.com)
Value: v=DKIM1; k=rsa; p=<public key from Sendr>

The public key value is unique to your domain and provided by Sendr when you add the domain.

DMARC record

Type:  TXT
Host:  _dmarc  (i.e., _dmarc.acme.com)
Value: v=DMARC1; p=none; rua=mailto:dmarc@acme.com

Start with p=none (monitor mode) before enforcing. Upgrade to p=quarantine or p=reject once you've confirmed no legitimate emails are failing.

Step 3: Verify

After adding all three records, trigger verification:

const result = await sendr.domains.verify("dom_abc123");
console.log(result.status);         // "verified" or "pending"
console.log(result.spf_verified);   // true
console.log(result.dkim_verified);  // true
console.log(result.dmarc_verified); // true

Or click Verify in the dashboard.

DNS propagation

Changes typically propagate within 2–10 minutes but can take up to 48 hours. If verification fails, wait a few minutes and try again.

Check propagation with:

# SPF
dig TXT acme.com | grep spf

# DKIM
dig TXT sendr._domainkey.acme.com

# DMARC
dig TXT _dmarc.acme.com

BIMI (Brand logo in inbox)

BIMI displays your company logo in supporting email clients (Gmail, Apple Mail, Yahoo). Available on Pro and higher plans.

Requirements:

1. DMARC policy must be p=quarantine or p=reject (not p=none)
2. A verified BIMI record with an SVG logo URL
3. A VMC certificate (for Google — optional but recommended)

Type:  TXT
Host:  default._bimi
Value: v=BIMI1; l=https://acme.com/logo.svg; a=https://acme.com/vmc.pem

Subdomain sending

You can send from subdomains of a verified domain. Add and verify mail.acme.com as a separate domain — it gets its own DNS records.

Sending domain vs. root domain

You can verify acme.com for sending without affecting your website's DNS (MX records, etc.) as long as you don't change existing records.