Custom domains guideCustom Domain Email Alias

Custom domain email alias — use a domain you actually own

A custom domain email alias is a forwarding address minted on a domain you own — for example contact@yourdomain.com — that drops mail straight into your real inbox while keeping your real address private. This page covers the DNS setup, the email-authentication story, and what to look for when comparing providers.

Start freeSee pricing
Definition

What is a custom domain email alias?

Same alias idea — different address. A custom-domain email alias lives on a domain you own, not on the provider's shared domain.

Regular alias
Example address
k7-bright-river@emailalias.io
Domain owner
The provider
Looks like
A privacy tool
If you leave
The alias dies
Deliverability
Provider's reputation
This page
Custom-domain alias
Example addresses
contact@yourdomain.comstripe@yourdomain.com
Domain owner
You
Looks like
A professional address
If you leave
Aliases come with you
Deliverability
Your own reputation

Mail sent to the custom-domain alias forwards to your real inbox; the sender only ever sees the alias.

Three things change once you bring your own domain

Aliases look professional

They live on a domain you control — not a shared service domain.

You aren't locked in

If you ever change providers, you keep the domain. The aliases come with you.

Deliverability is yours

Your DKIM, your SPF, your DMARC. A misconfigured shared domain can't poison your reputation.

Why bother

Why use your own domain instead of a shared one?

Shared-domain aliases (the @emailalias.io kind) are quick, anonymous, and perfect for personal use. A custom-domain alias becomes the right call when any of the four below apply.

  1. 01·For professionals

    Professional sender identity

    “Email me at contact@yourdomain.com” reads as professional. contact@randomprovider.io raises eyebrows.

  2. 02·For long-term users

    Vendor independence

    If you switch providers later, the domain stays — every alias keeps working with whoever runs them next, no migration on your side.

  3. 03·For deliverability sticklers

    Own your sending reputation

    Publish your own SPF, DKIM, and DMARC records on your domain and control the deliverability story over time.

  4. 04·For multi-persona users

    Multiple personas, one inbox

    Separate domains for personal, freelance, and business — same inbox, completely separate sender identities.

None of the four apply? A shared-domain alias on the free tier is exactly what you want — no DNS, no setup, no domain to maintain.

DNS in plain English

How custom domain email aliases work

A custom-domain alias service needs three pieces of DNS to do its job. Most providers walk you through it; the underlying mechanics are the same everywhere.

  • MX records

    Tell the rest of the internet where to deliver mail addressed to your domain. You point your domain's MX records at the alias provider's mail servers, so anything sent to anything@yourdomain.com lands at their inbound infrastructure first.

  • SPF (Sender Policy Framework)

    A TXT record listing which servers are allowed to send mail on behalf of your domain. When the alias service forwards a message and signs it as you, the recipient checks your SPF record — if the alias provider's servers are listed, the mail is trusted; if not, it gets flagged as spam or rejected.

  • DKIM (DomainKeys Identified Mail)

    A cryptographic signature attached to every outbound message. The alias provider signs forwarded messages with a key they generate; the recipient looks up your DKIM TXT record to verify the signature. This proves the message wasn't tampered with in transit and that your domain authorized the send.

  • DMARC (Domain-based Message Authentication, Reporting & Conformance)

    Tells receiving servers what to do when SPF or DKIM fails — reject, quarantine, or just report. A strict DMARC policy stops attackers from spoofing your domain. Best providers will help you tune the policy as you ramp up.

In practice, your provider gives you a checklist of records to add at your DNS host (Cloudflare, Namecheap, Route 53, wherever your domain lives). You paste them in, click verify, and the domain becomes available for minting aliases. Setup typically takes 10 minutes plus DNS propagation time. EmailAlias.io's full DNS setup walkthrough is in the documentation.

Watch out

Subdomain alias vs real custom domain alias

Some services advertise “custom domains” but only give you a subdomain on their brand — for example yourname@theprovider.com. That isn't a custom domain in any meaningful sense. Compare:

Subdomain on their brand

