Email hosting versus web hosting: keep them apart

Website and email are different services with different failure modes. Why bundling them on one account is a risk, and how to separate them.

3 minread 636words last updated

The short answer

A website serves pages to the public. Email stores private correspondence and delivers it reliably to other people’s servers. They are different services with different security needs, different failure modes and different providers who are good at them. Bundling them on one shared hosting account, as many packages do, means a compromised website can take your email down, a migration of one disrupts the other, and your deliverability depends on the reputation of a server you share with strangers. Keep them apart: a dedicated email provider, a modern web platform, and DNS pointing each where it belongs.

Why they do not belong together

ConcernBundled on one accountSeparated
A website compromiseAttackers reach the mail server; mailboxes and outgoing mail at riskThe website incident stays a website incident
DeliverabilityShared server IP reputation, often poor; your mail lands in spam because of a neighbourA provider whose whole business is getting mail delivered
MigrationsMoving the site risks the mail records; moving mail risks the siteEach moves independently
SupportHosting support, for whom mail is an afterthoughtEmail specialists
Spam filtering and securityBasicModern filtering, two-factor, device management, retention controls
UptimeBoth down togetherIndependent

Separating them, step by step

  1. Choose a dedicated email provider with business plans, two-factor, good mobile sync and support.
  2. Create the mailboxes and aliases there, matching the existing ones.
  3. Lower the time-to-live on the current mail records a day ahead, so the switch propagates quickly.
  4. Migrate existing mail into the new mailboxes while the old ones still receive.
  5. Switch the mail records to the new provider in a quiet window; set up the sending authentication records for the new provider.
  6. Run both in parallel for a day; check that new mail arrives at the new provider and that sending works.
  7. Retire the old mailboxes after a final sync, and remove the old mail records.

The pattern we recommend

Domain at a registrar in your name. DNS at a network layer that is fast to change. Website on a modern platform. Email at a dedicated provider. Transactional email from the website, such as form notifications and confirmations, through a sending service with its own authentication records, so the website never sends through your mailboxes. Four services, each doing one thing, each replaceable without touching the others.

What this means for you

Email is how customers reach you and how you reach them; it deserves its own provider, not a checkbox on a hosting package. Separate it from the website, plan the DNS change carefully, and let each service do one job. Then a website incident stays a website incident, migrations stop breaking mail, and your messages arrive where they are sent.

Written by the CivSec S.M.A.R.T team

We build and run websites, software and AI systems for businesses. We write about what we see in that work, in plain language, and we update articles when things change.

Last checked . Spotted something outdated? Tell us.

Frequently asked questions

Our hosting package includes email for free. Why pay separately?

Because the included email is usually the weakest part of the package: shared server reputation, limited spam filtering, poor mobile sync, no real support, and it goes down with the website. A dedicated email provider costs a small amount per mailbox and removes all of those. Email is how customers reach you; it should not be an add-on.

Will we lose emails during a move?

Not if it is planned. Mailboxes are migrated while the old ones still receive; the DNS records for mail are changed with a low time-to-live; both run in parallel for a day; then the old is retired. Done in a quiet window, users notice a new login and nothing else.

Does moving the website affect our email?

Only if the mail records are changed by mistake, which is the most common way website migrations break email. Keep email on its own provider and touch only the web records when moving the site. Separation makes each migration independent of the other.