Skip to main content

​
Why Verify Your Domain?

Better Deliverability

DKIM signing proves email authenticity

Custom Sender

Send from your own domain address

Brand Trust

Recipients see your domain, not ours

No Spam Warnings

Avoid “via unosend.co” labels

​
Setup Guide

1

Add Your Domain

Add your domain to Unosend through the dashboard or API:
cURL
curl -X POST https://www.unosend.co/api/v1/domains \
  -H "Authorization: Bearer un_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "domain": "yourdomain.com"
  }'

​
Response

response.json
{
  "id": "dom_xxxxxxxxxxxxxxxx",
  "domain": "yourdomain.com",
  "status": "pending",
  "dns_records": [
    {
      "type": "TXT",
      "name": "_unosend",
      "value": "v=unosend1 k=abc123..."
    },
    {
      "type": "TXT",
      "name": "@",
      "value": "v=spf1 include:_spf.unosend.co ~all"
    },
    {
      "type": "CNAME",
      "name": "unosend._domainkey",
      "value": "dkim.unosend.co"
    }
  ],
  "created_at": "2024-01-15T10:30:00Z"
}
2

Configure DNS Records

Add the following DNS records to your domain. Go to your DNS provider (Cloudflare, Route53, GoDaddy, etc.) and add these records:

​
1. Verification Record (TXT)

This record proves you own the domain:
FieldValue
TypeTXT
Name/Host_unosend
Valuev=unosend1 k=your-verification-code
TTL3600 (or Auto)

​
2. SPF Record (TXT)

Authorizes Unosend to send emails on your behalf:
FieldValue
TypeTXT
Name/Host@ (or your domain)
Valuev=spf1 include:_spf.unosend.co ~all
TTL3600 (or Auto)

​
3. DKIM Record (CNAME)

Points to our DKIM public key for email signing:
FieldValue
TypeCNAME
Name/Hostunosend._domainkey
Valuedkim.unosend.co
TTL3600 (or Auto)
That’s it! Just 3 simple records - 2 TXT and 1 CNAME. No more copying long DKIM keys!
Optionally add a CNAME for link branding in your emails:
FieldValue
TypeCNAME
Name/Hosttrack
Valuetrack.unosend.co
TTL3600 (or Auto)
The exact record values will be shown in your dashboard after adding a domain. The values above are examples.
3

Verify Your Domain

After adding DNS records, trigger verification. DNS propagation can take up to 48 hours, but usually completes within a few minutes.
cURL
curl -X POST https://www.unosend.co/api/v1/domains/dom_xxxxxxxx/verify \
  -H "Authorization: Bearer un_your_api_key"

​
Response

response.json
{
  "id": "dom_xxxxxxxxxxxxxxxx",
  "domain": "yourdomain.com",
  "status": "verified",
  "verified_at": "2024-01-15T10:35:00Z"
}

​
Provider-Specific Instructions

  1. Go to your domain in Cloudflare dashboard
  2. Click DNS in the sidebar
  3. Click “Add record” for each record
  4. Set proxy status to “DNS only” (gray cloud)
  1. Open Route 53 console
  2. Select your hosted zone
  3. Click “Create record” for each entry
  4. Use Simple routing
  1. Go to your domain’s DNS Management
  2. Click “Add” in the Records section
  3. Select TXT as the record type
  4. Enter the host and value

​
Troubleshooting

Verification taking too long?DNS propagation can take up to 48 hours. You can check propagation status at dnschecker.org.
CNAME record not validating?Make sure you’re entering the Name/Host without your domain suffix. For example, enter unosend._domainkey not unosend._domainkey.yourdomain.com.
Cloudflare proxy enabled?If using Cloudflare, make sure the proxy is disabled (gray cloud icon) for CNAME records. DNS-only mode is required for DKIM authentication.

​
Verification Complete!

Once verified, you can start sending emails from your domain. Your emails will be DKIM-signed and show your domain as the sender.