mailenv
All guides

How to verify your sending domain for Amazon SES delivery.

MailEnv sends from your own domain, with your own DKIM signature. Verifying the domain proves you control it and lets mailbox providers authenticate every message.

5 steps 6 min read

01Add your domain

In the dashboard, open Domains and click Add Sender Domain. Enter the domain you'll send from in Domain Name, such as acme.com or a subdomain like mail.acme.com. Type it again in Confirm Domain Name, then click Add Domain.

Before the domain is added, MailEnv checks that:

  • The domain is registered and has working nameservers.
  • It isn't already in your account.
  • It isn't verified by another MailEnv account. Each domain can only be verified once.
  • You have room on your plan. The number of sender domains depends on your plan.

02Wait for approval if your domain is new

MailEnv looks up the domain's registration record. Domains older than 30 days, with a registrar on record, are approved automatically.

Newer domains, and domains without public registration details, go to a person for review. Brand-new domains are a common spam signal, so this check protects everyone sending on the network.

The DNS records and the verify button appear on the domain's page once it's approved.

Planning a launch on a new domain? Add it early so review is done before you need to send.

03Publish the DNS records

Open the domain from Domains to see its records on the Manage Sender Domain page. Each one has a name, a type, a value, and a status. Add them at your DNS provider, such as Cloudflare, Route 53, GoDaddy, or Namecheap.

RecordTypeWhat it does
DKIMAs shownPublishes the public keys that prove each message was signed for your domain and not altered.
MAIL FROMMXRoutes bounce notifications for your custom MAIL FROM subdomain.
MAIL FROM SPFTXTAuthorizes Amazon SES to send for that subdomain, so SPF passes and aligns with your domain.
DMARCTXTTells mailbox providers how to handle mail that fails authentication. Gmail and Yahoo require it for bulk senders.

Copy names and values exactly. Many DNS providers add your domain to the end of the name automatically, so if the record name is _dmarc.acme.com, you may only need to enter _dmarc.

Already have a DMARC record? Don't add a second one. A domain can only have one DMARC record, so update the existing record instead.

04Verify

Back on the domain page, click the Verify DNS Records button next to the domain name. MailEnv looks up every record and marks each one Verified or Pending. The domain is ready to send once all of them are verified.

Still pending? DNS changes can take a few minutes to a few hours to propagate. Check for typos, extra quotes, or a duplicated domain in the record name, then verify again.

05Send from the domain

Any address on a verified domain can be used as the from address in your send requests. If a domain isn't verified yet, or is paused, the API refuses the send with a 403 that names the domain.

Next, create an API key and send your first email.

FAQ

Common questions

Stuck on a step? Talk to an engineer.

Can I use a subdomain?

Yes. Many teams send transactional mail from a subdomain such as mail.acme.com, which keeps its reputation separate from the main domain.

Why does my domain need manual approval?

Domains registered within the last 30 days, or without public registration details, are reviewed by a person before they can send. This keeps freshly registered spam domains off the network.

Do I lose my reputation if I leave MailEnv?

No. You send from your own domain with your own DKIM keys and DMARC policy, so your domain reputation stays with you.

Which DMARC policy should I use?

Start with p=none and reporting turned on while you confirm everything passes, then move to p=quarantine or p=reject. We can help you plan the change.

Ready to send?

Request access, verify your domain, and send your first email through Amazon SES with one API key.