How to Add Your Own Domain to Mailbox Hosting

Ready to move off the shared free domain and start using [email protected]? Here's the actual process.

Step 1: Order a Paid Mailbox Plan

Custom domains are a paid-tier feature — pick a plan from our Mail Hosting products. At checkout, you'll be asked for the domain you want to use.

Step 2: Domain Gets Added Automatically

Once your order is provisioned, your domain is automatically added to our mail platform on the backend — you don't need to manually configure anything on our side. Your service's management page will then show you the exact DNS records you need to add at your domain registrar or DNS provider (wherever your domain's nameservers actually point).

Step 3: Add the DNS Records

You'll be given:

• MX record — tells the world where to deliver mail for your domain (points at our mail servers).
• SPF record — authorizes our servers to send on your domain's behalf.
• DKIM record — a public key for signature verification, generated specifically for your domain.

Add each one exactly as shown at your DNS provider (Cloudflare, GoDaddy, Namecheap, wherever your domain is managed) — see our DNS records explainer if the terminology (TXT, MX, record types) is unfamiliar.

Step 4: Wait for DNS Propagation

DNS changes aren't instant — depending on your provider and your domain's TTL settings, it can take anywhere from a few minutes to a few hours (rarely, up to 24-48 hours) for changes to fully propagate globally. Mail sent before propagation completes may not route correctly.

Step 5: Create Your Mailboxes

Once DNS is confirmed working, create mailboxes on your domain from your service's management page — each one gets its own address ([email protected], [email protected], etc.) and its own credentials.

Common Issues

• Mail not arriving: almost always an MX record issue — double-check it points exactly where specified, with no typos, and that no OTHER conflicting MX record exists from a previous mail provider.
• Mail landing in spam: check that SPF and DKIM are both actually verifying — a missing or malformed DKIM record is a common, easy-to-miss cause.
• "Domain already in use" errors: a domain can only be actively configured on one mail platform's MX records at a time — if you're migrating from another provider, you'll need to fully cut over rather than run both simultaneously.

Migrating From an Existing Mail Provider

If you already have mail flowing through another provider on this domain, plan the cutover deliberately — set up everything here first, verify it's working, then switch the MX record over as the final step, rather than changing MX first and scrambling to configure everything else afterward.