How to get an email domain and set it up correctly

Getting an email domain takes a few minutes. Owning it properly takes a little more thought.

You need four separate things:

1. A registered domain, such as example.com.
2. DNS access for that domain.
3. A mailbox provider, such as Google Workspace or Microsoft 365.
4. A sending tool if you plan to run campaigns.

Buying one does not automatically give you the others. Keep those layers clear and the setup becomes much easier to operate.

The short version

To get an email domain:

1. Choose a domain name you can represent honestly.
2. Register it through an accredited registrar or a provider that clearly documents registration and ownership.
3. Put the domain in an account your business controls.
4. Turn on renewal protection and secure the account.
5. Connect the domain to a mailbox provider.
6. publish and verify the required DNS records.
7. Create the mailboxes.
8. Send an external test and inspect the result.

If the domain will support cold email, add a ninth step: record who owns the domain, DNS, inboxes, sequencer connection, suppression data, and retirement decision.

Domain, website, mailbox, and sequencer are different

These products are often sold together, which makes the boundaries easy to miss.

You can have an email domain without a website. You can host a website somewhere different from your DNS. You can also move a domain between mailbox providers without changing its registrar.

That flexibility is useful—as long as the business keeps access to every layer.

Step 1: choose a domain that makes sense

A good email domain is readable, defensible, and easy to say out loud.

For a company’s main domain, the exact brand name is usually the cleanest choice. For outbound campaigns, some teams use additional domains so the operating boundary is separate from the domain used by employees and customers.

That separation is an operational decision, not a license to impersonate another business or hide the sender. The domain and message should still make the company identity clear.

Check these points before registering:

• Does the spelling look natural?
• Can a recipient understand the relationship to the business?
• Is the name free of confusing characters and accidental meanings?
• Does it infringe another company’s mark?
• Is the top-level domain appropriate for the audience?
• Can the business keep renewing it for the expected lifetime of the program?

Avoid piling on hyphens, numbers, or misleading brand variations just because the exact name is unavailable. A cheap registration becomes expensive if nobody trusts or remembers it.

Step 2: register it in the right account

ICANN coordinates the domain-name registration system and accredits registrars for common top-level domains. When you register a domain, you are purchasing the right to use it for a term—not buying the name forever.

The registrar account should belong to the business that needs the domain.

Use:

• A company-controlled email address.
• A password manager.
• Multi-factor authentication.
• Named administrators instead of one person’s private login.
• Accurate registrant and recovery information.
• Renewal notifications going to more than one responsible person.

If an agency registers domains for clients, define ownership before checkout. Decide whether the client or agency is the registrant, who pays for renewals, who controls DNS, and how access is transferred at the end of the engagement.

Do not let a former contractor’s personal inbox become the only way to recover a revenue-critical domain.

Step 3: understand the real cost

The advertised first-year price is not the whole cost.

Compare:

• Initial registration price.
• Renewal price.
• Registry or ICANN-related fees shown at checkout.
• Privacy features.
• DNS hosting.
• Transfer fees or renewal requirements.
• Mailbox licenses.
• Any provider service fee for setup or management.

Prices and promotions change. Check the current checkout total and renewal terms before you buy rather than copying an old comparison table.

For a multi-domain program, model the annual portfolio cost. A small difference multiplied by dozens of domains and renewals can matter. So can the labor required to keep them organized.

Step 4: secure renewal and ownership

Turn on automatic renewal when the account and payment method are stable. Then create a second reminder before the expiration date. Automatic renewal can still fail because a card expires or an account is locked.

Record:

• Domain.
• Registrar.
• Account owner.
• Expiration date.
• Renewal status.
• Payment owner.
• DNS host.
• Mailbox provider.
• Business or client owner.
• Retirement or transfer plan.

Registrar lock can help prevent unauthorized transfers. DNSSEC may protect the DNS lookup chain when the registrar and DNS provider support it, but it needs careful operation. Neither feature replaces secure account access.

Step 5: choose a mailbox provider

Registering the domain does not create you@example.com. A mailbox provider does that.

Google Workspace and Microsoft 365 are common choices for business email. Custom SMTP products are another category with different administration, IP, and deliverability responsibilities.

Choose based on:

• The mailbox experience the users need.
• Admin and recovery controls.
• Supported authentication and connection path.
• Tenant or workspace structure.
• The sending tools that need to connect.
• Ownership and support.
• The total cost of mailboxes, domains, and operations.

For standard Google or Microsoft mailboxes, the underlying provider still operates the mail transport. A reseller can compete on service, setup, domain structure, controls, and ongoing help. It should not claim that the same standard transport becomes inherently superior just because the mailbox was purchased through a different storefront.

