Domains
Add and verify domains to authenticate your outbound email with DKIM and DMARC.
Overview
Before you can send email through your cluster, you must add and verify at least one domain. This process proves you own the domain and configures the DNS records necessary for email authentication.
Proper domain authentication improves deliverability, protects your brand from spoofing, and ensures receiving mail servers trust your messages.
Each domain belongs to a single cluster. You can add the same domain name to multiple clusters if needed—each will have its own unique DKIM keys.
Email Authentication Concepts
When you add a domain, you'll configure two types of DNS records. Here's what each one does:
DKIM (DomainKeys Identified Mail)
DKIM adds a cryptographic signature to every email you send. When a receiving mail server gets your message, it looks up your public key in DNS and verifies the signature matches. This proves:
- The email actually came from your domain
- The message wasn't modified in transit
When you add a domain, a unique RSA 2048-bit key pair is automatically generated. The public key goes in your DNS; the private key is securely stored and used to sign outbound messages.
DMARC (Domain-based Message Authentication, Reporting & Conformance)
DMARC builds on DKIM by telling receiving servers what to do when authentication fails. It also enables reporting so you can monitor authentication results.
The DMARC policy we recommend uses:
p=reject— Reject emails that fail authenticationadkim=s— Strict DKIM alignment (the signing domain must exactly match the From domain)aspf=r— Relaxed SPF alignment
Adding a Domain
- Navigate to the Domains page from the sidebar
- Click the Add domain button
- Enter your domain name (e.g.,
example.com) - Click Add domain
You'll be redirected to the domain detail page showing the DNS records you need to configure.
Domain Requirements
- Must be a valid fully-qualified domain name (FQDN)
- Cannot be an IP address
- Cannot use reserved TLDs:
localhost,local,test,invalid,example,localdomain - Must be unique within your cluster (the same domain can exist in different clusters)
DNS Records Setup
After adding a domain, you'll see two DNS TXT records that need to be added to your DNS provider:
| Record | Name | Value |
|---|---|---|
| DKIM | unmta._domainkey.example.com | p=MIIBIjANBg... (your unique public key) |
| DMARC | _dmarc.example.com | v=DMARC1; p=reject; adkim=s; aspf=r |
Click the copy button next to each record value to copy it to your clipboard.
Provider-Specific Instructions
- Log in to your Cloudflare dashboard
- Select your domain
- Go to DNS → Records
- Click Add record
- For each record:
- Type: TXT
- Name: Enter the name from the table above (e.g.,
unmta._domainkeyfor DKIM) - Content: Paste the value
- TTL: Auto
- Click Save
For the DKIM record, enter only unmta._domainkey as the name—Cloudflare automatically appends your domain.
- Open the Route 53 console
- Select Hosted zones and click your domain
- Click Create record
- For each record:
- Record name: Enter the subdomain portion (e.g.,
unmta._domainkeyfor DKIM,_dmarcfor DMARC) - Record type: TXT
- Value: Paste the value wrapped in quotes
- TTL: 300 (or your preference)
- Record name: Enter the subdomain portion (e.g.,
- Click Create records
The general steps for adding TXT records are similar across DNS providers:
- Log in to your DNS provider's management console
- Navigate to your domain's DNS settings (often called "DNS Management", "DNS Records", or "Advanced DNS")
- Add a new TXT record for each of the two records
- For each record, you'll need to enter:
- Type: TXT
- Name/Host: The record name
- Value/Content: The record value from the table above
- TTL: Use the default or set to 3600 (1 hour)
- Save your changes
Some providers automatically append your domain to the record name. If you're adding the DKIM record and your provider does this, enter only unmta._domainkey rather than the full unmta._domainkey.example.com.
DNS changes can take up to 48 hours to propagate, though most updates appear within a few minutes to a few hours.
Verifying a Domain
Once you've added the DNS records:
- Go to your domain's detail page
- Click the Verify Now button
The system queries DNS for your DKIM record. It must be correctly configured for verification to succeed.
If verification fails, you'll see which records are still pending. Double-check your DNS configuration and try again—remember that DNS propagation can take time.
What Gets Verified
| Record | Verification Check |
|---|---|
| DKIM | TXT record at unmta._domainkey.yourdomain.com contains your public key |
DMARC is displayed in the DNS records table but is not required for domain verification. However, we strongly recommend configuring it for optimal deliverability.
Domain Status
Domains have two possible statuses:
| Status | Meaning |
|---|---|
| Pending | DNS records not yet verified. Email cannot be sent from this domain. |
| Verified | Domain is authenticated and ready to send email. |
Ongoing Monitoring
Verified domains are automatically monitored to ensure DNS records remain correctly configured. If your DNS records change or are removed:
- First failed check: You'll receive a warning email. The domain stays verified to give you time to fix the issue.
- Second consecutive failed check: The domain is downgraded to Pending status and you'll receive a notification. You'll need to fix the DNS records and verify again.
This two-strike policy prevents brief DNS issues from immediately disrupting your email sending while still catching persistent problems.
Managing Domains
Viewing Domain Details
Click any domain in the list to view its detail page, which shows:
- Current verification status
- All DNS records with copy buttons
- Per-record verification status
Deleting a Domain
To delete a domain:
- Go to the domain's detail page
- Click the menu button and select Delete domain
- Type the domain name to confirm
- Click Delete domain
Deleting a domain is immediate and irreversible. Any email sent from this domain will be rejected after deletion.
API Reference
For programmatic domain management, see the Domains API documentation.