Skip to content

Home / Blog

Guide

Business Email on Your Own Domain: Setup and Spam Fixes

Business Email on Your Own Domain: Setup and Spam Fixes

An address like sales@yourcompany.com tells a client you’re an established business; a free webmail address makes them wonder. Creating business email on your own domain takes minutes. The harder part comes next, when messages start landing in spam or bouncing. The cause is rarely your wording. It’s usually missing or duplicated DNS records. This guide covers setting up the mailboxes, then the four records that decide where your mail ends up, and what Gmail, Yahoo and Outlook require from senders today.

What you need first

Just two things:

  1. A domain in your company’s name. If you don’t have one yet, start at our domains page. If the difference between a domain and hosting is fuzzy, this explainer clears it up.
  2. Somewhere to host the email. The two usual options:
Option Good for Notes
Hosting mailboxes (cPanel) Everyday email for small and mid-sized teams Comes with your hosting plan, managed from the same panel
A dedicated email suite (e.g. Google Workspace, Microsoft 365) Teams that want shared calendars and collaboration tools Separate per-user subscription; you add the records the provider gives you

Either way it’s the same domain, and the deliverability rules below apply to both.

How to set up business email on your own domain

These steps use cPanel, the control panel on Start Bigger hosting plans.

1. Create the mailbox

In cPanel, open Email Accounts and click Create. Choose the domain, enter the mailbox name and set a long, strong password. Common choices: info@ or hello@ for general enquiries, sales@ and support@ for departments, and firstname@ for each person.

If you just want sales@ mail delivered to your own inbox, create a Forwarder instead of another mailbox.

2. Connect your phone and laptop

Webmail works from any browser, but most people prefer their usual mail app. Choose IMAP rather than POP3 so messages stay in sync across devices.

Service Port Encryption
IMAP (incoming) 993 SSL/TLS
SMTP (outgoing) 465 SSL/TLS
SMTP (alternative) 587 STARTTLS

Your username is the full email address. The Connect Devices option next to each mailbox in cPanel shows the exact server names.

3. Add a clean signature

Name, role, phone number and website. A short text signature beats a large image.

The four DNS records that keep you out of spam

When your message reaches a provider like Gmail, it asks one question: is this server really allowed to send for this domain? Four DNS records answer it.

MX: where your mail is received

The MX record tells the world which server accepts incoming mail for your domain. If email lives on your hosting, it points to your hosting server; if you use an email suite, enter their values and remove the old ones. A wrong MX record means incoming mail never reaches you.

SPF: who may send as you

SPF is a TXT record listing the servers allowed to send for your domain:

v=spf1 a mx include:_spf.sending-service.example ~all

Two rules trip people up:

  • One SPF record per domain. Add a second record for a newsletter tool and the whole check fails with a PermError. Merge every sender into a single record.
  • A 10-lookup limit. Each include, a, mx, ptr, exists and redirect counts; ip4, ip6 and all don’t. Go over 10 and SPF fails, so remove services you no longer use.

DKIM: a signature on every message

DKIM adds a cryptographic signature to each message and publishes the public key in DNS, so receivers can confirm the message really came from you and wasn’t altered. In cPanel the record is usually named default._domainkey.yourdomain.com. Each external sending service gives you its own DKIM record under a different name, and several DKIM records can coexist happily.

DMARC: what happens to fakes

DMARC ties SPF and DKIM to the address people actually see in the From field. That’s called alignment: it isn’t enough for SPF or DKIM to pass; the domain that passed must match your From domain. It’s published as a TXT record at _dmarc.yourdomain.com:

v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
  • p=none monitors only, with no effect on delivery. Start here.
  • p=quarantine sends failing mail to spam.
  • p=reject blocks it.

Read the aggregate reports sent to the rua address, and once everything that sends as you is passing, tighten to quarantine and then reject. You may see a pct tag in older guides. It’s optional, the basic record above doesn’t need it, and the IETF’s updated DMARC specification (known as DMARCbis) drops it, so there’s no need to add it to a new record.

What Gmail, Yahoo and Outlook require now

