Running Email on Your Own Domain with Reusable.Email

Running email on your own domain used to mean setting up a mail server, configuring DNS records by trial and error, and hoping nothing breaks at 3 AM. Services like Google Workspace and Microsoft 365 simplified things but added monthly per-user costs that add up fast — $7/user/month for Google Workspace means a five-person team pays $420/year just for email.

Reusable.Email offers a different approach. For $10 per year, you can receive email at any address on your own domain — with unlimited aliases, catch-all support, and zero server management. Add a managed inbox for $3 one-time and you can send from your domain too.

This guide walks through the complete setup process, explains each DNS record you'll configure, and shows you how to get from zero to a fully functional custom domain email in about five minutes.

Why Run Email on Your Own Domain?

Before diving into the how, it's worth understanding the why. Running email on your own domain provides several advantages that provider-specific addresses can't match.

Ownership. Your domain is an asset you control. If Gmail changes its terms, raises prices, or scans your inbox for ad targeting, you can't take [email protected] somewhere else. But [email protected] goes wherever you point your DNS — today, tomorrow, or ten years from now.

Privacy. When you use @gmail.com, Google processes every message that enters and leaves your inbox. Google's privacy policy makes clear that they collect and process email content for various purposes. The Electronic Frontier Foundation has documented how major email providers analyze message content for advertising and other purposes. With your own domain pointed at a privacy-focused provider, your email stays between you and your correspondents.

Professionalism. For freelancers, small businesses, and side projects, [email protected] carries more weight than [email protected]. It signals permanence and legitimacy.

Unlimited aliases. With catch-all routing, every possible address at your domain works automatically. No caps, no pre-configuration, no per-alias fees. Use [email protected] for Netflix, [email protected] for GitHub, and invent new addresses on the fly.

Blocklist immunity. If you've used disposable email services before, you know the frustration of shared domains being blocked by websites. Your own domain won't appear on any disposable email blocklist.

How It Works

The setup process has three steps:

1. Add your domain. Enter your domain name in the Reusable.Email dashboard. The system generates the DNS records you need to configure.

2. Configure DNS. Add the provided MX, SPF, DKIM, and DMARC records to your domain's DNS settings. If you've never done this before, the dashboard includes step-by-step guides for every major registrar — Cloudflare, Namecheap, GoDaddy, Porkbun, and more.

3. Verify. Once the DNS records propagate (usually within minutes), Reusable.Email verifies the configuration and your domain goes live. Any email sent to any address at your domain will be received.

That's the entire process. No server to provision, no software to install, no firewall rules to configure. The infrastructure runs on Reusable.Email's servers — you just point your DNS records at it.

Step-by-Step DNS Configuration

DNS configuration is where most people feel intimidated, but it's actually straightforward. You're adding four records to your domain's DNS settings, and Reusable.Email generates the exact values for each one.

Step 1: The MX Record

The MX (Mail Exchange) record is the most important record. It tells the internet which server handles email for your domain. Without it, email sent to your domain has nowhere to go.

yourdomain.com.  MX  10  mx.reusable.email.

In your registrar's DNS panel, you'll typically fill in:

• Type: MX
• Name/Host: @ or blank (represents your root domain)
• Value/Points to: mx.reusable.email
• Priority: 10
• TTL: 3600 (or "Auto")

Step 2: The SPF Record

SPF (Sender Policy Framework) tells receiving servers which mail servers are authorized to send email on behalf of your domain. Without SPF, emails you send may be flagged as suspicious or rejected outright.

yourdomain.com.  TXT  "v=spf1 include:spf.reusable.email -all"

In your registrar's DNS panel:

• Type: TXT
• Name/Host: @ or blank
• Value: v=spf1 include:spf.reusable.email -all
• TTL: 3600

The -all at the end means "reject all mail from servers not listed." This is the strictest (and most secure) SPF policy.

