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.
What is a custom domain email alias?
A regular email alias lives on the provider's domain — addresses like k7-bright-river@emailalias.io. A custom domain email alias is the same idea, but the alias address belongs to a domain you own, like contact@yourdomain.com or stripe@yourdomain.com. Mail sent to that address forwards to your real inbox; the sender only ever sees the custom-domain 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 to maintain. Your DKIM signature, your SPF record, your DMARC policy. A misconfigured shared domain can't poison your reputation.
Why use your own domain instead of a shared one?
Shared-domain aliases (the @emailalias.io kind) are perfect for personal use — quick, anonymous, and disposable in the casual sense. A custom domain email alias makes sense once any of the following apply:
- You're using aliases for work or client communication. “Email me at
contact@yourdomain.com” reads as professional.contact@randomprovider.ioraises eyebrows. - You want vendor independence. If you switch alias providers later, the domain stays — the aliases keep working with whoever runs them next, no migration required from your side.
- You care about deliverability long-term. A custom domain lets you publish your own SPF, DKIM, and DMARC records and own the sending reputation.
- You want unlimited per-alias addresses on a single domain. A wildcard
*@yourdomain.commeans every signup on the internet can have its own alias without any pre-registration step. - You're running multiple personas. Separate domains for personal, freelance, and business mail — same inbox, totally separate sender identities.
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 in their dashboard, and the domain becomes available for minting aliases. Setup typically takes 10 minutes plus DNS propagation time. EmailAlias.io's flow is in the Domains section of the dashboard.
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.
What to look for in a custom domain alias provider
Before you point your domain's MX records anywhere, run the following checklist:
- Real custom-domain support, not subdomain. The provider should accept any domain you own and walk you through the DNS setup.
- SPF, DKIM, and DMARC enforcement on every alias on your custom domain. Anything less means forwarded mail might land in spam.
- Wildcard / catch-all support. So
anything@yourdomain.comworks without pre-registering each address. - Send-from-alias from the custom domain, not just receive. Replies should appear to come from the alias address, with a DKIM signature aligned to your domain.
- Programmatic API for adding/rotating aliases on the custom domain. If you ever want to script this, the API is what matters.
- How many domains can you add? One is fine for personal use; multiple is better if you're running personas (personal, freelance, business).
- Deliverability transparency. Look for actual SPF/DKIM/DMARC documentation, not just a marketing claim.
- Encryption at rest on the alias-mapping database. Custom-domain aliases are no less sensitive than shared-domain ones.
How EmailAlias.io handles custom domains
Custom domain support is a Premium feature on EmailAlias.io. Concretely, here's what you get when you bring your own domain:
- Up to 5 custom domains per account, each independently verified.
- Guided DNS setup — paste-ready MX, SPF, DKIM, and DMARC records, plus a one-click verify check.
- Catch-all aliases — receive mail at any address on your domain without pre-creating it. Useful for unique-per-signup patterns.
- Send and reply from any custom-domain alias. Replies are DKIM-signed by your domain, so recipients see a properly authenticated reply.
- Per-alias controls — disable, rotate, or delete any individual alias on the custom domain in one click.
- Suspicious-sender intelligence on incoming mail to custom-domain aliases — same exposure events you get on shared-domain aliases.
- REST API + MCP server for programmatic alias management on custom domains, including alias rotation from scripts and AI assistants.
- AES-256 at rest for alias mappings and metadata. Security architecture →
Full feature breakdown is on the Email Alias Service guide and the Private Email Alias guide.
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.
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. This is one of the strongest reasons to set up a custom domain even on a free tier — it's vendor-independence insurance.
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, up to 5 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 $38.40/year (save 20%).
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.
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.
Best Email Alias Service in 2026→
Honest opinionated roundup. 5 picks ranked by use case, with pros/cons and a 12-row feature table.
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.