Cheap Inboxes provides Google and Microsoft mailbox options, supports domain registration or importing a domain you already own, and uses one domain per workspace. That structure keeps each domain’s mailbox group easier to identify and hand off.

Step 6: publish the DNS records

Your mailbox provider will give you records to add to the domain’s authoritative DNS zone.

Common records include:

• MX: where inbound mail should go.
• SPF: which systems are allowed to send for the domain.
• DKIM: a public key used to verify signed messages.
• DMARC: the domain’s authentication policy and reporting instructions.
• Verification records: proof that you control the domain.

Copy values from the current provider admin interface or official documentation. Do not use another domain’s records, and do not assume a screenshot from an old guide still matches the provider’s current tenant-specific values.

Microsoft 365 DKIM is a good example: the record names are predictable, but the CNAME targets are specific to the domain and tenant. Our Office 365 DKIM setup guide shows how to retrieve and verify them.

Check the authoritative DNS host

The registrar and DNS host may be different. Nameservers tell you which DNS provider is authoritative.

If you add a TXT record at the registrar while the nameservers point somewhere else, nothing changes publicly. Confirm the authoritative zone before editing.

Enter hostnames the way your DNS provider expects

Some interfaces want only the host portion, such as selector1._domainkey. Others accept the full name. Some automatically append the root domain.

Preview the final record, save it, and query public DNS afterward. A duplicated domain name in the record is a common setup error.

Avoid duplicate SPF records

A domain should not publish several independent SPF TXT records. If multiple authorized senders are required, build one valid policy that includes them within the protocol’s lookup limits.

Do not add sending services the domain does not use “just in case.”

Step 7: create mailboxes and document the pattern

Choose a naming pattern that a real person can understand and maintain. Save the display name, sending address, recovery owner, mailbox provider, workspace or tenant, and campaign assignment.

Do not put credentials in the same planning sheet as the public inventory. Use a proper secrets or password-management system.

If one person uses several mailboxes, the visible identity should still be accurate. Do not create misleading employees or pretend the message came from someone who does not exist.

For an agency, decide what happens at handoff:

• Does the client keep the domain?
• Does the client receive registrar and DNS access?
• Who owns mailbox billing?
• Who removes the sequencer connection?
• Where are suppression records retained?
• Who is authorized to retire the domain?

These decisions are cheaper before launch than during an offboarding dispute.

Step 8: verify the setup with a real message

Provider setup screens show the configuration they expect. Verify the message that a receiver actually got.

Send to an external account, then inspect:

• Visible From address.
• Return-path.
• DKIM-Signature and its d= domain.
• SPF result.
• DKIM result.
• DMARC result.
• Sending IP and provider path.
• Reply behavior.

The message should pass authentication using identities that align with the domain you intended to send from.

Save one known-good header sample. It becomes the baseline after a DNS, mailbox-provider, or sequencer change.

Connect the sequencer last

Do not begin with the campaign tool.

First prove that the domain is owned, DNS is correct, the mailbox is active, and external authentication works. Then connect the mailbox using a path the provider and sequencer document—preferably OAuth where supported.

Record the connection owner and test removal as well as setup. A clean offboarding path matters when a campaign ends or an agency relationship changes.

CheapSequencer is a separate sequencing product. Cheap Inboxes handles the domain and inbox infrastructure layer; a sequencer handles campaigns. Keeping the layers separate makes it easier to replace one without losing control of the others.

Common mistakes

Buying a domain without checking renewal

Promotional pricing expires. Model the price you will actually pay to keep the asset.

Letting the wrong person own the account

The purchaser is not automatically the right long-term owner. Use the business or client account defined in the agreement.

Editing DNS in the wrong place

Check authoritative nameservers before assuming the registrar hosts the live zone.

Treating authentication as an inbox guarantee

SPF, DKIM, and DMARC verify identity and policy. They do not make an irrelevant message wanted.

Changing several layers at once

A new domain, provider, sequencer, audience, copy set, and sending pattern launched together are difficult to troubleshoot. Establish a known-good configuration and document changes.

Forgetting the exit plan

Every domain needs a transfer, retirement, or renewal owner. Otherwise unused assets keep billing or expire unexpectedly.

The email-domain handoff checklist

Before calling the setup complete, confirm:

• The correct business controls the registrar account.
• Multi-factor authentication and recovery are set.
• Renewal and expiration alerts have owners.
• DNS access is documented.
• The mailbox provider and billing owner are known.
• MX, SPF, DKIM, and DMARC were checked publicly.
• A real external message passed the intended authentication.
• Mailbox and sequencer ownership are recorded.
• Suppression and offboarding paths are defined.
• No credentials or customer records are stored in public planning documents.

