Setting up business email with your domain involves more than creating mailboxes. This practical checklist covers mailbox setup, DNS records, SPF, DKIM, DMARC, deliverability testing, and the troubleshooting steps to use when messages bounce, fail authentication, or disappear into spam.
Overview
A professional email address uses your domain, such as hello@example.com, rather than a general consumer address. The visible mailbox is only one part of the system. Your domain’s DNS records tell receiving mail servers where to deliver messages and whether a sending service is authorized to use your domain.
The setup usually has four layers:
- Mailboxes: User accounts, aliases, groups, and recovery options created with your email provider.
- MX records: DNS records that identify the servers responsible for receiving email for your domain.
- SPF and DKIM: Authentication controls that help receiving systems verify permitted senders and message signatures.
- DMARC: A policy and reporting layer that tells receiving systems how to handle messages that fail authentication checks.
Exact record names and values vary by provider, so use the provider’s current setup instructions rather than copying records from another domain. The general workflow remains consistent: inventory your senders, create the mail service, publish the required DNS records, test authentication, and monitor delivery.
Before changing DNS, record the existing values and confirm where DNS is managed. Your registrar, hosting company, website platform, or a separate DNS provider may control the authoritative zone. If you are also changing hosts, the DNS troubleshooting guide can help separate website, email, and SSL changes.
Checklist by scenario
Scenario 1: Setting up a new business email domain
- Choose the email provider and plan. Confirm the number of mailboxes, aliases, storage limits, sending restrictions, administrator roles, recovery options, and support process.
- Verify domain ownership. Most providers ask you to add a temporary TXT record. Add it exactly as provided, then complete verification in the provider dashboard.
- Create the initial administrator account. Use a monitored address and enable multi-factor authentication where available. Avoid using a shared password for several people.
- Add mailboxes, aliases, and groups. Decide which addresses need individual sign-in accounts and which can forward to an existing mailbox. For example, invoices@ might be an alias or shared address rather than a separate user.
- Publish MX records. Remove obsolete MX records only after confirming that the new provider is ready. Multiple providers should not be left active accidentally, because receiving behavior can become unpredictable.
- Add SPF, DKIM, and DMARC. Use the values supplied by the email provider. DKIM often requires a provider-generated selector, while SPF must account for every legitimate service that sends mail for the domain.
- Test from more than one address. Send and receive messages using the new mailbox, a personal account, and a separate business address if available. Check headers for authentication results.
Scenario 2: Adding a website contact form or marketing platform
List every system that sends messages using your domain. This may include the mailbox provider, website contact form, ecommerce platform, customer relationship system, newsletter tool, booking platform, or transactional email service.
Do not add a second SPF TXT record for each service. SPF is normally published as one record for the domain, so authorized services may need to be combined according to the providers’ instructions. Each sending platform may also require its own DKIM record, often under a unique selector. If a service supports a custom return-path or dedicated sending subdomain, document that configuration separately.
After adding a contact form, test both the visitor confirmation and the notification sent to the business. Confirm that the reply-to address is useful and that the form does not allow arbitrary visitor input to become the message sender. For website maintenance and access controls, see the website security checklist for small businesses.
Scenario 3: Moving email to a new provider
- Export or migrate existing messages, contacts, calendars, and aliases according to the old and new providers’ procedures.
- Lower the DNS record TTL ahead of the change when practical, while recognizing that cached records may still remain visible for a period of time.
- Confirm the new mailboxes and authentication records before switching MX records.
- Change MX records during a monitored window and keep the old service available until delivery and migration checks are complete.
- Update SPF to remove services that no longer send mail and add the new provider.
- Rotate or replace DKIM records as required by the new provider.
- Review DMARC reports and bounced messages after the transition.
A mail change is separate from a website migration. If both are happening together, maintain a written DNS change list to avoid replacing unrelated A, CNAME, or TXT records. The hosting comparison and migration checklist provides a broader change-management framework.
Scenario 4: Sending mail from a domain that only needs forwarding
Forwarding is not the same as hosting a mailbox. Confirm whether the forwarding service supports replies, catch-all addresses, spam filtering, and authentication preservation. Forwarded messages can be difficult to authenticate because the forwarding path may alter the original delivery context. Test messages to several recipient providers before relying on forwarding for important business communication.
What to double-check
| Record or setting | Purpose | What to verify |
|---|---|---|
| MX | Routes incoming email | Hostnames, priority values, spelling, and removal of obsolete records |
| TXT verification | Confirms domain ownership | Exact value, correct DNS zone, and removal only when the provider permits it |
| SPF | Lists authorized sending sources | One coordinated policy, all legitimate senders included, and no abandoned services |
| DKIM | Provides a cryptographic message signature | Correct selector, record type, full value, and enabled status in the provider dashboard |
| DMARC | Sets handling and reporting preferences for authentication failures | Correct policy, reporting address, alignment settings, and gradual rollout plan |
| Mailbox settings | Controls access and user behavior | Multi-factor authentication, recovery details, aliases, forwarding, and account limits |
Check the domain portion of every record carefully. A record intended for _dmarc.example.com can be entered incorrectly if a DNS interface automatically appends the domain name. Some interfaces also expect only the host label, while others require a fully qualified name.
For DMARC, begin with a policy that lets you observe authentication results before enforcing a stricter handling policy, unless you already understand every legitimate sending source. Use a monitored reporting address and review whether reports identify a real business service or an unknown sender. A policy that is too strict before all senders are aligned can interrupt legitimate messages; a policy that is never reviewed provides little operational value.
Authentication is not a substitute for good email practices. Keep account credentials protected, remove former users promptly, use clear display names, and avoid sending from addresses that recipients cannot reply to. Keep website backups and recovery procedures current as well; the website backup and restore guide covers the related business continuity work.
Common mistakes
- Publishing multiple SPF records: Combine authorized services into the provider-supported format instead of creating separate SPF TXT records.
- Forgetting non-mail senders: A website form or booking platform may send mail even when staff use a different mailbox provider.
- Copying records from another domain: DKIM selectors, verification tokens, and provider hostnames are often domain- or account-specific.
- Changing MX without a migration plan: New mail may arrive at the new provider while older messages remain at the previous service.
- Using a personal address in a contact form’s From field: The form should generally use an authorized domain address as the sender and place the visitor’s address in Reply-To.
- Ignoring failed authentication: A single test message is not enough when several sending platforms are involved. Test each workflow separately.
- Assuming DNS changes are instant: Cached records can cause different results during the transition. Keep a timestamped change log and test from more than one network or checker.
- Enforcing DMARC without inventorying senders: Review legitimate sources first, then increase enforcement carefully.
If messages bounce, read the complete error rather than relying on the subject line. A recipient rejection may indicate an invalid address, a mailbox limit, a policy block, authentication failure, or a temporary server problem. If authentication fails, inspect the message headers and identify which service actually sent the message. If forwarding fails, test direct delivery to the recipient and compare the headers. If contact-form notifications do not arrive, check the website’s mail configuration, provider logs, spam folders, and the form’s sender and reply-to fields.
When to revisit
Use this checklist whenever you add a mailbox, change email providers, launch a new website form, connect a marketing or booking platform, change DNS providers, or onboard or remove staff. Revisit it before seasonal campaigns and other periods when message volume or business inquiries may increase.
Set a recurring review of your sending inventory and DMARC reports. Confirm that every listed sender is still needed, that former vendors have been removed, and that administrator access remains appropriate. Also review provider documentation when workflows, authentication requirements, mailbox limits, or DNS interface steps change.
For a practical final check, complete these actions:
- Write down every service that sends mail for the domain.
- Confirm where authoritative DNS is managed.
- Verify MX, SPF, DKIM, and DMARC records against current provider instructions.
- Send a test from each sending workflow and inspect the results.
- Record any bounce, authentication failure, or forwarding issue with its full error message.
- Keep the change log and recovery contacts somewhere the next administrator can access.
Reliable business email is an ongoing configuration task, not a one-time checkbox. A short review after each provider or website change helps protect both routine correspondence and the contact forms that prospective customers rely on.