EmpireVault

Knowledge Base / Platform & Billing / Hosted Email on Your Own Domain

Hosted Email on Your Own Domain

Published November 06, 2026

What hosted email is

EmpireVault can host the email for your own domain. Addresses such as sam@yourdomain.com then live on EmpireVault's own mail server instead of at Google, Microsoft or another provider, and they work in the Inbox, the Today page and the calendar like any other mailbox.

Who can use it

Only organisation admins, and only for organisations where EmpireVault has switched hosted email on. If you do not see an Email domain button on Platform > Mailboxes, it is not on for your organisation yet: contact support to have it turned on. Members never see these pages.

Adding your domain

Open Platform > Mailboxes and click Email domain. Type your domain (for example example.com) under Domain and click Add. EmpireVault emails the person who added it the first record to publish, and the page lists the DNS records you need. Next to the domain a status reads Unverified, Ready - MX not yet switched or Live.

The four stages, and why the order matters

The page walks through four stages in this order. Nothing changes about where your current email goes until the last one.

  1. Prove you own the domain. Publish one TXT record. This does not change your current email. The other records appear once it is found.
  2. Let EmpireVault send for the domain. Publish SPF, two DKIM records and DMARC. Three SRV records that let mail apps find the server on their own are recommended, and a TLS reporting record is optional. This does not move your email either.
  3. Create your mailboxes. This opens once the domain is Ready. Create every address that receives mail today before the next step, so nothing arrives at an address that does not exist yet.
  4. Move your email to EmpireVault. Publish the MX record. This is the switch: from the moment it is saved, new mail for the domain arrives in EmpireVault. The domain becomes Live once every required record (MX, SPF, both DKIM records and DMARC) is found.

If the domain does not receive email anywhere yet, you can do stages 2 to 4 together.

Choose your DNS provider

The page asks Where do you manage DNS for this domain? with GoDaddy, Namecheap, Cloudflare, Squarespace (including domains that used to be on Google Domains), Wix and Other. EmpireVault picks one from your domain's nameservers; change it if that is wrong. Choosing one saves at once and rewrites the steps in that provider's own words. Wix has no form that fits the SRV records, so they are skipped for Wix.

Filling in each record

Each record is shown as the boxes your provider's form has, such as Host, Value and Priority, each with a Copy button. There is also a Copy all button.

  • Type only what the Host box shows, not the full name. Most providers add the domain themselves, and typing it in full makes it appear twice. The full name is printed underneath for reference.
  • For the domain itself the Host is @. For Wix the box says to leave it empty.
  • Cloudflare accepts either the short or the full name.

SPF: one record only

A domain may have only one SPF record. The standard value is v=spf1 include:_spf.empirevaultmail.com -all. If your domain already has an SPF record, the page shows it under Found now and gives a Change it to value that keeps your existing senders and adds EmpireVault's. Edit the existing record to that value; never add a second one, because two SPF records make receiving servers ignore both. If your record uses redirect=, ask whoever set it up to add include:_spf.empirevaultmail.com to it. If the page says your SPF record can need more than 10 DNS lookups, mail from services listed late in that record can fail SPF; remove senders you no longer use or ask a sending service for a setup with fewer lookups. EmpireVault's mail is also signed with DKIM, which helps it pass when SPF fails, but receiving servers differ, so fix the record rather than rely on that.

Provider notes

  • Namecheap: in stage 4 open Mail Settings and choose Custom MX (not MXE), then add the MX row there. Custom MX turns off Namecheap Email Forwarding along with its forwarding SPF record, and any forwarding you set up stops. That forwarding SPF record goes away in stage 4, so the page does not ask you to merge it.
  • Cloudflare: if Cloudflare Email Routing is on, its MX and SPF records are locked. The stage 4 steps turn Email Routing off.
  • GoDaddy and Squarespace: an existing mail preset, such as Google Workspace or email forwarding, has to be removed (or its MX records edited), which ends delivery there.

Checking your records

Each record shows Found, Needs a fix or Not found. The page recognises common mistakes and tells you what to change: a record added with the full name so the domain was doubled, a value added at @ when it belongs on a named host, more than one SPF record, or an SPF record with redirect=.

EmpireVault reads your records from the domain's own nameservers, so a saved record usually shows within a minute or two. Some providers take longer to publish a change. Click Check records to check straight away; EmpireVault also checks every 15 minutes by itself, so you do not need to keep clicking.

If someone else manages your DNS

Click Print instructions to open a printable page with the domain, the DNS provider, the four stages and every record. The email sent when the domain is added can also be forwarded to whoever runs your DNS.

The two emails the admin receives

Both go to the person who added the domain, while they are an active member of the organisation and hosted email is on.

  • The records email arrives right after the domain is added, with the subject "Your email domain ...: the first record to publish". It gives the ownership record's Type, Host, Name and Value, links to the Email domain page and explains what happens next.
  • The live email arrives when the domain goes live, with the subject "... is live on EmpireVault: what helps its mail land". It suggests registering the domain with Google Postmaster Tools, explains that a brand-new domain may land in spam for the first weeks, asks you to keep the records published, and links to Mailboxes.

Creating hosted mailboxes

Once the domain is Ready, click Add mailbox on Platform > Mailboxes. Under Where does this mailbox live? choose On EmpireVault, at your domain. Enter a Name, choose who it is for (a member, an outstanding invitation, or shared), type the Address (the part before the @) and optionally tick Sequences or Tickets, then click Create mailbox. You never type server settings or a password. Create a mailbox for every member who has none creates one for each member at once, skipping any address that cannot be used. The number of hosted mailboxes is limited; if you reach it, contact support.

Using a hosted mailbox in a mail app

Open the mailbox's Edit page. Settings for a mail app shows the incoming (IMAP) and outgoing (SMTP) server, port and security, and the username. The password is never shown. Reset password makes a new one, shown once with a Copy button; every mail app using the old password stops working until it is updated. If the page says the server has not taken the password yet, it starts working within 15 minutes.

Removing a domain

Remove domain is refused while any of its mailboxes are active: deactivate them first. Deactivated mailboxes keep their mail on the server until support deletes them. If you add the same domain again, new DKIM keys are generated, so both DKIM records have to be published again.

Was this article helpful?

Powered by EmpireVault