Custom Domain Email: What It Is and How to Get It Right

Custom domain email is email that uses a domain name you own, such as you@yourcompany.com, rather than a provider's domain like gmail.com. To get it you need two things: a registered domain and an email hosting service. You then add a few DNS records (MX, SPF, DKIM, DMARC) at your domain so the world knows where to deliver your mail and that it's genuine.

Why a custom domain matters

A custom domain is more than branding. It decides who controls your email identity.

Portability. The address belongs to your domain, not to a provider. If you change hosts, you update DNS and keep the same addresses. Nobody has to update their contacts.
Control. As the domain owner, you decide who gets an address, what happens when someone leaves, and which services are allowed to send mail on your behalf.
Credibility. Clients, suppliers and banks are more likely to trust and reply to mail from @yourcompany.com. A free address on an invoice or contract is a common red flag for fraud.
Organisation. You can create role addresses (sales@, support@, billing@) that survive staff changes and route to the right people.

Even a one-person business benefits: you@yourname.com follows you for decades, whereas a free address is tied to one company's terms of service.

What you need before you start

Item	What it is	Where you get it
Domain name	e.g. example.com	Any domain registrar
DNS access	Ability to add records for the domain	Usually your registrar, or a DNS host like Cloudflare
Email hosting	The service that stores and sends your mail	A business email provider
10–30 minutes	For the DNS changes	You, or your IT person

You do not need a website. The domain can point mail to one provider and the website to another; the two are independent.

If you're starting from zero, pick a domain that is short, easy to say over the phone, and without hyphens or tricky spellings. Register it in the company's name and turn on auto-renew: an expired domain means your mail stops arriving.

The DNS records behind custom domain email

DNS is the internet's public address book. For email, a handful of records do the work:

TXT (verification) — proves to your provider that you control the domain.
MX — tells other mail servers where to deliver mail for your domain.
SPF — a TXT record listing the servers allowed to send as your domain.
DKIM — a public key (often published via CNAME) that lets receivers verify your messages' signatures.
DMARC — a TXT record at _dmarc telling receivers what to do with mail that fails SPF/DKIM checks, and where to send reports.

A typical set looks like this (values vary by provider):

example.com.          MX    10 mx.provider.example.
example.com.          TXT   "v=spf1 include:_spf.provider.example ~all"
selector1._domainkey  CNAME selector1.dkim.provider.example.
_dmarc.example.com.   TXT   "v=DMARC1; p=none; rua=mailto:dmarc@example.com"

Two rules people often trip over:

Only one SPF record per domain. If you also send through a newsletter tool or a billing system, merge their include: entries into a single SPF record. SPF also has a limit of 10 DNS lookups; too many includes and SPF fails.
**Start DMARC at p=none, then tighten.** Watch the reports for a couple of weeks to find every legitimate sender, then move to p=quarantine and eventually p=reject.

Optional but valuable: autoconfig/autodiscover and SRV records (so email apps can find settings automatically) and MTA-STS/TLS-RPT (so other servers must use encrypted connections when delivering to you).

Step-by-step: setting it up

Sign up with an email host and add your domain.
Verify the domain with the TXT record the host gives you.
Add MX, SPF, DKIM and DMARC. Copy each value exactly. Some hosts can apply all records automatically if your DNS provider supports it.
Wait for DNS to update. Often minutes, sometimes a few hours.
Check the records. A good provider shows a green or red status for each one.
Create mailboxes, aliases and groups.
Connect your apps — webmail, phone, Outlook or Apple Mail.
Import old mail if you're moving from another service.

We go through this in detail in how to create email with your own domain.

Ways to get custom domain email

There are three common routes, each with trade-offs.

Email included with web hosting (cPanel and similar). Cheap and convenient if you already have hosting. Quality varies a lot between hosts: shared servers can end up on blocklists because of another customer's behaviour, and features like DMARC reporting, strong phishing protection or calendar sync are often limited.

Large productivity suites (Google Workspace, Microsoft 365). Mature, reliable, well integrated with their own document tools, and supported by almost every third-party app. They are excellent if you want their full ecosystem. Some small teams find them more than they need, or prefer a different vendor for privacy or cost reasons.

Dedicated business email providers. Services such as Zoho Mail, Fastmail, Proton and others focus on email plus a smaller set of collaboration tools. They range from privacy-focused to budget-focused. Compare support for standard protocols, migration tools and admin features.

Whichever you choose, insist on standard protocols (IMAP, SMTP, CalDAV, CardDAV). They are your guarantee that you can leave later, taking every message with you.

Mistakes to avoid

Letting the domain lapse. Set auto-renew and keep the registrar login somewhere safe that more than one person can access.
Registering the domain to a freelancer's personal account. It should belong to the company.
Two SPF records. Receivers treat it as an error; merge them.
Leaving old MX records in place. Remove the previous provider's MX entries when you switch, or some mail will keep going to the old service.
Never looking at DMARC reports. They tell you if someone is spoofing your domain.
Using a catch-all as your main inbox. Catch-all addresses attract a lot of spam. Use them sparingly, if at all.

Getting custom domain email with Zomail

With Zomail you keep your domain at your current registrar. The guided DNS page lists every record — verification TXT, MX, SPF, DKIM (two CNAMEs, with keys rotated automatically), DMARC, autodiscover, SRV and MTA-STS — and checks each one for you. You can download a zone file to import into a DNS host like Cloudflare, or use one-click Domain Connect setup where your DNS provider supports it. The getting started guide walks through the screens, and pricing is per mailbox per month, shown live on the page.

FAQ

Can I use a custom domain with Gmail?

A personal Gmail account can be set up to send as another address, but receiving, security and admin control are limited. For real custom domain email you need a business email service that hosts mail for your domain, such as Google Workspace or another provider.

Do I have to move my domain to my email provider?

No. You can keep the domain at any registrar. You only need to add or change DNS records there. Moving the domain is optional.

How much does custom domain email cost?

You pay for the domain (usually yearly) and for the email service, which is commonly priced per mailbox per month. Plans differ in storage, security features and extras, so compare what's included rather than headline price alone. See also what business email is.

Will changing MX records cause me to lose email?

Not if you plan it. Create mailboxes first, lower the DNS TTL a day before, then switch MX. During propagation some mail may still reach the old provider, so keep it active for a few days and import anything that arrives there. Our migration guide explains the steps.

Can one domain use two email providers?

Only one set of MX records should be active, so one provider receives the mail. Other services can still send as your domain if they are included in your SPF record and sign with DKIM.