​

Domain Verification

Setting up a custom domain ensures your emails reach inboxes and aren’t flagged as spam. New custom domains include 4 DNS records for sending authentication, bounce tracking, and branded reply routing.

​

Why Domain Verification Matters

When you send an email, receiving mail servers (Gmail, Outlook, etc.) check if the email is legitimate. Without a verified custom domain, your emails may:

• Land in spam folders
• Be rejected entirely
• Damage your sending reputation

Domain verification proves:

1. You own the domain - Only someone with DNS access can add the required records
2. You authorize Sequenzy to send on your behalf - The records explicitly list Amazon SES as an authorized sender

​

How Email Authentication Works

Email authentication uses multiple protocols working together. When a receiving server gets your email:

1. SPF Check - “Is this server allowed to send for this domain?” → Looks up TXT record on bounce subdomain
2. DKIM Check - “Was this email modified in transit?” → Verifies cryptographic signature using public key from TXT record

​

Required DNS Records

Sequenzy shows the required DNS records for your domain during setup:

​

DKIM Record (1 TXT record)

DKIM adds a digital signature to every email. Sequenzy generates a unique key pair for your domain — outgoing emails are signed with the private key, and receiving servers verify using the public key published in this record.

​

SPF Record (1 TXT record)

SPF authorizes which servers can send email for your domain. We use a bounce subdomain as the envelope sender for better deliverability tracking.

​

MX Record (1 MX record)

Routes bounce notifications to AWS SES so failed deliveries are tracked and subscribers are marked as bounced.

​

Inbound Reply MX Record (1 MX record)

Routes replies to Sequenzy when reply tracking uses your own domain. This enables branded reply addresses such as reply+{emailId}@inbound.yourdomain.com.

​

Optional: DMARC

DMARC is not required for domain verification, but we recommend setting it up for better deliverability and domain protection. DMARC tells receiving servers what to do when authentication fails and where to send reports.

​

Verification Methods

​

Option 1: Automatic Setup with Cloudflare

If your domain uses Cloudflare DNS, you can set up all records automatically with one click. Step 1: Create a Cloudflare API Token

1. Go to Cloudflare Dashboard → My Profile → API Tokens
2. Click Create Token
3. Use the Edit zone DNS template or create a custom token with:
   • Zone - Zone - Read (to find your zone)
   • Zone - DNS - Edit (to create records)
4. Set zone resources to All zones or select your specific domain
5. Click Create Token and copy it immediately

Step 2: Connect in Sequenzy

1. Go to Settings → Domains and click your domain
2. Click Connect Cloudflare
3. Paste your API token
4. Click Verify & Create Records

Sequenzy will validate your token, find the zone for your domain (including subdomains), and create all required DNS records automatically.

​

Option 2: Manual DNS Setup

1. Go to Settings → Domains and click your domain
2. Copy each DNS record from the verification table
3. Add them in your DNS provider’s control panel
4. Return to Sequenzy and click I’ve added the records

Common DNS Providers:

​

Verification Process

Once you’ve confirmed the DNS records were added, Sequenzy monitors their status:

1. DNS Lookup - Checks if records exist and point to correct values
2. AWS SES Verification - Once DNS is correct, AWS SES verifies the DKIM signatures
3. Inbound Routing - Once the inbound MX record is verified, Sequenzy connects the receipt rule for branded reply tracking
4. Status Update - Domain status updates from “Pending” to “Verified”

​

Verification Statuses

​

Troubleshooting

​

Records Not Detected

• Wait for propagation - DNS changes can take up to 48 hours
• Check for typos - Ensure record names and values match exactly
• Check proxy settings - For Cloudflare, DKIM records must have proxy disabled (DNS only)

​

Verification Is Stuck

If verification stays pending or misconfigured:

1. Delete the domain in Sequenzy
2. Re-add it to get a fresh DKIM key
3. Update your DNS records with the new values

​

Branded Replies Not Active

If reply+{emailId}@inbound.yourdomain.com is not active yet:

1. Confirm the inbound MX record points to the region-specific inbound-smtp endpoint shown in Sequenzy
2. Return to Settings -> Email Tracking and refresh the Reply-to Domain status
3. Leave the Reply-to Domain setting on Sequenzy until inbound routing shows as active if you want to avoid fallback behavior

​

Cloudflare Token Errors

​

Using Subdomains

We strongly recommend sending from a subdomain (e.g., mail.example.com) rather than your root domain. This protects your domain reputation and isolates any deliverability issues.

​

Best Practices

1. Use a subdomain - Protect your root domain’s reputation with mail.yourdomain.com
2. Consider setting up DMARC - While optional, DMARC protects against spoofing and helps monitor email authentication
3. Keep tokens secure - Never share your Cloudflare API token publicly
4. Verify inbound replies before switching - Keep the Reply-to Domain setting on Sequenzy until the inbound MX record and routing status are active

​

Related