Website planning

Business Email on Your Own Domain: What to Check When You Set It Up or Switch Providers

Check domain email routing, SPF, DKIM, DMARC, and forwarding before a provider switch. Test delivery and tighten policies gradually.

Wild Article 025, 2026-11-20: Business Email on Your Own Domain: What to Check When You Set It Up or Switch Providers

The short answer: check who controls the domain and admin accounts, confirm incoming mail is routed to the provider you use, and verify that SPF, DKIM, and DMARC reflect every service that sends using your domain. Recheck these pieces after changing providers. No DNS setup can guarantee every message lands in an inbox, but a deliberate review can catch common misconfigurations.

First, know which accounts control what

A domain, DNS, and mailbox are separate control points. The registrar holds the domain registration; the DNS host publishes the records that route mail; the email provider runs the mailboxes. One company may handle several of these jobs.

Check that domain registration, renewals, and recovery details are in a business-controlled registrar account, and keep admin access to the DNS host and email provider documented. The business should still be able to sign in if a staff member or contractor leaves.

Before switching, list the mailboxes, aliases, shared inboxes, and forwarding rules you need. Prepare new accounts and plan how to copy or retain old messages before retiring the old service.

MX records send incoming mail to a provider

MX records are DNS entries that tell sending systems where to deliver mail for your domain. On a provider switch, use the new provider's exact MX values; old or incorrect entries can interfere with delivery. Google's MX guide says Workspace changes may take up to 72 hours to be recognized, but requirements and timing vary by provider.

Change only the mail records, not unrelated website DNS. After the change, test from an outside address and confirm mail reaches the new mailbox before cancelling the old service.

SPF, DKIM, and DMARC cover outgoing mail

These checks help receiving systems assess whether mail using your domain is legitimate. The FTC's email authentication guide explains the roles: SPF lists approved senders; DKIM adds a verifiable signature; DMARC checks whether authentication matches the visible From address and sets a handling policy.

After a provider switch, update rather than erase the existing setup. Google's SPF guide says to account for all mail sources, including web servers and third parties, and update SPF when adding a new sender. Your list might include the mailbox provider, invoicing software, a newsletter platform, and a booking tool. Ask each vendor which DNS records it needs, and remove a former sender only when it has stopped sending.

For DKIM, publish the key specified by each sending provider and enable signing in its system. For DMARC, at least one of SPF or DKIM must pass with a domain aligned to the visible From address. Ask third-party senders how they authenticate with your domain, then check a real message instead of relying only on a setup screen.

For a new DMARC rollout, start in monitoring mode

When setting up DMARC for the first time, avoid strict enforcement before you know all the senders. Google recommends setting up SPF and DKIM, waiting at least 48 hours, then beginning DMARC at p=none. That policy does not ask receivers to quarantine or reject failing mail; it lets you review reports. Google's rollout guide advises daily report review for a week, then moving to quarantine and increasing enforcement gradually if there are no issues. Since p=reject can stop failing messages from being delivered, use it only after legitimate senders are accounted for.

If DMARC is already enforced, ask your email administrator to validate the provider switch without automatically weakening the existing policy. Set the report destination to a monitored address and assign someone to review the reports. If you can't interpret them, ask your provider or an email administrator before tightening the policy.

Forwarding can change authentication results

Forwarding can change authentication. Microsoft's email authentication overview explains that SPF may fail because the forwarder, not the original server, sends the message onward. DKIM may still pass if the message is unchanged; modifications can break checks and DMARC. Some systems use ARC (Authenticated Received Chain) to preserve earlier authentication results, but support depends on the services involved.

If you rely on forwarding, test it after a provider change and follow your provider's guidance. Don't use forwarding as a substitute for planning a mailbox migration.

A provider-switch checklist

  • Keep registrar, DNS, and email-admin access under business control; document recovery and administrators.
  • List mailboxes, aliases, shared inboxes, forwarding rules, and services that send as your domain.
  • Prepare the new mailboxes and any needed message copy before changing MX records.
  • Use the new provider's MX instructions and preserve unrelated DNS records.
  • Update SPF for approved sources and enable DKIM for every service that supports it; remove former senders only when they stop sending. Services that send in bulk to Gmail or Yahoo addresses must pass both SPF and DKIM and have a DMARC record (Google's sender guidelines, Yahoo's sender best practices).
  • For a new DMARC rollout, start at p=none, review reports, and tighten gradually after legitimate senders are accounted for. For an existing enforced policy, validate the provider switch with your email administrator rather than automatically weakening the policy.
  • Test inbound/outbound mail, key vendor messages, and forwarding. Recheck after provider or vendor changes.

Hypothetical example: A shop moves its inboxes to a new provider but leaves its newsletter service out of the SPF/DKIM plan. Staff mail works, while campaign messages fail authentication. The fix is not to switch mailboxes again. The owner inventories both senders, follows the providers' DNS instructions, and checks DMARC reports before considering enforcement.

Limits of this advice

DNS records and provider setup screens vary, and delivery also depends on receiving providers' filtering decisions. These steps are a general review, not a live audit of your domain or a promise of inbox placement. If you are unsure which records are safe to change, ask your email provider or a qualified administrator to review the current DNS before editing it.

Evidence

Sources

  1. Set up MX records for Google Workspace  |  Domain management  |  Google Workspace HelpGoogle · Retrieved
  2. Cybersecurity for Small BusinessFederal Trade Commission · Retrieved
  3. Set up SPF  |  Apps & integrations  |  Google Workspace HelpGoogle · Retrieved
  4. Recommended DMARC rollout  |  Security & data protection  |  Google Workspace Helpknowledge.workspace.google.com · Retrieved
  5. How email authentication works in Microsoft 365 - Microsoft Defender for Office 365learn.microsoft.com · Retrieved
  6. Email sender guidelines - Google Workspace Admin Helpsupport.google.com · Retrieved
  7. Sender Best Practices - Yahoo Sender Hubsenders.yahooinc.com · Retrieved

A useful next step

Keep a useful record

Use the ownership checklist to organize the accounts and people involved in your site.

Open the ownership checklist