# How to create a business email address with your own domain > Set up professional email on a custom domain: choose a mailbox host, verify ownership, create users and role addresses, change MX records, authenticate sending, and test the migration. - **Category:** Email Strategy - **Published:** August 4, 2026 - **Reading time:** 16 min read - **Author:** Maya Chen, Email Strategy - **Canonical page:** [https://emailbump.com/blog/how-to-create-a-business-email](https://emailbump.com/blog/how-to-create-a-business-email) To create a business email address such as maya@example.com, you need control of the domain example.com and a mailbox provider that hosts incoming and outgoing mail for it. Register or connect the domain, verify ownership, create the mailboxes and aliases, publish the provider's MX and authentication records, then test inbound, outbound, reply, recovery, and migration behavior before announcing the address. > **The domain and mailbox service are separate assets** > > Your registrar controls registration, your authoritative DNS provider publishes records, and your mailbox host stores and serves mail. One company may provide all three, but document each role separately so a website redesign, billing dispute, or employee departure cannot silently take down business email. ## What you need before creating business email - A domain registered to the business with current renewal, recovery, and organization-owned contact information. - Administrative access to the domain's authoritative DNS—not merely the website builder or a non-authoritative registrar panel. - A mailbox provider that supports your users, devices, retention, migration, security, shared-mailbox, and compliance needs. - A naming plan for people, duplicate names, role addresses, former employees, contractors, and automated senders. - Primary and backup administrators using strong, preferably phishing-resistant multifactor authentication. - An inventory of existing mailboxes, aliases, groups, forwarding, applications, forms, scanners, CRM systems, and DNS authentication. ## Step 1: choose and protect the domain Choose a domain that is readable, durable, and owned by the organization. Avoid a spelling that must be explained aloud or a temporary campaign domain for core employee identity. Turn on registrar lock, multifactor authentication, renewal alerts, and more than one controlled recovery method. Record who can change nameservers and who approves transfers. Buying a domain does not automatically create mailboxes. It gives you the name and the ability to publish DNS. The mailbox provider will supply verification, MX, and authentication instructions after you connect the domain. ## Step 2: choose a business mailbox provider ### Identity and security **MFA, passkeys, SSO, recovery, audit logs** Administrators and high-risk role inboxes need stronger controls than a shared password. ### Collaboration **Calendars, contacts, shared mailboxes, groups** Confirm how sent history, assignment, delegation, and external senders work. ### Migration **IMAP import, coexistence, routing, support** A working import plan matters more than a glossy signup flow. ### Operations **Status, retention, export, support, data location** Document recovery and exit before the provider becomes business-critical. ### Applications **SMTP submission, relay, APIs, limits** Human mailboxes are not automatically appropriate for receipts, alerts, or campaigns. Google Workspace and Microsoft 365 both support custom-domain business addresses, but they are not the only choices. Compare current provider documentation for your actual account type and region. Do not select solely from a per-user headline price: migration, security, storage, shared access, compliance, and application-mail separation determine the operating cost. ## Step 3: verify domain ownership The provider normally asks you to publish a unique TXT or CNAME record. This proves you can control DNS; it does not route mail yet. Copy the generated owner and value exactly, learn whether the DNS interface appends the zone name automatically, and verify through the provider after the authoritative nameserver returns the record. ### Conceptual verification record ```text TYPE OWNER VALUE TXT @ or example.com provider-verification=unique-token The exact owner and token come from your provider. Do not copy this example into production DNS. ``` ## Step 4: create users, role addresses, and groups - Create a named account for each person who needs independent sign-in, auditability, storage, and recovery. - Use aliases for additional addresses belonging to one stable owner; do not disguise a team workflow as one person's alias. - Use shared mailboxes, groups, or ticket queues for support@, billing@, privacy@, security@, and other durable responsibilities. - Assign primary and backup owners, external-sender policy, retention, sent-history, escalation, and expected response time. - Reserve application identities such as receipts@ or alerts@ for verified sending platforms rather than sharing a human mailbox password with code. ### Example identity plan ```text maya.chen@example.com named employee mailbox sales@example.com shared sales queue support@example.com ticketing-system ingress security@example.com restricted monitored workflow receipts@example.com transactional visible From identity bounces@mail.example.com provider-managed envelope and bounce identity ``` ## Step 5: publish MX records carefully MX records tell external senders which servers accept inbound mail for the domain. Publish the exact hosts and preference values supplied by the mailbox provider. Lower preference numbers are tried first. Remove old MX records only when the migration plan says they are no longer needed; mixing two providers without intentional split routing can make delivery unpredictable. ### Pre-cutover checks ```text Authoritative DNS provider confirmed All destination users, aliases, and groups created Historical mail import or coexistence tested Old and new MX values recorded DNS TTL and rollback window understood Website forms, devices, CRM, and apps inventoried Inbound and outbound test accounts available outside the domain Support owner and rollback decision time assigned ``` ## Step 6: configure SPF, DKIM, and DMARC MX routes inbound mail; it does not authenticate outbound mail. Publish one valid SPF policy that includes only actual envelope senders, enable DKIM signing for the custom domain, and deploy DMARC reporting and policy at a level the organization can operate. Verify alignment from a real received message rather than assuming the provider's green setup indicator covers every application. - Inventory every system that sends as the domain before changing SPF or DMARC. - Generate DKIM records inside each provider and keep selectors and keys distinct for rotation and incident response. - Confirm the visible From domain aligns with a passing DKIM signing domain or SPF-authenticated Return-Path under DMARC. - Send DMARC aggregate reports to a monitored analysis route and investigate unknown sources. - Separate marketing and transactional streams when consent, cadence, reputation, and failure budgets differ. ## Step 7: test before and after cutover ### Inbound **External account → every address type** Test named users, aliases, groups, role queues, unknown users, attachments, and spam handling. ### Outbound **Every supported client → external providers** Check visible identity, replies, SPF, DKIM, DMARC, TLS, and message formatting. ### Applications **Forms, CRM, devices, automations** Move credentials deliberately and verify bounce or failure reporting. ### Access **Login, MFA, delegation, recovery** Test administrators and ordinary users without sharing credentials. ### Continuity **Import, forwarding, old addresses, rollback** Keep evidence for messages sent during the DNS and coexistence window. ## Can you create a business email for free? Some hosting packages, registrars, or mailbox providers include limited mail service, and some products offer free tiers. The domain registration itself normally has a recurring cost, and “included” email still carries migration, backup, support, security, and continuity risk. Evaluate current terms and export options; do not build a permanent company identity around a temporary promotion you cannot migrate from. ## Send product email from verified domains Use stable business identities for receipts, alerts, and account messages without turning an employee mailbox into production infrastructure. - Verified sending domains - Purpose-specific sender identities - Message-level delivery evidence [Learn more](https://emailbump.com/signup) ## Frequently asked questions ## Do I need a website to create a business email? No. You need control of the domain and a mailbox service. A trustworthy website can help recipients verify the organization, but web hosting and mail hosting are technically separate services. ## Can I use Gmail with my own business domain? Google Workspace supports Gmail-hosted mailboxes on a custom domain. A free consumer Gmail address ending in gmail.com is different from a custom-domain Workspace account. Follow Google's current setup and billing documentation for the account you choose. ## Will changing MX records affect my website? An MX-only change should not alter web A, AAAA, or CNAME records. Mistakes in the zone or nameserver delegation can affect both, so export the current DNS and change only the intended records. ## Complete the business email setup - [Google Workspace alias vs user](https://emailbump.com/blog/google-workspace-email-alias-vs-user) — Decide when an address needs an alias, paid account, Group, or delegated mailbox. - [Google Workspace pricing](https://emailbump.com/blog/google-workspace-pricing) — Compare Google’s business plans, commitments, storage, features, users, aliases, and annual costs. - [Business address examples](https://emailbump.com/blog/business-email-address-examples) — Choose consistent personal formats and durable role inboxes. - [MX record lookup](https://emailbump.com/tools/mx-record-lookup) — Verify which servers currently accept inbound mail for the domain. - [Email authentication methods](https://emailbump.com/blog/email-authentication-methods) — Separate login security from SPF, DKIM, and DMARC. - [Email migration checklist](https://emailbump.com/tools/email-migration-checklist) — Plan discovery, coexistence, cutover, rollback, and validation. ## Sources - [Google Workspace: create a business email address](https://workspace.google.com/solutions/business-email/) - [Microsoft 365: add a custom domain](https://learn.microsoft.com/en-us/microsoft-365/admin/setup/add-domain) - [RFC 5321: MX records and SMTP routing](https://www.rfc-editor.org/rfc/rfc5321)