Gmail and Yahoo have enforced sender requirements since February 2024, and Outlook followed for high-volume senders in May 2025. Since November 2025, Gmail has been stepping up enforcement, so non-compliant mail may be deferred or rejected outright.

Requirement All senders Bulk senders (Gmail and Outlook: around 5,000+ messages a day)
SPF / DKIM At least one Both
DMARC Recommended Required (at least p=none), aligned
Spam complaint rate Under 0.3% Under 0.3%; aim for under 0.1%
One-click unsubscribe — Required on marketing mail

The details are in Google’s email sender guidelines and Yahoo’s sender best practices. Gmail and Yahoo also expect unsubscribe requests to be honoured within two days (48 hours). Technical items such as reverse DNS (PTR) and TLS encryption are handled by your host on its servers. Even if you send only a handful of emails a day, set up all three: SPF, DKIM and DMARC.

How to check it’s working

  1. In cPanel, open Email Deliverability. It shows SPF and DKIM status per domain and offers a repair when your host manages the DNS.
  2. Send a message to a Gmail account, open it and choose Show original. You want PASS next to SPF, DKIM and DMARC.
  3. After a few weeks, review your DMARC reports before tightening the policy.

Newsletters belong on a dedicated sending service

Hosting mailboxes are built for everyday correspondence, not campaigns. On Start Bigger hosting, outgoing mail is limited to 100 messages per hour per domain, which protects both the server’s reputation and yours. For newsletters, use a dedicated sending service, then:

  • add its include to your existing SPF record, not a new one;
  • publish the DKIM record it gives you;
  • consider sending campaigns from a subdomain such as news.yourdomain.com, so campaign performance doesn’t drag down your everyday mail;
  • only email people who opted in, and never buy lists.

Our acceptable use policy covers the sending rules on our servers.

Common setup mistakes

  • Editing records in the wrong place. If your nameservers point to your host, records added at the registrar are ignored.
  • Leftover MX records from a previous provider, which can send some mail to the old place.
  • An unread rua mailbox. Create a dedicated address, or use a tool that summarises the reports.
  • Forgetting email when you move hosts. Nameserver changes move mail records too; see how to migrate WordPress without downtime.
  • WordPress forms “sending as” the visitor. Send form mail via SMTP from a real mailbox on your domain and put the visitor’s address in Reply-To, not From.

In short

Creating the mailbox is the easy part. Reaching the inbox depends on four records: MX for incoming mail, one SPF record under 10 lookups, DKIM signing, and a DMARC policy that starts at none and tightens over time. Check your results with Show original, keep campaigns on a dedicated sending service, and your everyday business email stays trusted.

Frequently asked questions

Do I need a website to have email on my own domain?

No. You need a domain and somewhere to host the mailboxes. You can set up email today and build the website on the same domain later.

I added an SPF record. Why is my email still going to spam?

SPF alone often isn't enough. Add DKIM signing and a DMARC record, with your From domain aligned to at least one of them; for bulk senders this is mandatory. Content and sending to people who never asked for your email can also push messages into spam.

Can I have one SPF record for my host and another for my newsletter tool?

No. The SPF standard allows one SPF record per domain, and two records make the check fail outright. Merge every sender into a single record and keep it under 10 DNS lookups.

How many emails can I send from my hosting mailbox?

On Start Bigger hosting the limit is 100 messages per hour per domain, which comfortably covers day-to-day business email. For newsletters and campaigns, use a dedicated sending service and add its records to your domain.

Should I set DMARC to reject straight away?

Usually not. Start with p=none and read the reports for a few weeks until every service that sends as you is passing. Then move to quarantine, and finally to reject.

Read next

Domains guide

How to Recover a Domain From a Former Web Developer

Practical steps to get back a domain a former developer or employee registered for you: find the registrant and registrar, gather documents, request a registrant change or transfer code, and prevent it happening again.

Domains guide

Domain Expired? What Happens Next and How to Get It Back

What happens after a domain expires under ICANN rules: the grace period, the redemption period and deletion, plus the recovery steps for each stage and how to stop it happening again.

Ready to start, or have a question first?

We answer on WhatsApp Saturday to Thursday, 9:00 am – 9:00 pm Amman time (GMT+3)

WhatsApp