How to Set Up Business Email on Your Own Domain

A business address like you@yourcompany.com is a ten-minute purchase and a two-hour setup. The purchase is easy. The setup is where people lose a week, usually because they added the mailboxes first and the DNS records last, then wondered why their first client email went to spam.

Do it in the order below and it works the first time.

Table of contents

Step 1: Own the domain, and know where its DNS lives

Register the domain at a registrar where you hold the login yourself, not one that a freelancer or an old agency set up in their name. Namecheap is one option. Any reputable registrar works.

Then find out where your DNS is managed. It’s the place that lists your A, MX, and TXT records. Often that’s the registrar, but if the site sits behind Cloudflare, the records live there. You’ll edit records in that one place for every step below, so write down which it is.

Step 2: Choose one provider

You need one service that hosts the mailboxes. For most small businesses and agencies the choice is between two:

1. Google Workspace if your team already works in Google Docs, Sheets, and Calendar.
2. Microsoft 365 if your clients send you Word and Excel files, or you want the desktop Outlook app.

Pick based on the tools your team opens all day, not on a feature table. Both do the job, and both let you move later; my guide to moving business email off GoDaddy covers the switch.

The cheap bundle that comes with a web host is the option I’d skip for anything client-facing. Shared hosting mailboxes tend to share sending reputation with strangers, which is a quiet way to end up in spam.

Step 3: Add your domain and verify it

Sign up with the provider and enter your domain. It will ask you to prove you own it by adding a TXT record at your DNS host. Copy the value exactly, paste it into a new TXT record, and click verify. DNS changes can take a few minutes to a few hours to appear.

This record doesn’t touch mail delivery. It’s safe to add at any time.

Step 4: Create the mailboxes

Create one mailbox per person, then add the shared addresses people will actually write to: info@, billing@, support@. Make shared ones aliases or group inboxes rather than paid seats where your provider allows it.

Use a consistent pattern, first name or first initial plus last name, and decide it now. Changing it after your address is on 200 invoices is miserable.

Step 5: Point the MX records at the provider

MX records tell the internet where to deliver mail for your domain. Your provider shows the exact values on its setup screen. Delete any MX records already on the domain, add the provider’s, and keep the priorities it gives you.

If this domain already receives mail somewhere, stop. Switching MX records moves delivery, and anything still arriving at the old place is lost to you. Use the migration steps in the GoDaddy move guide instead.

Step 6: Publish SPF and DKIM before you send

This step separates mail that arrives from mail that doesn’t.

1. SPF is a single TXT record listing which services may send as your domain. You get one per domain. If you later add an invoicing tool or a newsletter service, you add its include: to that same record, not a second one.
2. DKIM signs each outgoing message so receivers can check it wasn’t altered. Turn on signing in your provider’s admin console and publish the key it gives you as a DNS record.

I walk through both, plus DMARC, in how to set up SPF, DKIM, and DMARC for business email. Do SPF and DKIM now, and add DMARC at p=none the same day.

Step 7: Test before you tell anyone

1. Send a message from your new address to a personal Gmail account and to an Outlook.com account.
2. Reply to each, and confirm the replies arrive.
3. In Gmail, open the received message, choose “Show original,” and check that SPF and DKIM both say PASS.
4. Send one to a friend and ask them to look in spam, not just the inbox.

If a test lands in spam or SPF says fail, the fix is almost always in Step 6. Don’t announce the address until all four pass.

Step 8: Connect the tools that send as you

Your invoicing tool, CRM, contact form, and scheduling app may all send mail from your domain. Each one needs either to be authorized in your SPF record or to send through your new mail provider. Open each, update its sending settings, and send a test.

Then add the address to your phone and laptop, set a signature, and update the contact page, social profiles, and invoice template.

Tell Claude or ChatGPT to do it

The part worth handing off is the checklist tailored to your setup. Paste this and fill in the brackets:

I'm setting up business email for [yourdomain.com] with [Google Workspace /
Microsoft 365]. My DNS is hosted at [DNS provider]. The domain [does / does not]
receive mail anywhere today. These tools also send mail as the domain: [list].
Give me a numbered checklist in the right order: domain verification TXT, the
mailboxes and aliases to create, MX records, the single SPF record I should end
up with, DKIM setup, and a DMARC record at p=none. For each step, tell me
whether it happens at the DNS host or in the mail admin console.

Compare every record it gives you with the values on your provider’s own setup page before you save. Assistants will confidently invent an MX hostname or an include: that looks right and isn’t.