Custom domain

Send as [email protected] instead of ugly bounce addresses.

Why bother

Sending from [email protected] instead of a generic bounce address dramatically improves deliverability and looks legit. SPF + DKIM on your own domain is the price of admission to most inboxes today.

Add your domain

  1. Brand settings → Domain → enter the domain (e.g. example.com).

  2. Maillayer asks the configured provider for the DNS records needed (SES returns DKIM CNAMEs, Mailgun returns TXT + CNAME records, etc.).

  3. Add those records at your DNS host. Cloudflare, Route 53, Namecheap — all work the same way.

  4. Maillayer polls for verification and flips the badge to verified when the records resolve. This usually takes 5–30 minutes.

What gets verified

  • SPF — a TXT record listing servers authorized to send for this domain.
  • DKIM — public key TXT record(s); the provider signs each outgoing email with the matching private key.
  • DMARC — optional but recommended. See SPF, DKIM, DMARC.
  • Tracking CNAME — for click/open tracking, some providers want a CNAME like email.example.com.
Don't share your DKIM key across providers
Each provider needs its own DKIM record at a unique selector (m1._domainkey, s1._domainkey, etc.). Add all of them — SPF lookups merge automatically.

Sub-domain trick

Send marketing email from send.example.com and transactional fromtx.example.com. Sub-domains have independent reputation, so a marketing complaint won't tank your password reset deliverability.