Custom Domain Email: Catch-All Addresses, Unlimited Aliases & Full Privacy
Most people think custom domain email is about looking professional. An address like you@yourdomain.com instead of you@gmail.com. That's part of it. But the real value goes much deeper — into privacy, security, spam control, and total ownership of your email identity.
When you run email on your own domain, you control every aspect of it. You decide what addresses exist. You decide where they point. You decide when to walk away and take your domain somewhere else. No vendor can shut down your address, raise your price, or scan your inbox for ad targeting.
This guide covers everything you need to know about running email on your own domain: catch-all addresses, unlimited aliases, DNS authentication, sending capabilities, and how it all compares to the alternatives.
What Custom Domain Email Actually Means
Custom domain email means receiving and sending email at addresses that use a domain you own. Instead of relying on a provider's domain (@gmail.com, @outlook.com, @protonmail.com), you use your own (@yourdomain.com).
The domain itself costs around $10-15/year from any registrar. The email service that handles mail for that domain is separate. That's where most providers charge per-user monthly fees. Google Workspace starts at $6/user/month. Fastmail charges $3/user/month. Microsoft 365 starts at $6/user/month.
Reusable.Email takes a different approach: $10/year flat for catch-all routing on your domain, with no per-user or per-address fees.
The Catch-All Approach
A catch-all address receives email sent to any address at your domain, even addresses that were never explicitly created. There's no mailbox to configure, no alias to set up, no forwarding rule to write. If someone sends an email to literally-anything@yourdomain.com, it arrives.
This is fundamentally different from how most email providers work. With Google Workspace or Outlook, you create specific mailboxes or aliases. Each one has to be set up in advance. If someone emails an address that doesn't exist, it bounces.
With catch-all, nothing bounces. Every address works from the moment your domain goes live.
How It Works Technically
When someone sends you an email, their mail server looks up the MX record for your domain. That record tells it which server handles mail for your domain. The server accepts the message for any recipient address and delivers it to your inbox.
There's no wildcard DNS record involved — the magic happens at the mail server level. Reusable.Email's servers are configured to accept mail for any address at your domain and route it to your account. You see all incoming mail in one place and can filter by the address it was sent to.
For a deeper look at how catch-all works and when to use it, see What Is a Catch-All Email Address?.
Unlimited Aliases — Without Creating Them
The catch-all model gives you something that other providers either limit or charge extra for: truly unlimited aliases.
Gmail gives you dot tricks and plus addressing (you+tag@gmail.com), but many services strip the plus tag or reject it entirely. Apple's Hide My Email generates random addresses, but you're limited in how many you can create. Fastmail and ProtonMail offer alias systems, but they cap the number unless you pay more.
With your own domain and catch-all, there is no cap. Every possible address already works. You can use a different address for every service you sign up for:
netflix@yourdomain.comfor Netflixgithub@yourdomain.comfor GitHubbank@yourdomain.comfor your bankshopping@yourdomain.comfor online retailnewsletters@yourdomain.comfor email subscriptions
None of these need to be created in advance. You type them into the signup form, and they work immediately.
Why Per-Service Addresses Matter
Using a unique address per service gives you two powerful capabilities:
Spam tracing. If shopping@yourdomain.com starts receiving spam, you know the retail site you gave it to either sold your data or got breached. You can filter or ignore that specific address without affecting anything else.
Selective blocking. You can't selectively block senders when everything goes to one address. With per-service aliases, you can effectively "turn off" any address that becomes compromised, while the rest of your addresses continue working normally.
This is the same compartmentalization principle that email alias strategies are built on — but with zero limits on how many compartments you create.
DNS Setup: MX, SPF, DKIM, and DMARC
Running email on your own domain requires four DNS records. Each one serves a different purpose, and together they ensure your email is delivered reliably and can't be easily spoofed.
MX Record
The MX (Mail Exchange) record tells the internet which server handles email for your domain. Without it, no one can send you email. This is the most critical record.
yourdomain.com. MX 10 mx.reusable.email.
SPF Record
SPF (Sender Policy Framework) declares which servers are authorized to send email on behalf of your domain. Receiving servers check this record and may reject messages from unauthorized senders.
yourdomain.com. TXT "v=spf1 include:spf.reusable.email -all"
DKIM Record
DKIM (DomainKeys Identified Mail) adds a cryptographic signature to outgoing messages. The receiving server verifies this signature against a public key published in your DNS, confirming the message wasn't altered in transit and that it genuinely came from an authorized server.
reusable._domainkey.yourdomain.com. TXT "v=DKIM1; k=rsa; p=MIGf..."
DMARC Record
DMARC (Domain-based Message Authentication, Reporting & Conformance) ties SPF and DKIM together with a policy. It tells receiving servers what to do when authentication fails and optionally sends you reports about authentication attempts.
_dmarc.yourdomain.com. TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com"
Auto-Configuration
Setting up these four records manually is where most people get stuck. One typo in a TXT record and your email silently breaks.
Reusable.Email auto-generates all four records when you add your domain. The dashboard shows exactly what to paste into your registrar's DNS settings, with step-by-step guides for Cloudflare, Namecheap, GoDaddy, and every other major registrar.
For a complete technical breakdown of how these protocols work together, see SPF, DKIM, and DMARC Explained.
Sending From Your Domain
Receiving email on your domain is useful. Sending from it is essential if you want to use it as your actual email address.
With a managed inbox ($3 one-time) linked to your custom domain, you can send and reply to email from any address at your domain. The messages go out with proper SPF and DKIM authentication, so they land in recipients' inboxes rather than their spam folders.
Managed inboxes support standard email protocols:
| Protocol | Server | Port | Security |
|---|---|---|---|
| IMAP | imap.reusable.email | 993 | SSL/TLS |
| SMTP | smtp.reusable.email | 587 | STARTTLS |
| POP3 | pop3.reusable.email | 995 | SSL/TLS |
This means you can use any email client — Thunderbird, Apple Mail, Outlook, or a mobile app — to send and receive email from your custom domain. You're not locked into a web interface.
For the full setup walkthrough, see the custom domain email setup guide.
Multi-Domain Support
You're not limited to one domain. Reusable.Email supports multiple domains from a single dashboard, each at $10/year.
This is useful for:
- Separating personal and professional email. Run
@yourname.comfor personal use and@yourbusiness.comfor work. - Managing multiple projects. Each side project or brand gets its own domain and email addresses.
- Testing. Developers can set up test domains for QA environments, staging systems, or integration testing.
All domains share the same dashboard. You see all incoming mail in one place, or you can filter by domain. Each domain gets its own DNS records and authentication setup.
Custom Domain vs. Shared Disposable Domains
If you've used disposable email services before, you've probably used shared domains like @yopmail.com, @mailinator.com, or @guerrillamail.com. These work for quick throwaway signups, but they have a significant limitation: blocklisting.
Every major service maintains a blocklist of known disposable email domains. The shared domains are on all of them. Try signing up for most services with a @yopmail.com address today and you'll be rejected.
This creates an arms race. Disposable email services register new domains. Blocklists add them. Services register more. The cycle continues, and users are stuck constantly searching for a domain that hasn't been blocked yet.
Your own domain solves this permanently. A custom domain you registered yourself won't appear on any disposable email blocklist. It looks like any other personal or business domain. Services have no reason to block it — unless you specifically abuse it, which would take deliberate effort.
For more on why switching from shared domains matters, see how to stop using shared disposable email domains. And for a practical guide to using your own domain for throwaway addresses, see custom domain disposable email.
Pricing Comparison
The cost difference between custom domain email providers is significant, especially if you need multiple addresses or users.
| Provider | Price | Aliases | Catch-All | Send Support |
|---|---|---|---|---|
| Reusable.Email | $10/year | Unlimited | Yes | Yes (with managed inbox) |
| Google Workspace | $72/year per user | Limited | Paid plans only | Yes |
| Fastmail | $36/year per user | 600 max | Yes | Yes |
| ProtonMail | $48/year | 10-15 | Paid plans | Yes |
| Zoho Mail | $12/year per user | 5-50 | Paid plans | Yes |
The key difference: Reusable.Email charges per domain, not per user or per address. One flat fee covers unlimited addresses on that domain. There's no cost difference between using 3 aliases and using 300.
The managed inbox that enables sending is a separate $3 one-time purchase — not a monthly subscription.
No Lock-In
Your domain is yours. You registered it. You control the DNS. If you ever want to move away from Reusable.Email, you update your MX records to point somewhere else. That's it.
There's no migration fee. No export restriction. No 90-day notice period. You change your DNS records and your email starts flowing to the new provider within minutes.
This is the fundamental advantage of custom domain email over provider-specific addresses. If you use you@gmail.com and want to leave Google, you lose your address. If you use you@yourdomain.com, you take it with you anywhere.
Getting Started
The setup process takes about five minutes:
- Register a domain (if you don't have one already) from any registrar.
- Add the domain to your Reusable.Email dashboard.
- Configure DNS records using the auto-generated values. The dashboard provides copy-paste records and registrar-specific guides.
- Wait for verification — usually under 10 minutes.
- Start using any address at your domain immediately.
If you want to send email from your domain (not just receive), add a managed inbox for $3 one-time and configure your preferred email client with the IMAP/SMTP settings.
FAQ
How do I set up email on my own domain?
Add your domain to Reusable.Email, configure the four DNS records (MX, SPF, DKIM, DMARC) at your registrar using the auto-generated values, and wait for verification. The full process is covered in the setup guide.
What is a catch-all email address?
A catch-all address receives email sent to any address at your domain, even addresses that were never created. It eliminates the need to set up individual aliases or mailboxes. See What Is a Catch-All Email Address? for details.
How many email aliases can I have on my domain?
Unlimited. With catch-all routing, every possible address at your domain works automatically. There's no cap, no per-alias fee, and no setup required for each one.
Do I need to create each alias separately?
No. Catch-all routing means every address at your domain works from the moment your domain is verified. You don't create aliases — you just start using them.
What DNS records do I need for custom domain email?
Four records: MX (mail routing), SPF (sender authorization), DKIM (message signing), and DMARC (authentication policy). Reusable.Email generates all four automatically. You just paste them into your registrar's DNS settings.
Conclusion
Custom domain email gives you something no provider-specific address can: permanent ownership of your email identity, combined with unlimited aliases, complete privacy control, and the ability to leave whenever you want.
The traditional tradeoff was complexity for control. Running your own mail server meant managing software, security patches, and deliverability. Reusable.Email removes that tradeoff. You get the control of a custom domain with none of the operational burden — for $10/year.
Whether you want to compartmentalize your online accounts with per-service aliases, stop using blocklisted shared domains, or simply own your email address instead of renting it from a tech company, custom domain email is the foundation that makes it all work.