yourname@theprovider.com

  • Looks like a service domain to recipients.
  • You can't take it with you — switching providers means new addresses everywhere.
  • Deliverability tied to their domain reputation.
  • No control over MX, SPF, DKIM, or DMARC.

Real custom domain

contact@yourdomain.com

  • Looks professional — your brand, not theirs.
  • Portable. Switch providers; your domain (and inbox) come along.
  • Deliverability tied to your domain reputation.
  • Full control over MX, SPF, DKIM, DMARC.

We compare specific competitors on the alternative pages. Worth seeing how each handles custom domains: vs Firefox Relay, vs DuckDuckGo Email, vs SimpleLogin, vs Addy.io.

Checklist

What to look for in a custom domain alias provider

Seven things to verify before you point your domain's MX records anywhere. The order roughly matches importance — top items are deal-breakers; the rest are quality-of-life.

  1. 01

    Real custom-domain support, not subdomain

    The provider should accept any domain you own and walk you through DNS setup — not restrict aliases to a subdomain like @yourname.theirhost.com.

  2. 02

    SPF, DKIM, and DMARC enforcement

    Every alias on your custom domain should be properly authenticated. Anything less and forwarded mail lands in spam.

  3. 03

    Send-from-alias on the custom domain

    Replies should appear to come from the alias address with a DKIM signature aligned to your domain — not from a generic routing address.

  4. 04

    Programmatic API

    For adding, rotating, or auditing aliases on the custom domain. If you ever want to script alias hygiene, the API is what matters.

  5. 05

    Multiple custom domains per account

    One domain is fine for personal use; multiple is better if you're running separate personas (personal, freelance, business).

  6. 06

    Deliverability transparency

    Look for actual SPF, DKIM, and DMARC documentation on the provider's site — not just a marketing claim of good deliverability.

  7. 07

    Encryption at rest on alias mappings

    Custom-domain aliases are no less sensitive than shared-domain ones. The mapping database should be encrypted at rest with documented key management.

EmailAlias.io delivers all seven on every custom domain — documented on /security and the REST API reference.

Our approach

How EmailAlias.io handles custom domains

Custom domain support is a Premium feature. Every item below either satisfies one of the seven checklist criteria above, or extends past them.

Ticks the checklistBeyond the checklist

  • Up to 5 custom domains

    Multi-domain

    Each domain is independently verified through its own SPF, DKIM, and DMARC records — so you can run separate sender identities side by side.

  • Guided DNS setup, one-click verify

    Setup UX

    Paste-ready MX, SPF, DKIM, and DMARC records, plus a verify button that re-checks every record in one click.

  • Custom MAIL FROM subdomain

    Deliverability polish

    Optional bounce.yourdomain.com Return-Path so Gmail shows mailed-by: yourdomain.com instead of amazonses.com, with native SPF alignment.

  • Send & reply from custom-domain aliases

    Send-from-alias

    Replies are DKIM-signed by your domain, so recipients see a properly authenticated reply — not a relay.

  • Per-alias controls

    Operations

    Disable, rotate, or delete any individual alias on the custom domain in one click — without touching DNS.

  • Suspicious-sender intelligence

    Sender risk

    Inbound mail to custom-domain aliases gets the same exposure-event scoring as shared-domain aliases — risky TLDs, typosquat patterns, phishing-keyword signals.

  • REST API + MCP server

    Programmatic API

    Programmatic alias management on custom domains — script alias rotation, or let an AI assistant manage your alias hygiene via the Model Context Protocol server.

  • AES-256 at rest

    Encryption at rest

    Custom-domain mappings and metadata are encrypted at rest with documented key management.

Drill into the architecture

Full security posture is on /security; broader category framing on the email alias service guide and the private email alias guide; API reference at /documentation.

Use cases

Who needs a custom domain email alias

Freelancers and consultants

Per-client aliases on your own brand — clientname@yourdomain.com — kept separate from your personal inbox while still routing into one place.

Small businesses

Department-style aliases (sales@, support@, billing@) without paying per-mailbox seat. Mail forwards into a single shared inbox you already use.

Indie hackers and side-project owners

Each project gets its own domain and per-feature aliases (waitlist@, beta@, feedback@) without wiring up a real inbox provider for each.

