Using a @gmail.com or @outlook.com address for your business isn't just unprofessional — it's a deliverability risk. More email providers and spam filters in 2026 are using sender domain reputation as a signal. A custom domain gives you control over that reputation.

We're the JustEmails team — JustEmails is built by Velocity Digital Labs, and it's the email host we use across every product we run, from support inboxes to founder aliases. We've helped enough people set custom domain email up that we know where it gets confusing. This guide covers the whole process: choosing a provider, configuring DNS, setting up authentication (SPF, DKIM, DMARC), and testing. Real records, real commands, real pricing.

Let's get into it.

Step 1: Pick Your Email Provider

You've got more options than you think. Here's an honest breakdown of pricing as of April 2026:

Google Workspace — $7.20/user/month (Business Starter). The default choice for a reason. 30GB storage per user, full Google suite (Docs, Sheets, Drive, Meet), excellent deliverability, and every email client in the world supports it. Downsides: you're giving Google access to your email content for ad targeting (they say they stopped scanning Workspace emails, but the privacy-conscious won't love it), and the admin console is a sprawling maze once you get past basic setup.

Microsoft 365 — $6/user/month (Business Basic). Outlook, Teams, OneDrive, SharePoint. If your team already lives in the Microsoft ecosystem, this is the obvious pick. Exchange Online's deliverability is strong. Downsides: the admin portal has about 47 different settings panels and none of them agree on where to find DNS records.

Zoho Mail — Free for up to 5 users (5GB/user), or $1/user/month for the paid tier. Surprisingly good for the price. Their webmail interface is clean, and they support custom domain email on the free plan — something Google and Microsoft dropped years ago. Downside: deliverability isn't quite as strong as Google or Microsoft (some recipients' spam filters are less familiar with Zoho's IP ranges), and the ecosystem of third-party integrations is thinner.

Fastmail — $5/user/month (Standard). Privacy-focused, based in Australia, no advertising, no data mining. Excellent IMAP support, very fast webmail. Good choice for people who want solid email without the productivity suite baggage. Downside: no video calling, no document collaboration, no integration ecosystem to speak of. It's just email. (Some people consider that a feature.)

Proton Mail — $4.99/user/month (Mail Plus, annual billing). End-to-end encrypted. Based in Switzerland. If privacy is your top priority, this is the one. Downside: the encryption means you can't use standard IMAP with regular email clients without their Bridge app, which adds friction. And some of the enterprise email features (shared mailboxes, advanced routing) lag behind Google and Microsoft.

JustEmails — our product, so we'll be upfront about the bias. $49/year flat (about $4.08/month) for unlimited domains and unlimited email accounts on one account, with auto SPF/DKIM/DMARC setup, 10 GB of included storage (expandable in 100 GB blocks at $100/year each), and a bundled transactional email API (1,000 emails/month free, $25/year per 10K-email tier). We're newer and smaller than all the options above. Our strength is the flat annual price and unlimited domains. Our weakness is that we don't have a productivity suite — no docs, no spreadsheets, no video calls, no calendar/contacts, no native mobile apps. If you need email and only email, we're a solid option. If you need the full workspace, Google or Microsoft is the better choice.

Step 2: Add Your Domain to the Provider

Every provider has a slightly different onboarding flow, but the core steps are identical:

Sign up for the provider
Enter your domain name (e.g., yourbusiness.com)
The provider will give you DNS records to add
You add those records at your domain registrar or DNS host
The provider verifies ownership
Email starts working

The DNS part is where most people get confused. Here's how it works.

Step 3: Configure DNS Records

You'll need access to your DNS management panel. This is wherever you bought your domain (Namecheap, GoDaddy, Google Domains/Squarespace, Cloudflare, etc.).

MX Records (Mail Exchange)

MX records tell the internet where to deliver email for your domain. Your provider will give you these. Here's what they look like for the major providers:

Google Workspace:

Priority  Host    Value
1         @       ASPMX.L.GOOGLE.COM
5         @       ALT1.ASPMX.L.GOOGLE.COM
5         @       ALT2.ASPMX.L.GOOGLE.COM
10        @       ALT3.ASPMX.L.GOOGLE.COM
10        @       ALT4.ASPMX.L.GOOGLE.COM

Microsoft 365:

Priority  Host    Value
0         @       yourdomain-com.mail.protection.outlook.com

(Microsoft gives you a unique subdomain during setup.)

