How to Create an Email Address With Your Domain Name

The short answer. Buy a domain, pay an email provider from about 1 dollar per user per month, and paste three or four DNS records into your registrar. Twenty minutes, start to finish. You do not need hosting and you do not need a website.

Sending from a Gmail or Outlook address is the fastest way to look like a hobby. An address at your own domain is the cheapest credibility you will ever buy, and the setup is far less technical than people expect.

---

What you actually need#

Three things, and one of them you probably already have.

You do not need web hosting. Email and websites are routed by completely separate DNS records. You can have a working address at a domain that serves no website at all.

---

How it works in one paragraph#

When someone emails [email protected], their mail server asks DNS a single question: which servers receive mail for this domain? The answer comes from your MX records. Whatever those point at is where your mail goes. Setting up email is really just setting those records correctly and proving to the world that you meant to.

---

What it costs in 2026#

Prices are per user, per month.

The cheaper routes

Your registrar may include forwarding for free. Several registrars will forward [email protected] to an inbox you already have, at no cost. This is genuinely useful for a solo project, with one catch covered below.

Some hosting plans bundle mailboxes. They work, though the deliverability and spam filtering are usually weaker than a dedicated provider, and you have tied your mail to your host.

Forwarding is not sending. A free forward delivers incoming mail to your personal inbox, but when you reply it goes out from your Gmail address. The recipient sees the wrong name. To send as your domain you need a real mailbox, or an SMTP relay your provider supports.

---

The setup, step by step#

1. Have a domain. If you do not yet, check what is available first, since the name matters more than the provider.

2. Choose a provider from the table above. For one person, Zoho is hard to beat on price. For a team that lives in shared documents, Google Workspace or Microsoft 365 will pay for itself.

3. Verify you own the domain. The provider gives you a TXT record to add at your registrar. Paste it in and click verify. This normally confirms within minutes.

4. Point your MX records at the provider. They will give you the exact values, usually two to five entries with priority numbers. Delete any existing MX records first, because leftovers from a previous setup will silently misroute mail.

5. Add SPF, DKIM and DMARC. This is the step people skip, and it is the step that decides whether you land in the inbox. More below.

6. Create your addresses. Start with one. Most providers let you add aliases like support@ and billing@ to the same mailbox for free, which is far cheaper than paying per user for addresses nobody staffs.

7. Send a test in both directions. Email yourself from an outside address, then reply. Check the reply arrives and shows the right sender.

---

The three records that decide whether your mail arrives#

This is the part that separates a working setup from one that quietly lands in spam.

All three are DNS records your provider generates for you. Adding them is copy and paste.

Start DMARC in monitoring mode. Set the policy to p=none first and read the reports for a couple of weeks before tightening to quarantine or reject. Going straight to reject on a domain with an unnoticed sender, such as your invoicing tool, will bounce legitimate mail on day one.

One SPF rule worth memorising

A domain may have exactly one SPF record. If you use several services that send on your behalf, they all go inside that single record. Adding a second one breaks both.

---

Which addresses to actually create#

There is real data on this. An analysis of over 200,000 email registrations across more than 180 countries produced a clear ranking of which aliases businesses actually create.

The 30 most common, in order

The headline finding is that info@ wins, and it is not close. If you assumed hello@ had taken over, the data says otherwise: it lands fifth. hello@ reads warmer and suits a small brand, but info@ is what people guess when they are trying to reach you without looking, and guessability is worth more than tone.

The other pattern in that list is that departmental addresses dominate personal ones. There are more marketing@ registrations than any individual first name, because role addresses outlive the people staffing them. When someone leaves, the address stays and the handover is a mailbox setting rather than a mass email telling customers to write to somebody new.

---

The addresses the standards expect

Separately from what is popular, there is a specification for this. RFC 2142, Mailbox Names for Common Services, Roles and Functions (May 1997), defines the addresses an organisation on the internet is expected to answer.

The RFC's own framing is that organisations should support at least each mailbox name for which the function actually exists. You are not expected to create uucp@ in 2026.

Two are worth taking seriously regardless of size:

postmaster@ is effectively mandatory. Any host running an SMTP server is required to accept mail at postmaster, a rule inherited from RFC 822. Some receiving systems and certificate authorities test it, and a domain that bounces postmaster looks misconfigured to the machines that judge you.

abuse@ is the de facto standard for reports of misbehaviour originating from your domain. If your account is ever compromised and starts sending spam, this is where the report lands. A domain with no working abuse address gets blocklisted rather than warned.

Both can be aliases pointing at your normal inbox. They cost nothing and they prevent a category of problem that is very unpleasant to debug later.

---

What to actually set up

On day one, create one real mailbox and use your own name, or hello@ if you prefer a neutral front door.

Add info@ and contact@ as aliases to that same mailbox. They are the two people guess most, and aliases are free at essentially every provider.

Add postmaster@ and abuse@ as aliases for the reasons above.

Add departmental addresses only when the department exists. A careers@ on a one-person company that nobody reads is worse than not having one.

Aliases are free. Seats are not. Every provider on the pricing table charges per mailbox, not per address. A single paid seat can comfortably answer to eight or ten aliases, so paid seats should match actual humans, never functions.

The one to avoid

Do not use noreply@.

It tells customers you are not interested in hearing back, which is a strange thing to say in your first interaction with them. It also costs you deliverability signals: replies to a sending address are a positive engagement signal to filters, and an address that structurally cannot receive them forfeits that. If you need to discourage replies, say so in the message and still accept them.

---

Common mistakes#

Leaving the old MX records in place. Mail splits unpredictably between two systems and you lose messages without any error.

Transferring the domain and forgetting the records. DNS records do not travel with a registration. This breaks email far more often than it breaks websites, because nobody thinks to test it.

Letting the domain expire. Your mail stops instantly, and password resets for every account tied to that address stop with it. This is the failure that turns an inconvenience into a genuine emergency, and it is why monitoring expiry on names you actually use is worth setting up on day one.

Using a free-domain extension. Deliverability on the cheapest extensions is measurably worse, because filters have learned what tends to arrive from them. Worth reading before you economise here.

---

Do it in this order#

1. Register the domain
2. Add the email provider and verify ownership
3. Replace the MX records
4. Add SPF, DKIM and DMARC in monitoring mode
5. Test both directions
6. Turn on auto-renew, then tighten DMARC

The whole thing is an evening at most, and it is the single cheapest upgrade to how a business is perceived.

Provider pricing reflects publicly listed 2026 rates and changes frequently. Check current pricing before committing.