Blog / How the internet works /

Email and website on the same host: pros and cons

When you buy hosting, the plan often comes with email addresses at your own domain: you@yourbusiness.com. It’s convenient and sometimes free. It’s also a decision with consequences, because if the website and email share one host, they share its problems.

Here is how to think about it.

First, how they connect

Your website and your email are two different services that happen to use the same domain name. Which server answers for each is set in DNS, the internet’s address book. Two kinds of records matter:

  • A or CNAME records point your domain to the server that shows your website.
  • MX records point your domain to the server that receives your email.

Those can point to the same place or to completely different ones. The domain name doesn’t care. I explained the address-book idea in DNS explained for people who just want their site to work, and the wider setup in DNS, SSL and Cloudflare: what site owners should know.

So “email on the same host” means you’ve set the MX records to point at the web host’s mail server, usually using cPanel or a similar control panel.

The pros

It’s simple

One company, one bill, one login. For a new business with a small budget, an inbox that comes with the hosting plan is an easy start.

It’s often cheap or included

Many shared hosting plans include a number of mailboxes at no extra charge. Compared with paying per user for a separate email service, that can matter when money is tight.

Setup is quick

Create an address in the control panel, connect it to a mail app or use webmail. Done in minutes.

Everything is in one place

For a one-person business, having site and mail in a single dashboard is less to remember.

The cons

One failure takes out both

If the host goes down, you lose the website and the email at the same moment. When your site is down, you most want to be able to email customers to tell them. If the same outage breaks that, you’re in the dark. I listed other causes in why websites go down.

Deliverability can suffer

This is the big one. When your email leaves a shared server, receiving systems judge it partly by the reputation of the server’s address. On shared hosting, other customers on the same server may send spam or have compromised accounts, and your messages inherit some of the damage. Result: your invoices and quotes land in spam.

Email also needs proper authentication records. In plain terms:

  • SPF lists which servers may send mail for your domain.
  • DKIM adds a signature that proves the message wasn’t altered.
  • DMARC tells receivers what to do with mail that fails those checks.

Dedicated email services tend to guide you through these. On a web host, you may have to set them up yourself, and plenty of people never do. Large mailbox providers have also announced stricter rules for bulk senders from early 2024, which makes proper authentication more important, not less.

Limited features

Hosting mail often means basic webmail, modest storage and weak spam filtering. Calendars, shared inboxes, good search, mobile sync and admin controls are usually better on dedicated platforms.

Security and access

If someone gets into your hosting account, they may reach your mailboxes too. A single weak password protects everything. Separating them limits the damage.

Migration headaches

If you later move your website to a new host, the email may need to move too, or you must carefully keep the MX records pointing to the old one. Mistakes during a move are a common reason for lost mail. See hosting migrations without losing rankings for the website side of this. Keeping mail separate makes those moves simpler, because the website can change hosts without touching the mailboxes.

Sending from your site

Contact forms, order notifications and password resets also send email, often through the web server. If those use the same server’s mail function, they can fail or land in spam. Many sites fix this by sending site email through a proper email service instead.

When same-host email is fine

  • A brand-new hobby or personal site where email is light.
  • A small business that sends few emails and receives mostly enquiries.
  • A temporary setup while you decide on something better.
  • A project where cost is the main limit and you keep backups.

When to separate them

  • Your business depends on email for sales, quotes or bookings.
  • You email customers in volume, such as newsletters or order updates.
  • You need reliability and can’t risk both services going down together.
  • You have a team that needs shared calendars, groups and admin controls.
  • You care about deliverability.

The setup I’d choose for most small businesses

  1. Host the website with a decent web host.
  2. Put business email with a dedicated provider, such as a workspace suite or a specialist email service, rather than the web host. I compared two big options in Google Workspace vs Microsoft 365 for a small business.
  3. Set the MX records to the email provider, and keep the website’s records pointing at the host.
  4. Add SPF, DKIM and DMARC according to the provider’s instructions.
  5. Send website emails through a transactional email service, not the web server’s default mail.
  6. Keep the DNS in a separate place if you can, such as the registrar or a service like Cloudflare, so changing hosts doesn’t mean redoing everything.
  7. Use strong passwords and two-factor login on every account.

That costs a few pounds or dollars a month per mailbox, and in my experience it is cheap insurance.

Quick migration warning

If you do move email, plan it. Lower the DNS record’s time-to-live in advance, set up the new mailboxes, copy old mail across, switch the MX records, and keep the old mailbox alive for a few days to catch stragglers. Don’t cancel the old hosting on the same day.

Key takeaways

  • Website and email are separate services connected through DNS records.
  • Same-host email is simple and cheap, but a single outage can take out both.
  • Deliverability, features and security are usually better on a dedicated provider.
  • For a business that lives on email, separate them.
  • Set SPF, DKIM and DMARC whichever way you go.

Where does your business email live right now, and would you know what to do if that host went down?