Zoho Mail:

Priority  Host    Value
10        @       mx.zoho.com
20        @       mx2.zoho.com
50        @       mx3.zoho.com

Important: Delete any existing MX records before adding new ones. Having old MX records pointing to a previous provider alongside your new ones will cause some emails to go to the wrong place. This is the single most common mistake we see.

TXT Record for Domain Verification

Before the provider activates email, they need to verify you own the domain. They'll give you a TXT record to add. It looks something like:

Host: @
Type: TXT
Value: google-site-verification=abc123xyz456...

Or for Microsoft:

Host: @
Type: TXT
Value: MS=ms12345678

Add it, wait 5-30 minutes for DNS propagation, then click "Verify" in your provider's admin panel. If verification fails, wait longer — DNS propagation can take up to 48 hours in some cases, though usually it's under an hour.

Step 4: Set Up Email Authentication (The Part Most People Skip)

This is where it actually matters. SPF, DKIM, and DMARC are the three authentication protocols that tell receiving email servers "yes, this email legitimately came from this domain." Without them, your emails land in spam. Or get rejected entirely.

Google and Yahoo made SPF and DKIM mandatory for bulk senders starting February 2024. DMARC is technically optional but increasingly expected. If you're sending more than a few dozen emails a day — newsletters, transactional emails, sales outreach — you need all three.

SPF (Sender Policy Framework)

SPF tells receiving servers which IP addresses are allowed to send email on behalf of your domain. It's a TXT record.

For Google Workspace:

Host: @
Type: TXT
Value: v=spf1 include:_spf.google.com ~all

For Microsoft 365:

Host: @
Type: TXT
Value: v=spf1 include:spf.protection.outlook.com ~all

For Zoho:

Host: @
Type: TXT
Value: v=spf1 include:zoho.com ~all

Critical detail: You can only have ONE SPF record per domain. If you're using multiple services that send email (e.g., Google Workspace for team email plus Mailchimp for newsletters plus your app for transactional emails), you combine them into a single record:

v=spf1 include:_spf.google.com include:servers.mcsv.net include:sendgrid.net ~all

Having multiple SPF records doesn't just fail — it can cause ALL your email authentication to break. We see this mistake constantly. If we had to pick the single most common email deliverability issue, it's duplicate SPF records.

DKIM (DomainKeys Identified Mail)

DKIM adds a cryptographic signature to your outgoing emails that proves they haven't been tampered with in transit. Your provider generates the signing key; you publish the public key as a DNS record.

The setup process varies by provider:

Google Workspace: Admin Console > Apps > Google Workspace > Gmail > Authenticate Email. Google gives you a TXT record to add. It'll look like v=DKIM1; k=rsa; p=MIIBIjANBgkq... with the host being google._domainkey.
Microsoft 365: Defender portal > Policies > DKIM. Enable signing for your domain. You'll add two CNAME records.
Zoho: Mail Admin Console > Domain > DKIM. Generate the key, add the TXT record.

