What is email on your own domain?
And what a company needs to have ready before using it.
Short answer
Domain email is a mailbox whose part after the @ is your company's own domain — accounts@company.com rather than company.accounts@gmail.com. Technically it is ordinary email: it still exchanges mail with every other system, and still opens in Outlook or on a phone. The difference is who owns the address: the domain belongs to the company, so the mailbox does too, rather than belonging to whoever's personal account is using it.
Why a business needs it
- When someone leaves, the address stays with the company. With a personal Gmail mailbox, the whole history of dealings with a customer walks out of the door with the person, and you have no way to get it back.
- Customers and partners read the address to judge whether you are real. A quote sent from the company domain reads very differently from a quote sent from a free mailbox.
- You control your own sending reputation. Your own domain lets you sign your mail and publish an anti-spoofing policy — the thing that decides whether mail lands in the inbox or in spam.
- It is manageable: create mailboxes for new joiners, lock the mailbox of someone who left, set up shared addresses like support@ or accounts@ that several people read.
What you need to start
A domain name
If your company has a website, you already have one — use it. If not, buy one from any registrar; this is a separate cost, paid to the domain registrar rather than to the email service.
An email service
The thing that actually stores the mail and runs the sending and receiving servers. This is the part you pay for monthly or yearly.
Permission to edit the domain's DNS
You need access to the domain's control panel to add a few records, which is how the rest of the world learns where mail for your domain should go. If someone else holds the domain on your behalf, ask them for access or ask them to add the records for you.
How long it takes
Creating the mailboxes takes minutes. The waiting is DNS: after you add the records, name servers around the world need time to pick them up — typically minutes to a few hours, depending on the TTL your domain provider uses. While you wait, incoming mail may still go to the old place, so don't cancel the old service on the same day you switch.
Three common mistakes
Confusing forwarding with a real mailbox
Many registrars throw in "email forwarding": mail to you@company.com is forwarded to your Gmail. It sounds like enough, but you can only RECEIVE — when you reply, the mail still leaves from the Gmail address. The customer sees a personal address, and the conversation isn't in the company's hands.
Using the domain inside Gmail without publishing anything
Setting your display name to "ABC Company" and sending from Gmail does not make the address the company's. Recipients still see the @gmail.com ending, and filters get more suspicious, not less, if you try to make the reply address differ from the sending one.
Pointing DNS and then forgetting
Pointing the MX record only solves RECEIVING. For the mail you SEND not to be treated as forgery, you also need the anti-spoofing records. This is the single most common reason a newly-configured domain has its mail dropped straight into spam.
Next step
If you're about to do this: look at the list of records you'll need on the DNS guide, and the explanation of MX, SPF, DKIM and DMARC if you want to understand what you're adding.