Mail on your own domain: hosting or a separate service
There are three ways to get an address like info@yourdomain.com: the mail already included in your hosting plan, a separate business mail service or your own mail server on a VPS. They differ in price, in how reliably messages get delivered and in what happens to your mail when the website moves. Below: how to choose and how to set up DNS so that the website and mail can live in different places without trouble.
The short answer. If you have a few mailboxes and the website is already on shared hosting, the mail in the plan is enough: it costs nothing extra and is set up in the same panel. A separate service is worth it when you have more than ten or so employees, mail is critical to the business, you need calendars and shared documents, or the website may move to another host. Your own mail server on a VPS only makes sense if you are ready to look after the IP address reputation and spam filters.
How the website and mail share one domain
Where the domain's mail goes is set by the MX DNS record (RFC 5321), and where website visitors go is set by the A and AAAA records. They are independent: the website can run on shared hosting while MX points to a mail service. So your choice of mail does not tie you to a host, as long as the DNS records are set up correctly. How records work and where to manage them is covered in the article Domains and DNS.
Three options
| Mail on hosting | Separate service | Own server on a VPS | |
|---|---|---|---|
| Price | Included in the plan | Usually a fee per user | The VPS price and your time |
| Number and size of mailboxes | Within the plan limits | As many as you pay for | As much as fits on the disk |
| Sending | A limit on messages per hour per account or domain | The service's per-user limits | Needs an open port 25 and a clean IP |
| Deliverability | A shared IP with the other users of the server | The reputation of a large service | Depends entirely on you |
| When the website moves | Mail has to be moved with it | Does not change | Does not change |
| Calendars, documents, mobile clients | Usually only IMAP and webmail | Included | You install and update them yourself |
Mail in a hosting plan
According to the accsly.io catalog as of 15 November 2026, the number of mailboxes is stated for 1,810 of the 9,497 hosting plans. 973 of them offer unlimited mailboxes, 190 up to five, 142 from 6 to 10, 489 more than ten, and 16 have no mail. A plan with at least ten mailboxes costs $9.99 or €14 a month in the middle of the market at hosts outside Russia and ₽729 at Russian hosts. Examples as recorded in the catalog:
- SpaceWeb, "Vzlyot": ₽311 a month: 5 sites, unlimited mailboxes, 10 GB;
- Timeweb, "Optimo": ₽729: 15 sites, 10 mailboxes, 40 GB;
- Directnode, "Standard": €1.95: 10 mailboxes, 5 GB.
"Unlimited" refers to the number of mailboxes, not to sending or space. Mail uses the plan's disk together with the website, and the number of messages per hour is limited: in cPanel, for example, the host sets a limit per domain and per account. Besides, mail goes out from the server's shared IP: if another user on the server sends spam, delivery of your messages suffers too. More about mail limits and mailbox backups in the article Hosting for a company website and domain mail.
A separate mail service
Mail for a domain is offered by Yandex 360 for Business and VK WorkSpace (popular in Russia), Google Workspace, Microsoft 365, Zoho Mail and other services. You confirm ownership of the domain with a DNS record, change MX to the service's addresses and create mailboxes for employees. What you gain: spam filters and the reputation of a large sender, large mailboxes, calendars and mobile apps, and mail that does not depend on the website's host. What you pay: usually a monthly fee for each user. Service prices change and are not part of the accsly catalog, so compare them on the services' websites. If your messages will contain personal data of customers from Russia, choose a service that stores it in Russia (see 152-FZ and hosting, about Russia's personal data law).
SPF, DKIM and DMARC when there are several senders
The most common mistake when splitting the website and mail is that messages from the website stop arriving. The website sends notifications and orders from the hosting server, while the recipient sees that the domain has authorised only the mail service to send. The rules are:
- SPF: one record per domain. If there are two TXT records with v=spf1, the check ends in an error (RFC 7208, section 3.2). All senders are listed in a single record:
v=spf1 include:<mail service record> include:<hosting record> ~all. A record may make no more than 10 DNS lookups (section 4.6.4), so remove unnecessary includes. - DKIM: each sender has its own key. Signatures differ by selector (RFC 6376), so the service's and the hosting's records do not interfere with each other: turn on DKIM in both panels and add both records.
- DMARC: one policy for the domain in the _dmarc record (RFC 7489). Start with p=none and an address for reports, check after a couple of weeks that all legitimate senders pass SPF or DKIM, and only then switch to quarantine or reject.
This is not a formality: Gmail requires SPF or DKIM from all senders, and SPF, DKIM and DMARC together from those who send more than 5,000 messages a day. An even simpler option is to send the website's messages not from the hosting but through the SMTP of the same mail service or of a mailing service: then the domain has a single sender.
How to move mail without losing messages
- Create mailboxes with the same addresses in the new place.
- A day before the move, lower the TTL of the MX record, for example to 300 seconds, so that the change spreads quickly.
- Copy old messages over IMAP: many services have a built-in import, and for your own server the open-source tool imapsync will do.
- Change MX and update SPF and DKIM for the new sender.
- Do not delete the old mailboxes for a few more days: some senders keep delivering mail using the old records for a while. Repeat the IMAP copy to pick up messages that arrived in the meantime.
Your own mail server on a VPS
Your own server gives you full control and does not limit the number of mailboxes, but deliverability is entirely up to you: an open outgoing port 25, a PTR record, a clean IP address, a spam filter and updates. What this takes is covered in the article Mail server on a VPS: SPF, DKIM, DMARC, and a selection of servers is in VPS for a mail server. For a small company this usually costs more in time than hosting or a service.