Business Email Domain Setup: A UK Step-by-Step Guide

Setting up business email on your own domain takes five jobs: register or confirm the domain, choose a mailbox platform, create the mailboxes, publish the DNS records that route and protect your mail, and connect your devices. Done in that order, a small team can be sending from name@yourcompany.co.uk within a day. The part most people skip, and the part that decides whether your messages reach inboxes, is the DNS authentication: MX, SPF, DKIM and DMARC. This guide walks through all of it.
TL;DR
You need three things first: a domain you control, access to its DNS settings, and a mailbox platform (a hosted suite or a mailbox plan from your web host).
Four DNS record types do the work: MX sends incoming mail to the right place, while SPF, DKIM and DMARC prove your outgoing mail is genuine.
Start DMARC at p=none, read the reports, then tighten to quarantine and finally reject.
Turn on multi-factor sign-in for every mailbox before anyone starts using it.
Send test messages to several outside providers and check headers before you announce the new addresses.
Table of Contents
Why use your own domain instead of a free address
A free webmail address tells customers very little about who you are. An address on your own domain does three practical things.
It looks like a business. A supplier or a homeowner deciding whether to trust a quote is more likely to engage with a message from sales@yourcompany.co.uk than from a string of numbers at a free provider. It also matches your website and your invoices.
You own it. When someone leaves, you reassign the mailbox rather than lose a personal account that happened to hold your customer history. Staff turnover stops being a data problem.
You can protect it. Only the owner of a domain can publish SPF, DKIM and DMARC records for it. Those records make it harder for criminals to send messages that pretend to come from you. The UK National Cyber Security Centre (NCSC) frames this as making spoofing harder with SPF, DKIM and DMARC and protecting email in transit with TLS. A free webmail address gives you no such control.
There is a fair counter-argument: a free account costs nothing and works instantly. For a hobby that is fine. For anything that takes payments, signs contracts or holds customer data, the monthly cost of a proper mailbox is small against the trust and control you get.

What you need before you start
Gather these before opening any admin console. It saves the usual half-day of hunting for passwords.
A domain name. If you already have a website, you have one. If not, register one through any accredited registrar. Keep the registrar login with the business, not with a freelancer or an ex-employee.
Access to the DNS records. Whoever hosts your DNS (often the registrar, sometimes your web host or a separate DNS service) lets you add and edit records. Government guidance for setting up email securely lists administrative access to the email service and an editable public DNS record for each email domain among its prerequisites, and the same logic applies to a ten-person firm.
A decision on who sends mail on your behalf. Make a list: your mailbox platform, your invoicing software, your newsletter tool, your website contact form, your booking system. Every one of these may need to be named in your SPF record later.
A list of mailboxes. Personal ones (firstname@) and role-based ones (info@, accounts@, support@). Role addresses can be shared mailboxes or aliases rather than paid seats on some platforms, so check before buying licences.
One administrator you trust, plus a second named recovery contact.
If your website already uses HTTPS, you have done some of this groundwork. Our piece on what SSL certificates do for HTTPS and SEO checks covers the website side of keeping a domain trustworthy.
Choosing where your mailboxes live
The platform choice shapes cost, storage, security controls and how much admin you will do. There are three common routes.
Hosted productivity suites
Google Workspace and Microsoft 365 both give you a mailbox on your own domain plus calendars, shared documents and video meetings. They suit most small and mid-sized businesses because the admin console, multi-factor sign-in and mobile apps are all built in. The NCSC notes that all organisational domains should be protected, including those used with cloud providers such as Google Workspace and Microsoft 365, so choosing a big platform does not remove your DNS work.
How to choose between them, honestly:
Question | Points towards Google Workspace | Points towards Microsoft 365 |
Your team already lives in | Browser, Gmail-style interface, shared drives | Word, Excel and Outlook on the desktop |
Collaboration style | Real-time co-editing in the browser | Desktop files, deeper offline use |
Existing systems | Mostly cloud tools | Windows servers, existing Office licences |
Admin skills in house | Light | Comfortable with a more detailed admin centre |
Neither is wrong. The right one is the one your staff will actually use without a training week. If you want help weighing it up for your team, see our Google Workspace page.
Mailboxes from your web host
Most hosting plans include email accounts created through a control panel such as cPanel. This is the cheapest route and works for a sole trader who only needs a couple of addresses. The trade-offs: fewer built-in security controls, storage tied to your hosting account, and your website and email share one point of failure. If the site is compromised or the plan lapses, email goes with it.
A dedicated email-only service
Some providers sell mailboxes without the full suite. This suits a business that already has document tools it likes. Look for TLS support, DKIM signing and a clear SPF include value. GOV.UK’s Service Manual says a specialist email provider should support TLS where available, DKIM signing and an SPF hostname or IP range, which is a sensible checklist for any platform you are considering.
Business email versus a free Gmail account
People often ask whether they really need to pay when a free Gmail account works. The differences that matter are your own domain name, administrator control over every account, the ability to enforce multi-factor sign-in across the team, shared mailboxes and calendars, and support if something goes wrong. A personal account gives you none of the controls that let you manage a team.
Step-by-step: from nothing to working email
Step 1: Confirm or register the domain
Check that the domain’s registrant contact is a business address. Turn on registrar lock and multi-factor sign-in at the registrar. Losing a domain means losing email, website and often access to every account that sends password resets to it.
Step 2: Sign up and verify ownership
Whichever platform you pick, it will ask you to prove you own the domain. It normally gives you a TXT record or a CNAME to add at your DNS host. Add it, wait a few minutes (it can take longer), and click verify. This record only proves ownership; it does not move any mail yet.
Step 3: Create the mailboxes
Create users with a naming convention you can live with for years: firstname@ or firstname.surname@. Add aliases for info@ and accounts@ so those addresses reach the right person. Set a strong temporary password and force a change at first sign-in.
Step 4: Turn on multi-factor sign-in
Do this now, not later. Enforce it for all users in the admin console, using an authenticator app or a hardware key rather than text messages where the platform allows. Stolen passwords are the usual way a business mailbox is taken over, and a compromised mailbox is how fake invoices get sent to your customers.
Step 5: Publish the DNS records
This is the part that decides deliverability. It gets its own section below.
Step 6: Switch mail flow, then connect devices
Only change the MX records once the mailboxes exist, otherwise incoming mail bounces. If you are moving from an existing mail system, copy the old mail across first and lower the record’s time to live (TTL) a day ahead so the switch takes effect quickly.

