Why it is worth the afternoon

Nothing changes how professionally a small site reads faster than replacing yourname123@gmail.com with hello@yourname.co.uk on the contact page — and if you already have a domain, you are one afternoon and four DNS records away from it.

Partly perception: an address on your own domain signals that the operation behind the site is real, in the same way headed paper once did. People reply to it more readily and trust invoices from it more.

Mostly, though, it is ownership. A Gmail or Outlook address belongs to the provider; an address on your domain belongs to the domain, and the domain belongs to you. Change hosts, change email providers, fall out with Google entirely — the address survives every one of those events, because you can point it anywhere. It is the same portability argument that applies to the website itself, extended to your correspondence.

The three ways to get it

Mailboxes on your hosting. Nearly every real hosting plan includes email: you create mailboxes in the control panel and the same server that serves your site stores your mail. Cost: nothing beyond hosting you already pay for. This is the right starting point for most small sites, and the rest of this article walks through it.

A dedicated email provider. Google Workspace, Microsoft 365, or the independent providers such as Fastmail and Proton, connected to your domain via DNS. Cost: typically £4–£10 per user per month. You get the polished apps, enormous storage, and deliverability handled by companies whose entire reputation rides on it.

Forwarding only. Many registrars and hosts will forward hello@yourdomain to an existing personal inbox free of charge. Receiving works immediately; the catch is sending — replying from the domain address requires SMTP configuration that forwarding alone does not give you, and half-configured setups are how replies end up in spam. Fine as a temporary measure, limiting as a permanent one.

Setting up mailboxes on your hosting

On a DirectAdmin server the mechanics take about two minutes per mailbox: E-mail Manager → E-mail Accounts → Create, choose the address and a strong password, and assign a quota. The step-by-step KB article has the screenshots.

Two decisions are worth making deliberately at this stage. First, create role addresses (hello@, accounts@) rather than only personal ones — roles survive people and make the eventual handover of any address painless. Second, resist the catch-all that accepts mail to any address at the domain: it sounds convenient and becomes a spam funnel within months. Individual addresses, created as needed, age much better.

The four DNS records that keep you out of spam

Here is the part most guides skip, and the reason mail from new domains lands in junk folders. Receiving servers no longer take a sender's word for anything; they check DNS for proof. Four records provide it.

MX says which server receives mail for the domain. If your host manages your DNS this exists already; if your DNS lives elsewhere (Cloudflare, commonly) you must add it there yourself — the number one cause of “my website works but email does not”.

SPF is a TXT record listing the servers allowed to send as your domain. Mail from anywhere else fails the check. Your host publishes the exact value to use.

DKIM has your server cryptographically sign each outgoing message, with the public key published in DNS so receivers can verify nothing was forged or altered. Usually one click to enable in the panel, which generates the record for you.

DMARC ties the first two together: a TXT record telling receivers what to do with mail that fails SPF and DKIM. A minimal p=none policy is the sensible start — it changes nothing but signals that the domain is actively managed, which the large providers increasingly expect. Gmail and Yahoo have required exactly this trio from bulk senders since 2024, and the expectation is spreading to everyone.

Set all four before the first important message, not after the first bounce. If any of this is unfamiliar, the DNS explainer covers the record types from first principles, and the troubleshooting KB article works through the failure cases.

Reading it on your phone and desktop

Mailboxes on your hosting speak the same protocols every mail app understands. Add the account in Outlook, Apple Mail, Thunderbird or your phone's mail app using IMAP for incoming (so every device sees the same mailbox) and SMTP for outgoing, with the server names and ports your control panel lists. The Outlook walkthrough shows a typical setup end to end.

If you would rather keep using the Gmail interface, Gmail can both fetch from and send through an external mailbox — Settings → Accounts — giving you the domain address inside the app you already know. A webmail client on the server covers the occasions you are away from your own devices.

When to use a dedicated provider instead

Honesty about the limits of host-based email: it shares resources with your website, storage quotas are hosting-sized rather than the tens of gigabytes the big providers offer, and deliverability — while fine with the records above configured — is ultimately tied to a shared server's reputation rather than Google's.

The practical rule: if email is correspondence — a small site's contact address, a handful of messages a day — hosting mailboxes are entirely adequate and cost nothing extra. If email is infrastructure — a team living in shared inboxes, calendars and large attachments all day — pay for Workspace or 365 and keep your hosting for the website.

The pleasing part is that the domain makes this choice reversible. Because the address belongs to you, moving between these options later is a DNS change and a mailbox export, not a new identity. Start with the included mailboxes, and upgrade the machinery behind the address if and when the volume justifies it.