Step 3: The DKIM Record

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to every outgoing email. The receiving server verifies this signature against a public key published in your DNS, confirming the message is authentic and unaltered.

Reusable.Email generates a unique DKIM key for your domain. The record looks something like:

reusable._domainkey.yourdomain.com.  TXT  "v=DKIM1; k=rsa; p=MIGf..."

In your registrar's DNS panel:

• Type: TXT
• Name/Host: reusable._domainkey
• Value: The full DKIM value provided by the dashboard (it will be a long string)
• TTL: 3600

Step 4: The DMARC Record

DMARC (Domain-based Message Authentication, Reporting & Conformance) ties SPF and DKIM together. It tells receiving servers what to do when authentication checks fail, and optionally sends you reports about who's trying to send email as your domain.

_dmarc.yourdomain.com.  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]"

In your registrar's DNS panel:

• Type: TXT
• Name/Host: _dmarc
• Value: The DMARC policy provided by the dashboard
• TTL: 3600

Verification

After adding all four records, return to the Reusable.Email dashboard and click verify. The system checks that each record is correctly configured. DNS propagation usually takes under 10 minutes, though in rare cases it can take up to 48 hours.

If verification fails, the dashboard tells you exactly which record has a problem and what the expected value should be. The most common issues are:

• Trailing periods — some registrars add these automatically, others don't
• Quote marks — TXT record values should include the quotes in some registrars but not others
• Conflicting MX records — if your domain previously had MX records pointing elsewhere, you may need to remove them

Catch-All by Default

One of the most useful features of custom domain support is catch-all receiving. You don't need to create individual addresses or aliases ahead of time. Send an email to [email protected], and it arrives.

This means you can give every service a unique address without any setup:

• [email protected] for Netflix
• [email protected] for GitHub
• [email protected] for retail accounts
• [email protected] for a one-off free trial

If one of those addresses starts receiving spam, you know exactly which service leaked it. You can filter or ignore that specific address without affecting any others.

For naming strategies and best practices for organizing your aliases, see our email templates guide. For a deep dive into how catch-all works technically, see What Is a Catch-All Email Address?.

Sending From Your Domain

Receiving email is half the picture. With a managed inbox ($3 one-time) linked to your custom domain, you can send email that appears to come from your domain. The SPF and DKIM records ensure that your messages pass authentication checks and land in recipients' inboxes, not their spam folders.

Configuring Your Email Client

After creating a managed inbox, configure your email client with these settings:

Incoming Mail (IMAP):

• Server: imap.reusable.email
• Port: 993
• Security: SSL/TLS
• Username: Your full email address
• Password: Your managed inbox password

Outgoing Mail (SMTP):

• Server: smtp.reusable.email
• Port: 587
• Security: STARTTLS
• Username: Your full email address
• Password: Your managed inbox password

These settings work with every major email client:

Client	Platform	Configuration
Apple Mail	macOS, iOS	Settings > Mail > Add Account > Other
Thunderbird	Windows, macOS, Linux	Auto-detects with email and password
Outlook	Windows, macOS, web	Settings > Add Account > Advanced
K-9 Mail	Android	Add Account > Manual Setup
Spark	macOS, iOS, Android	Add Account > Other
Gmail (app)	Android, iOS	Settings > Add Account > Other

This is particularly valuable for freelancers, small businesses, and side projects that need professional-looking email without the infrastructure investment. For a comparison of why this approach beats running your own mail server, see the white-label email service guide.

DNS Authentication Explained

Email authentication prevents others from spoofing your domain — sending emails that appear to come from you but actually come from an attacker's server. Reusable.Email configures three protocols automatically:

SPF declares which servers are allowed to send email for your domain. Receivers check this record and reject unauthorized senders. Without SPF, anyone could send an email that appears to come from [email protected].

DKIM adds a cryptographic signature to every email. The receiving server verifies the signature against a public key in your DNS, confirming the message wasn't altered in transit and genuinely came from an authorized server. Think of it as a tamper-evident seal on your messages.