The DNS records for email, explained
The Ministry of Justice’s DNS runbook sums up what an email domain commonly needs: an MX record to route mail, an SPF TXT record to identify authorised senders, a DKIM record to authenticate outgoing mail with a signature, and a DMARC record to define policy and reporting. Here is what each looks like in practice.
Record | Type | Where it lives | What it does |
MX | MX | Your domain root (@) | Tells other servers where to deliver mail for your domain |
SPF | TXT | Your domain root (@) | Lists the servers allowed to send mail as your domain |
DKIM | TXT or CNAME | A selector name such as selector._domainkey | Publishes the public key that checks the signature on outgoing mail |
DMARC | TXT | _dmarc | Sets what receivers do with mail that fails, and where reports go |
Your platform’s setup page gives you the exact values. Copy them exactly; a stray space or a missing full stop in a hostname is the commonest cause of failure.
MX: where incoming mail goes
Remove old MX records that point to a previous provider, then add the ones your new platform gives you, with the priorities it specifies. Leaving old records in place sends part of your mail to a system nobody checks.
SPF: who may send as you
SPF publishes the trusted sending addresses for your domain. You may have only one SPF record per domain; two records break it. If you use several services, they go into a single record, each with its own include. GOV.UK says an SPF record should include every system that sends mail and recommends at least a soft-fail (~all) qualifier in the government context. Many small businesses start with soft-fail and move to a hard fail (-all) once they are confident the list is complete.
This is where the sender list from earlier pays off. A forgotten invoicing tool is the classic reason legitimate mail lands in spam after a migration.
DKIM: a signature on every message
DKIM signs outgoing mail cryptographically. In most admin consoles you generate the key, copy the record it displays into DNS, then click a button to start signing. Do this for every service that sends as your domain, not just the main mailbox platform.
DMARC: the policy and the reports
DMARC tells receiving servers how to handle messages that fail SPF or DKIM checks, and sends you reports. The NCSC describes the trio together in its email security and anti-spoofing guidance. A safe first record looks like this:
v=DMARC1; p=none; rua=mailto:dmarc-reports@yourcompany.co.uk
The p=none policy changes nothing about delivery. It only asks receivers to send you reports, which is exactly what you want while you discover which of your systems send mail.
Rolling DMARC out without losing real mail
GOV.UK recommends starting DMARC at p=none and moving to p=quarantine or p=reject during implementation. A workable timetable for a small business:
Weeks 1 to 4: monitor. Publish p=none. Read the aggregate reports (a free report viewer makes the raw XML readable) and list every sender.
Fix the failures. Each legitimate sender that fails needs either an SPF include or DKIM signing set up with your domain.
Quarantine. Move to p=quarantine, ideally using the pct tag to apply it to a fraction of mail first, then increase.
Reject. Once reports show only genuine mail passing, move to p=reject. Forged mail claiming to be you is then refused by receiving servers that honour the policy.
If you hit trouble moving to reject, this practical write-up on moving a domain to DMARC reject without breaking email is worth reading before you change the policy. Whatever you do, change one step at a time and keep a note of the date and the record value, so you can roll back.
Connect your devices and check it works
Hosted suites make this simple: staff sign in to the vendor’s app on a phone or laptop, approve the multi-factor prompt, and mail syncs. For mailboxes from a web host you will normally use IMAP for incoming mail and SMTP for outgoing, with the server names, ports and encryption settings shown in the control panel. Choose the encrypted options rather than the plain ones.
Then test, in this order:
Send to yourself and a colleague inside the same platform.
Send to two or three outside providers, including a free webmail account and a corporate address if you have a friendly contact. Check that the message arrives in the inbox, not spam.
Reply from the outside account and confirm the reply arrives.
Open the full message headers of a received test and look for SPF, DKIM and DMARC all showing a pass.
Run the NCSC’s checker. The NCSC recommends checking your domain with its email security check as part of securing email, and it flags missing records quickly.
Send from every other system (invoicing, contact form, booking tool) and check each one passes authentication.
Only when all of those succeed should you update your website, invoices, business cards and email signatures.
Common mistakes we see
Two SPF records on one domain. Merge them into one.
Old MX records left in place after a move.
DKIM enabled for the main platform only, while the newsletter tool signs with its own domain and fails DMARC alignment.
Jumping straight to p=reject without a monitoring period.
The admin account is a personal mailbox. If that person leaves, nobody can change anything. Use a dedicated admin identity with a second recovery route.
No multi-factor sign-in on the registrar or the mail platform.
Contact form sends from a free address pretending to be your domain. Route it through your authenticated service.
Our perspective
We install and configure security and IT systems for homes and businesses around Guildford and Surrey, and email domain setup is the same discipline in a different place: get the foundations right once, document them, and do not leave a hole for somebody else to walk through. In our experience the technical steps are the easy part. What causes problems later is who holds the registrar login, nobody knowing which systems send mail, and a DMARC record that was copied from a tutorial and never looked at again.
Our advice to a small business owner is simple. Put the domain and the admin accounts in the company’s name. Keep a one-page record of every service that sends as your domain. Switch on multi-factor sign-in on day one. And treat DMARC as a three-stage project rather than a single record you paste in. A business that does those four things has done more than most to protect its customers from fake messages carrying its name.
— Andrii
Need a hand with the setup?
If you would rather not edit DNS yourself, Epicloud handles IT infrastructure, cloud and networking work for businesses in Guildford, Surrey and surrounding areas, including Google Workspace for company email. If you also want your premises protected, we supply and install Ajax alarms and CCTV; see our physical security and CCTV services or get in touch through epicloud.tech.
FAQ
How do I set up an email address for my domain?
Register or confirm your domain, choose a mailbox platform, and verify ownership with the TXT record it gives you. Create the mailbox, then add the MX, SPF, DKIM and DMARC records at your DNS host. Finish by connecting your devices and sending test messages to outside providers.
Do I need SPF, DKIM and DMARC for a small business?
Yes. They are the three records that let receiving servers check that mail claiming to come from your domain really did. The NCSC recommends them for organisations of all kinds, and they also reduce the chance your genuine mail is treated as junk.
How long does it take for the DNS changes to work?
Some changes appear within minutes, but records can take several hours to reach every resolver, depending on the TTL. Lower the TTL a day before switching MX records and avoid making the change at the end of a working day.
Can I keep my existing email when I move to a new provider?
Usually yes. Create the new mailboxes, copy old mail across using the new platform’s migration tool or an IMAP transfer, then switch the MX records. Leave the old service active for a short overlap so late-arriving messages are not lost.
Is Google Workspace or Microsoft 365 better for company email?
Neither wins outright. Teams that work in browsers and shared documents tend to settle into Google Workspace, while teams built around desktop Office files often prefer Microsoft 365. Pick the one your staff will use comfortably, and set up the same DNS protections either way.
Sources
Recommended
Comments