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 -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._domainkey",
      "value": "v=DKIM1; k=rsa; p=MIIBIjANBg..."
    },
    {
      "type": "MX",
      "name": "send",
      "value": "10 feedback-smtp.us-east-1.amazonses.com",
      "priority": 10
    },
    {
      "type": "TXT",
      "name": "send",
      "value": "v=spf1 include:amazonses.com ~all"
    }
  ],
  "created_at": "2024-01-15T10:30:00Z"
}
2

Configure DNS Records

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

​
1. DKIM Record (TXT)

This enables DKIM signing for email authentication:
FieldValue
TypeTXT
Name/Hostunosend._domainkey
Valuev=DKIM1; k=rsa; p=YOUR_PUBLIC_KEY
TTL3600 (or Auto)
The DKIM public key is unique to your domain and will be shown in your dashboard. It’s a long base64-encoded string.

​
2. MX Record (for bounce handling)

This enables bounce and complaint handling via AWS SES. Use the MX server for your region:
FieldValue
TypeMX
Name/Hostsend
ValueSee region table below
Priority10
TTL3600 (or Auto)
MX Server by Region:
RegionMX Value
US East (N. Virginia)feedback-smtp.us-east-1.amazonses.com
EU West (Ireland)feedback-smtp.eu-west-1.amazonses.com
Asia Pacific (Tokyo)feedback-smtp.ap-northeast-1.amazonses.com
Your region is shown in the dashboard when you add a domain. Most users are on us-east-1.

​
3. SPF Record (TXT)

Authorizes AWS SES to send emails on your behalf:
FieldValue
TypeTXT
Name/Hostsend
Valuev=spf1 include:amazonses.com ~all
TTL3600 (or Auto)
Just 3 records! We’ve simplified the setup - just 2 TXT records and 1 MX record. Your emails will be sent through AWS SES with enterprise-grade deliverability.
Important: The MX and SPF records use the send subdomain, not your root domain. This is intentional for bounce handling.
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"
}

​
DNS Record Summary

Here’s a quick reference for all required records:
TypeNameValue
TXTunosend._domainkeyv=DKIM1; k=rsa; p=... (your unique key)
MXsend10 feedback-smtp.us-east-1.amazonses.com
TXTsendv=spf1 include:amazonses.com ~all

​
Provider-Specific Instructions

  1. Go to your domain in Cloudflare dashboard
  2. Click DNS in the sidebar
  3. Click Add record for each record:
    • For TXT records: Select TXT, enter name and value
    • For MX record: Select MX, enter send as name, feedback-smtp.us-east-1.amazonses.com as value, priority 10
  4. Set proxy status to DNS only (gray cloud) for all records
  1. Open Route 53 console
  2. Select your hosted zone
  3. Click Create record for each entry:
    • TXT records: Simple routing, enter name and value in quotes
    • MX record: Simple routing, enter send as name, 10 feedback-smtp.us-east-1.amazonses.com as value
  1. Go to your domain’s DNS Management
  2. Click Add in the Records section
  3. For TXT records:
    • Type: TXT
    • Name: unosend._domainkey or send
    • Value: the record value
  4. For MX record:
    • Type: MX
    • Name: send
    • Priority: 10
    • Value: feedback-smtp.us-east-1.amazonses.com
  1. Go to Domain List → Manage → Advanced DNS
  2. Click Add New Record for each entry
  3. For TXT records: Select TXT Record
  4. For MX record: Select MX Record, set priority to 10
  1. Go to DNS settings for your domain
  2. Click Manage custom records
  3. Add each record with the correct type and values
  4. For MX: Use priority 10

​
Troubleshooting

Verification taking too long?DNS propagation can take up to 48 hours. You can check propagation status at dnschecker.org.
DKIM record not validating?Make sure you’re copying the entire public key value including v=DKIM1; k=rsa; p=.... The key is a long base64 string - don’t truncate it.
MX record issues?Ensure you’re adding the MX record to the send subdomain, not your root domain. The full record name should be send.yourdomain.com.
Cloudflare proxy enabled?If using Cloudflare, make sure the proxy is disabled (gray cloud icon) for all records. DNS-only mode is required for email authentication.
Already have SPF on root domain?The SPF record for Unosend goes on the send subdomain, so it won’t conflict with any existing SPF record on your root domain.

​
Verification Complete!

Once verified, you can start sending emails from your domain. Your emails will be:
  • DKIM-signed with your unique key
  • Delivered via AWS SES for maximum deliverability
  • Bounce-tracked automatically via the MX record

​
Sending Emails

After verification, send emails from any address at your domain: 
curl -X POST https://www.unosend.co/api/v1/emails \
  -H "Authorization: Bearer un_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "[email protected]",
    "to": "[email protected]",
    "subject": "Hello from my verified domain!",
    "html": "<p>This email is DKIM-signed and delivered via AWS SES.</p>"
  }'