DKIM is the one people skip because the records look intimidating (they're long strings of encoded key data). Don't skip it. Without DKIM, your SPF can still pass, but your DMARC alignment won't work properly — and that's what matters for deliverability in 2026.

DMARC (Domain-based Message Authentication, Reporting, and Conformance)

DMARC ties SPF and DKIM together and tells receiving servers what to do when authentication fails. It also sends you reports about who's trying to send email as your domain.

Start with a monitoring-only policy:

Host: _dmarc
Type: TXT
Value: v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com; fo=1

This doesn't block anything — it just collects data. You'll receive XML reports (ugly but useful) showing every source that sent email claiming to be from your domain. Run this for 2-4 weeks.

After you're confident that all legitimate email sources are passing SPF and DKIM, tighten the policy:

v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@yourdomain.com; fo=1

This sends failing emails to spam. And eventually:

v=DMARC1; p=reject; rua=mailto:dmarc-reports@yourdomain.com; fo=1

This outright rejects failing emails. Don't jump to p=reject on day one — you'll block your own legitimate email if anything is misconfigured. We've watched people do this. It's not pretty when your entire company's outgoing email starts bouncing.

Step 5: Test Everything

Don't just hope it works. Verify.

MXToolbox (mxtoolbox.com) — Free. Enter your domain and check MX records, SPF, DKIM, and DMARC. It'll flag misconfigurations in plain English.

Mail-tester.com — Free (up to 3 checks per day). Send an email to their test address and get a deliverability score out of 10. Anything below 7 means you've got issues.

Google Postmaster Tools — Free. If you send volume to Gmail recipients, this shows you your domain's reputation, spam rate, and authentication pass rates. Takes a few days to populate data.

The manual test: Send an email from your new custom domain address to a Gmail account, an Outlook account, and a Yahoo account. Check if it lands in inbox or spam. Check the email headers (in Gmail: three dots > "Show original") and verify that SPF, DKIM, and DMARC all show "PASS."

If any of them show "FAIL" or "NEUTRAL," go back and check your DNS records. The most common issues:

SPF: typo in the include value, or multiple SPF records
DKIM: wrong selector name (google._domainkey vs default._domainkey)
DMARC: missing underscore in _dmarc hostname

Common Mistakes We See Constantly

Leaving old MX records in place. If you switched from one provider to another and didn't delete the old MX records, some emails go to the old provider and some go to the new one. Delete the old records.

Multiple SPF records. One domain, one SPF record. Combine multiple senders into a single record using include: directives.

Not setting up DKIM. SPF alone isn't enough in 2026. Google and Yahoo's sender requirements made this clear. Set up DKIM.

Jumping to DMARC reject. Start with p=none, graduate to p=quarantine, then p=reject. In that order. Over weeks, not minutes.

Not testing after changes. DNS changes can take up to 48 hours to propagate. Test at multiple intervals. Don't assume it's working because it worked once.

Contrarian take: most small businesses overthink email hosting. If you're a team of 1-5 people and you don't need the Google or Microsoft productivity suite, a flat-fee provider like JustEmails ($49/year for the whole account) or Zoho's free tier is perfectly fine. The deliverability difference between Google Workspace and a properly configured Zoho or JustEmails account is minimal. What matters is getting SPF, DKIM, and DMARC right — which is the same work regardless of provider. Don't pay $7.20/user/month for Google Workspace just because it's Google if all you need is email.

That said — if you do need Docs, Sheets, Drive, and Meet, then Google Workspace's email is basically a free bonus on top of a productivity suite you'd be paying for anyway. Context matters.

If you're curious how we use JustEmails internally — every inbox across ClickzProtect, JustAnalytics, and the rest of our products runs on JustEmails — we wrote about the whole stack here.

Got questions about setup? We're at support@justemails.app. We answer email. (Obviously.) More posts on the JustEmails blog.

Frequently Asked Questions

How long does it take to set up custom domain email?

Roughly 30-60 minutes of hands-on work, plus DNS propagation (which can take 1-24 hours but is usually under an hour with modern registrars like Cloudflare or Namecheap). Account creation: 5 min. DNS records (MX, SPF, DKIM, DMARC): 15 min. Mail client setup: 10 min. The longest step is verifying everything lands correctly with a test email round-trip.

What DNS records do I need for custom domain email?

Five records minimum: (1) MX records pointing to your provider's mail servers, (2) SPF (TXT record) listing authorized senders, (3) DKIM (CNAME or TXT) for cryptographic signing, (4) DMARC (TXT) for policy enforcement, and optionally (5) BIMI (TXT) to display your logo in Gmail. Skipping DKIM or DMARC will land your mail in spam at Gmail and Outlook.

Can I use Gmail's interface with a custom domain on JustEmails?

Yes — JustEmails supports IMAP and SMTP, which Gmail can connect to via 'Send mail as' and 'Check mail from other accounts'. Setup is in Gmail Settings → Accounts. You get to keep Gmail's interface and search while sending and receiving from your custom domain. Many small business owners run this exact setup.

What's the cheapest way to host custom domain email in 2026?

Flat-rate providers like JustEmails ($49/year flat for unlimited domains and unlimited mailboxes) and MXroute (~$45/year all-in) beat per-user pricing from Google Workspace ($7/user/month) and Microsoft 365 ($6/user/month) at any team size over 1-2 users. For solo founders, even Zoho Mail's free tier ($0 for 5 users on one domain) works — but throughput limits hit fast.

Try JustEmails

Unlimited custom domain email hosting for $49/year flat — unlimited domains, unlimited mailboxes, 10 GB storage, full IMAP/SMTP. Built for agencies, freelancers, and anyone managing email across more than one domain.

Start your 7-day free trial → · How it compares

The Complete Guide to Setting Up Custom Domain Email in 2026