EnvlopedDocs

Domain Verification

How to verify your sending domain with Envloped

Domain Verification

Before you can send emails, you need to verify ownership of your sending domain. This improves deliverability and ensures your emails don't get marked as spam.

Why Verify Your Domain?

  • Better deliverability - Verified domains have higher inbox placement rates
  • Brand protection - Prevents others from spoofing your domain
  • Required for sending - You can only send from verified domains

Adding a Domain

  1. Log in to your Envloped dashboard
  2. Navigate to SettingsDomains
  3. Click Add Domain
  4. Enter your domain (e.g., yourdomain.com)
  5. Click Continue to get your DNS records

DNS Configuration

After adding your domain, Envloped shows the exact DNS records to create. They both verify ownership and set up DKIM signing — one set of records does both jobs.

Required records (DKIM)

You will be given three CNAME records. Each one carries a unique token, so copy them from your dashboard rather than from this page:

TypeNameValue
CNAME<token1>._domainkey.yourdomain.com<token1>.dkim.envloped.com
CNAME<token2>._domainkey.yourdomain.com<token2>.dkim.envloped.com
CNAME<token3>._domainkey.yourdomain.com<token3>.dkim.envloped.com

Each <token> is a long random string unique to your domain. All three are required — DKIM key rotation uses them in turn, and a domain with only some of them published will start failing authentication later, not immediately.

Nothing else is needed to start sending: ownership verification rides on the same records.

What DKIM does, and why it is not optional

DKIM attaches a cryptographic signature to every message, which the receiving mail server checks against the public key published in these DNS records. Mail that fails the check — or has no signature at all — is far more likely to be filed as spam, and Gmail and Yahoo now require authentication for bulk senders. Envloped will not let you send from an unverified domain for exactly this reason.

Two things to check on your DNS provider:

  • Do not proxy these records. On Cloudflare they must be "DNS only" (grey cloud). A proxied CNAME breaks the lookup.
  • Watch for an auto-appended domain. Many providers append your domain to whatever you type in the name field. If yours does, enter <token>._domainkey rather than the full hostname, or you will end up with <token>._domainkey.yourdomain.com.yourdomain.com. This is the single most common reason verification never completes.

Once DKIM is verified, publish a DMARC record so receivers know what to do with mail that fails authentication:

TypeNameValue
TXT_dmarc.yourdomain.comv=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

Start at p=none (monitor only), read the reports for a couple of weeks, and tighten to p=quarantine once you are confident every legitimate sender for the domain is authenticated.

Adding DNS Records

The exact steps depend on your DNS provider. Here are instructions for common providers:

Cloudflare:

  1. Go to your domain's DNS settings
  2. Click Add record
  3. Select CNAME as the type
  4. Enter the name and target from the table above
  5. Set Proxy status to DNS only (gray cloud)
  6. Click Save

GoDaddy:

  1. Go to My ProductsDNS
  2. Click Add under Records
  3. Select CNAME as the type
  4. Enter the host and points to values
  5. Click Save

Namecheap:

  1. Go to Domain ListManage
  2. Click Advanced DNS
  3. Click Add New Record
  4. Select CNAME Record
  5. Enter the host and target values
  6. Click the checkmark to save

Verification Process

After adding the DNS records:

  1. Return to your Envloped dashboard
  2. Go to SettingsDomains
  3. Click Verify next to your domain
  4. Wait for verification (usually 1-5 minutes, can take up to 48 hours)

The status will change from Pending to Verified once complete.

Troubleshooting

Verification taking too long?

DNS propagation can take up to 48 hours. If verification is still pending after this time:

  • Double-check the DNS records are entered correctly
  • Ensure there are no typos in the record names or values
  • Check if your DNS provider requires you to omit the domain suffix
  • Try using a DNS lookup tool to verify the records are visible

Common Issues

"Record not found" error:

  • The DNS record may not have propagated yet
  • The record name might be incorrect - some providers automatically append the domain

"Invalid record value" error:

  • Check for extra spaces or characters in the value
  • Ensure you copied the full value from the dashboard

Domain stuck in "Pending" status:

  • Clear your DNS cache and try again
  • Contact support if the issue persists after 48 hours

Sending From Subdomains

You can send from any subdomain of a verified root domain. For example, if you verify yourdomain.com, you can send from:

  • hello@yourdomain.com
  • noreply@mail.yourdomain.com
  • updates@notifications.yourdomain.com

On this page