DMARC provides a policy for what happens when SPF or DKIM checks fail. It also enables reporting so you can monitor who's attempting to send email as your domain. This is your early warning system for spoofing attempts.

Together, these three protocols ensure that:

1. Only authorized servers can send email from your domain
2. Messages can be verified as authentic and unaltered
3. Failed authentication attempts are handled according to your policy
4. You receive reports about authentication activity

For the full technical details on each protocol, see SPF, DKIM, and DMARC Explained.

Multi-Domain Support

You're not limited to a single domain. Each additional domain is $10/year. All domains are managed from the same dashboard, with unified inbox access across all of them.

This is useful for:

• Separating personal and business email
• Running multiple projects or brands
• Testing email delivery across different domains
• Managing client domains if you're an agency (see white-label email hosting)

Each domain gets its own DNS records, its own authentication setup, and its own catch-all routing. You can view all incoming mail in a unified view or filter by domain.

Common Setup Questions

What if I already have email on this domain?

If your domain currently has MX records pointing to Google Workspace, Zoho, or another provider, you'll need to update them to point to Reusable.Email instead. This means email will stop flowing to the old provider. Plan your migration accordingly — update account emails before switching MX records if you need to maintain continuity.

Can I use subdomains?

Yes. You can set up email on mail.yourdomain.com or any other subdomain while keeping your root domain's email with another provider. This is useful for testing or for creating a separation between your primary email and your alias system.

What registrars work with this?

All of them. Reusable.Email works with any domain registrar that lets you edit DNS records. The dashboard includes step-by-step guides for the most popular ones: Cloudflare, Namecheap, GoDaddy, Porkbun, Google Domains, Hover, and more.

How long does DNS propagation take?

Usually under 10 minutes. In rare cases, it can take up to 48 hours, depending on your registrar and the TTL values of any existing records. If verification fails after 10 minutes, wait an hour and try again.

What You Keep

Your domain is yours. If you ever decide to move away from Reusable.Email, you update your DNS records and point them elsewhere. There's no lock-in, no migration fee, and no data held hostage. You can export your emails at any time.

This portability is the single biggest advantage of custom domain email. Your email address is an identity that follows you regardless of which provider handles the infrastructure. Compare this to [email protected], which is permanently tied to Google's platform.

Frequently Asked Questions

How much does it cost to run email on my own domain?

The domain itself costs $10-15/year from a registrar. Catch-all routing on Reusable.Email costs $10/year. A managed inbox for sending costs $3 one-time. Total first-year cost: approximately $25. Annual renewal: approximately $20-25.

Do I need technical knowledge to set this up?

Basic familiarity with DNS settings helps, but it's not required. The Reusable.Email dashboard generates all the records you need and includes registrar-specific guides with screenshots. Most users complete the setup in under 10 minutes.

Can I send email from my custom domain?

Yes, with a managed inbox ($3 one-time). You get full SMTP access and can send from any address at your domain through any standard email client. Messages are authenticated with SPF and DKIM to ensure deliverability.

What happens if I don't renew my domain?

If your domain registration lapses, all email to that domain stops working. This is true regardless of which email provider you use. Set up auto-renewal with your registrar to prevent this.

Can multiple people use email on the same domain?

Yes. You can create multiple managed inboxes under the same domain, each with its own credentials. All inboxes share the same catch-all routing, so incoming mail for any address is received. Multiple users can each have their own managed inbox for sending.

Conclusion

Custom domain email doesn't need to be complicated or expensive. The goal is simple: professional email at your domain, with zero maintenance and full control over your addresses.

The setup takes five minutes. The annual cost is roughly $20-25. And the result is an email system that you own completely — unlimited aliases, catch-all routing, proper authentication, standard email client access, and the freedom to move to any provider at any time.

Your email address is one of the most important digital assets you own. It's worth spending $20/year to make sure you actually own it.