The domain name is the inexpensive part. Control is what makes it useful.

How many email domains should you get?

There is no responsible universal number.

A founder sending a small number of relevant messages has a different system from an agency managing separate client programs. Start from the operating boundary, not a rule repeated in a social post.

Ask which brand the domain represents, which campaign or client needs separation, who can maintain DNS and mailboxes, what happens when it is paused, and whether the team can monitor every asset it creates.

More domains create more renewals, DNS zones, mailboxes, recovery paths, and possible mistakes. Separate domains can reduce coupling between programs, but they do not make poor targeting or unwanted messages safe. Build capacity only after the current group has owners and known-good authentication.

Moving an existing domain instead of buying another one

If the business already owns the right domain, you may be able to import or connect it instead of registering a new one.

Inventory the registrar, registrant owner, authoritative nameservers, DNS host, website records, current MX, authentication records, sending services, renewal, and recovery access first.

Do not replace the whole DNS zone just to add email. Preserve unrelated website and service records. If the mailbox provider is changing, plan the migration and rollback before changing MX.

Cheap Inboxes supports importing a domain you already own. The exact work depends on the current provider and authoritative DNS. Keep the old mail path working until the new path and external authentication have been verified.

Transfer and DNS change are not the same thing

A registrar transfer changes who manages the registration. A nameserver change moves authoritative DNS. An MX change moves inbound mail. These operations can happen separately.

Name the operation precisely. “We moved the domain” is not enough for the person troubleshooting a missing website or mailbox.

Choose the registrar and mailbox provider separately

Convenience bundles can be useful, but the business should still understand each contract.

When comparing domain registration, ask:

• Is the business listed as the registrant where applicable?
• Can administrators manage nameservers, DNSSEC, transfer lock, and authorization codes?
• What is the renewal price and cadence?
• How are account recovery and ownership disputes handled?
• Can the domain move to another registrar?

When comparing mailbox service, ask:

• Is the product Google Workspace, Microsoft 365, custom SMTP, or another service?
• Who owns the tenant or workspace relationship?
• How are mailboxes added, removed, recovered, and transferred?
• Which DNS records are managed and which remain with the customer?
• How does the mailbox connect to the intended application?
• What support is available after checkout?

A provider may handle both layers. The checklist keeps ownership clear if the relationship changes.

Pick an email address format

The domain is only half the visible sender identity. Use an address format that maps to a real person or a clearly identified team.

Common business patterns include:

• first@example.com
• first.last@example.com
• firstinitiallastname@example.com
• a real function such as partnerships@example.com

Consistency makes mailbox inventories and handoffs easier. Before creating dozens of addresses, check name collisions, international names, employee changes, and how replies will be owned.

For cold email, do not invent employees to create the appearance of a larger team. The display name, address, signature, domain, and message should identify the sender honestly.

Role accounts such as info@ or sales@ may be appropriate for inbound routing and may be a poor fit for a person-to-person outbound message. Choose based on the actual job, not a universal naming rule.

Set up replies and forwarding deliberately

Outbound infrastructure is not complete when messages can leave. Replies need a monitored destination and an owner.

Test:

1. A normal reply.
2. A reply from outside the sender’s provider.
3. An out-of-office response.
4. An unsubscribe or negative reply.
5. A mailbox or alias that should not accept mail.

If replies are forwarded, verify the final mailbox, preserve the original sender, and check whether forwarding changes authentication or spam handling. Record who can edit the forwarding rule.

Do not route every client or campaign into one unowned inbox. The sequencer may display replies, but the underlying mailbox and recovery path still matter.

What to save after setup

The final asset record should let another operator take over without repeating the purchase:

domain:
business_or_client_owner:
registrar:
expiration_and_renewal:
authoritative_dns_host:
mailbox_provider:
workspace_or_tenant:
active_mailboxes:
mx_verified:
spf_verified:
dkim_verified:
dmarc_verified:
external_test_date:
sequencer_or_application:
reply_owner:
offboarding_owner:

Store passwords, tokens, and recovery codes in an approved secrets system—not in this record.

Review the inventory monthly for active sending domains and before any client handoff. The domain is ready when the business owns it, email works in both directions, authentication is proven externally, and the next person knows how to operate or transfer it.

Sources

• Information for domain-name registrants — ICANN
• Domain name registration process — ICANN
• Set up MX records for Google Workspace — Google Workspace Admin Help
• Set up SPF — Google Workspace Admin Help
• Learn about email authentication — Google Workspace Admin Help
• Email authentication in Microsoft 365 — Microsoft Learn
• Cheap Inboxes