Operate//guide // IT management
Business email on your own domain: how to set it up, from domain to DMARC
Registering the domain in the company’s name, choosing an email provider and the MX, SPF, DKIM and DMARC records, explained for people who do not work in IT. At the end, the mistakes that cost you later.
Updated: 17.11.2026 · ~7 min read
An address like [email protected] looks more serious on a quote than [email protected], but the important difference has nothing to do with image. When the addresses sit on the company domain, the company decides who gets a mailbox, what happens to the mail of an employee who leaves and which provider holds the email. The addresses also stay the same if you change provider a few years from now, because the domain is yours.
There are three stages. You buy the domain, choose an email provider, then add a few DNS records that tell the rest of the internet where your mail goes and who is allowed to send on your behalf.
The domain: in the company’s name, not someone at the company
A domain is bought from a registrar, a company accredited to sell domains. For .ro, the national registry is run by RoTLD, and registrations go through the registrars it has accredited. When you order, you fill in the details of the registrant, meaning the owner of the domain. The registrant should be the company, with its legal name and tax ID (CUI). Not the employee who placed the order, and not the agency that built the website.
The registrar account matters just as much. Put it on an address the company can always access, and turn on two-step authentication if the registrar offers it. Whoever controls that account can transfer the domain, change its DNS records and, in practice, take over the company’s email.
You also need to know where the domain’s DNS is managed. Usually it is at the registrar itself, but it can be moved to the hosting company or to a service such as Cloudflare. All the records below are added there, not at the email provider.
The email provider
The domain is only the name. The mailboxes live with a provider you choose separately. The usual options for a small company:
- Microsoft 365 or Google Workspace. Email, calendar, document storage and a console where you manage users. Both are paid per user, per month. What each Microsoft plan includes and what it cost on the date it was checked is in the guide to Microsoft 365 Business plans. Google’s prices are on the Google Workspace website.
- Email included with website hosting. Many web hosting packages come with mailboxes. For two or three addresses that can be enough, but storage is usually small and the email stays tied to the website’s hosting contract.
- Email-only providers. Services that sell only mailboxes on your domain, without an office suite.
Beyond price, a few questions settle the choice. Can you take over the mailbox of someone who leaves without asking for their password? Can you turn on two-step authentication for every user? Can you export all messages if you move to another provider? Can you have shared addresses, such as office@, that several people open, each with their own account?
MX, SPF, DKIM and DMARC in plain words
DNS is a kind of public phone book for the domain, readable by any server. Your email provider shows you exactly which records to add, and you copy them into the DNS panel.
MX: where mail is delivered
When someone writes to Ana at your-company.ro, the sender’s server looks up the domain’s MX record in DNS and delivers the message to the server listed there. There can be several MX records, each with a priority number. The lowest number is tried first.
SPF: who may send on behalf of the domain
SPF is a TXT record that starts with v=spf1 and lists the servers allowed to send email using your domain’s address. A receiving server checks whether the sender is on the list. The list includes your email provider and every other service that sends as the company: the invoicing software that emails invoices, the newsletter platform, the website’s contact form. A domain must have a single SPF record. Two separate records make the check fail. Ending with ~all asks for mail sent from anywhere else to be treated as suspicious, while -all asks for it to be rejected.
DKIM: a signature on every message
The provider digitally signs every message it sends, using a private key that only it holds. The public key, used for verification, sits in DNS under a name of the form selector._domainkey.your-company.ro. From the signature, the recipient learns that the message left from a server authorised by the domain and that it was not altered on the way. With some providers, including Microsoft 365 and Google Workspace, signing with your own domain is switched on separately in the admin console after you have added the records.
DMARC: what happens to forged mail
DMARC is a TXT record placed at _dmarc.your-company.ro. It tells receiving servers what to do when a message claims to come from your domain but passes neither the SPF check nor the DKIM check for that domain. The p=none policy only asks for reports, p=quarantine sends the messages to spam and p=reject refuses them. The reports, sent to the address in rua, show who has been sending email in your domain’s name. The safe order is to start with none, read the reports for a few weeks and raise the policy only once every legitimate service passes.
Since February 2024, Gmail has required every sender to have at least SPF or DKIM, and those sending more than 5,000 messages a day to Gmail addresses need all three, DMARC included.
What it looks like on an example domain
The table below is an example, not anyone’s configuration. example.ro is an example domain and furnizor-exemplu.net stands in for your provider. Take the real values from your provider’s panel.
| Type | Name | Value (example) |
|---|---|---|
| MX | example.ro | 10 mx1.furnizor-exemplu.net |
| TXT (SPF) | example.ro | v=spf1 include:spf.furnizor-exemplu.net ~all |
| TXT or CNAME (DKIM) | selector1._domainkey.example.ro | the public key or the address given by the provider |
| TXT (DMARC) | _dmarc.example.ro | v=DMARC1; p=none; rua=mailto:[email protected] |
One thing these records do not solve: they stop the sender address from being forged, but they do not stop someone who logs into the real mailbox with a stolen password. That takes two-step authentication on every account. How such an attack plays out, all the way to a payment sent to the wrong account, is described in the guide on invoice fraud with a changed IBAN.
The order to do things in
If the company already has email somewhere else, the order of the steps matters:
- create the users and mailboxes at the new provider and add the record, usually a TXT, that it uses to verify the domain is yours;
- copy the old messages, or decide how you will move them;
- change the MX record, ideally in the evening or at the weekend, when little mail comes in;
- add SPF, switch on DKIM and publish DMARC with the
nonepolicy; - set up Outlook and the phones, then send a message to an outside address and one back from it, to check that both directions work.
Common mistakes
- the domain registered in the name of an employee or of the agency that built the website. If the relationship goes bad, the company cannot move its domain without the registrant’s consent;
- the registrar account set up on an address on that very domain. When the domain expires, the website and the email stop together, so the renewal notices no longer reach anyone;
- a second SPF record, added when a new newsletter service comes along. The new service belongs in the existing record;
- DMARC set straight to
rejectbefore every service that sends on the company’s behalf is in SPF or signs with DKIM. Invoices sent from the invoicing software, for example, can end up rejected; - the MX record changed before the mailboxes exist at the new provider. Mail arriving in that window is rejected;
- a single password for office@ that everyone knows. There is no way to tell who read or deleted a message, and the password stays with everyone who has left the company.
What managing email accounts involves over the long term is described on the IT management page.
FAQ
Questions about email on your own domain
Can I get an email address on my company domain for free?
You pay for the domain either way. Mailboxes may come with your website hosting, and a few providers have free plans with limits. Microsoft 365 and Google Workspace are paid per user once the trial ends. With a free option, check whether you can take over the mailbox of someone who leaves.
How long until the new address starts working?
The mailbox can send messages as soon as it is created and the domain is verified. Mail from outside starts arriving at the new provider once the MX change has propagated. How long that takes depends on the TTL set on the record, usually anywhere from a few minutes to a few hours.
What happens to my old emails when I change provider?
They stay with the old provider. Changing the MX record only moves mail that arrives from then on. You copy the old messages through a migration, and close the old account only after checking that everything has arrived.
Why do our company emails land in the recipients’ spam folder?
The usual causes are a missing or incomplete SPF record, DKIM that was never switched on, no DMARC record, and messages sent from a service that is not listed in SPF, such as the invoicing software or the newsletter platform. Send a message to a Gmail address: in the menu of the received message, the option that shows the original message tells you whether SPF, DKIM and DMARC passed.
Do I need a separate licence for office@ or accounts@?
It depends on the provider. In Microsoft 365, shared addresses can be shared mailboxes, which need no licence of their own, and each person opens them with their own account. Other providers offer aliases, meaning an extra address for the same mailbox, or groups that deliver the message to several people.
Setting up email on your company domain?
If you would like help choosing a provider, with the DNS records or with moving your old email, get in touch.