Anyone running multiple personas

Personal, freelance, and business mail on three separate domains — same inbox, fully separate sender identities.

FAQ

Frequently asked questions

Do I need to own a domain to use email aliases?

No. The free plan and basic Premium use addresses on our shared domain (@emailalias.io), no domain ownership required. Custom domains are an optional Premium feature for users who want aliases on a domain they control — useful for professional, business, or vendor-portable use cases. Most personal users never need a custom domain.

How long does DNS verification take when I add a custom domain?

Once you paste the records into your DNS host (Cloudflare, Namecheap, Route 53, etc.) and click verify, the check is usually instant — DNS is cached aggressively at the resolver layer, but our verifier queries authoritative servers directly. If your records aren't visible immediately, propagation can take 5 minutes to a few hours depending on your DNS host. The verify button is safe to click multiple times.

Can I use a subdomain instead of my main domain for email aliases?

Yes. mail.yourdomain.com or aliases.yourdomain.com works the same as a root domain — same MX/SPF/DKIM/DMARC setup, just on the subdomain. People do this when they want to keep their root domain's mail handling separate (e.g., main domain runs on Google Workspace, subdomain runs on the alias service). Deliverability is identical as long as the records are right.

Can I move my aliases between providers?

Aliases on a shared provider domain (e.g. @emailalias.io) aren't portable — they live on our domain and stay with us. Aliases on a custom domain (yourdomain.com) are fully portable: you keep the domain, point its MX records at a new provider, re-create the same local-parts on their side, and the addresses keep working — provided the new provider supports custom local-parts (most do; some only issue random codes). Custom domains are a Premium feature on EmailAlias, but for anyone who plans to use aliases long-term, it's vendor-independence insurance worth having.

Can I use my own domain for email aliases?

Yes. Premium users can add up to 5 custom domains with full SPF, DKIM, and DMARC verification. Create professional aliases like contact@yourdomain.com while maintaining complete privacy.

Do you support SPF, DKIM, and DMARC?

Yes. All aliases — including custom domain aliases — support SPF, DKIM, and DMARC authentication. This ensures your forwarded emails have maximum deliverability and aren't flagged as spam.

What does Premium include?

Unlimited aliases, up to 5 custom domains, unlimited verified forwarding inboxes (so each alias can route to the right mailbox), send & reply from any alias, real-time leak detection with exposure analytics, and priority processing — all for $4/month or $35/year (save 27%).

How do I switch between email alias providers without losing access?

If you used a custom domain, switching is straightforward: re-create your aliases on the new provider, point your domain's MX records at their servers, and update SPF/DKIM/DMARC. Existing senders keep mailing the same addresses; only the routing changes. If you used the old provider's shared domain (e.g. @theirhost.com), those aliases die when you leave — you'd need to set up new aliases on the new provider's domain and update each site individually. Custom-domain users have vendor-independence; shared-domain users don't.

More questions? See the full FAQ.

Related reading

Adjacent guides on this topic

Email Alias Service→

Buyer's guide framing of the same category. What an alias service does, how forwarding works, and how to choose one.

Private Email Alias→

Privacy-first framing. The four pillars (zero-knowledge, AES-256, no-sell, kill-switch) and how to evaluate any provider.

Anonymous Email Forwarding→

What "anonymous" actually means here, the 5-stage forwarding pipeline, and why reply-from-alias is the trickier half.

Email Aliases for Business→

The B2B framing for custom-domain aliases — sales, support, procurement, partnerships patterns.

Email Aliases for Developers→

Programmatic DNS verification, bulk alias generation via REST API, MCP server for AI assistants.

Best Email Alias Service in 2026→

Honest opinionated roundup. 5 picks ranked by use case, with pros/cons and a 12-row feature table.

Email Alias Generator→

Random, custom-prefix, and tagged alias generation explained — and why inline browser generation beats copy-paste once you're on your custom domain.

Bring your own domain to EmailAlias

Custom domains are a Premium feature with up to 5 verified domains per account. Free plan with no credit card to start; upgrade when you're ready to add a custom domain. See plan details.

Start freeEmail Alias Service guide