Set Up Zoho Mail or Titan Email With Your Getwebup Domain

You bought a domain through Getwebup and want professional email — you@yourdomain.com — but you don't want to run your own mailbox through cPanel webmail. Zoho Mail and Titan Email are the two providers we get asked about most, especially from customers who came from GoDaddy or a reseller panel where Titan was bundled in. Both work fine on a Getwebup domain. Both also fail in the exact same way if you skip one step: cPanel quietly keeps routing mail to itself even after your MX records point elsewhere.

Why Not Just Use cPanel Webmail?

cPanel's built-in email (Roundcube/Horde, whatever theme you're on) is fine for a handful of accounts and it's free with hosting. But it doesn't give you a real inbox app on your phone with push notifications, shared calendars, or a spam engine that's tuned the way Gmail's is. Zoho Mail's free tier covers up to five users on one domain with 5GB each; Titan is usually a paid add-on (often ₹99–₹150/user/month through resellers) with a cleaner Outlook-style interface. Neither replaces your hosting — they just take over where incoming and outgoing mail for your domain actually lands.

Before You Touch DNS

Check what's currently handling mail for your domain

Log in to cPanel and open Email → Email Routing. If it says Local Mail Exchanger, your server is currently accepting mail itself and creating mailboxes locally — regardless of what your MX records eventually say. You'll need to flip this later, so just note it for now.

Drop your MX TTL a day ahead if you can

If your domain has been live for a while, its MX record probably has a long TTL. In Zone Editor → Manage, edit the existing MX entry and drop the TTL to 300 seconds. This isn't required, but it means the switch propagates in minutes instead of up to 24-48 hours.

Setting Up Zoho Mail

Step 1 — Verify domain ownership

In the Zoho Mail admin console, add your domain and Zoho will give you a TXT (or CNAME) verification record. Add it in cPanel's Zone Editor exactly as shown — the value is unique per account, so copy it rather than retyping:

Type: TXT
Host: yourdomain.com
Value: zoho-verification=zb XXXXXXXX.zmverify.zoho.in

Click Verify in Zoho once the record has saved. If it fails immediately, wait 5-10 minutes — cPanel's nameservers usually pick up new zone records fast, but Zoho's checker can be a step ahead of propagation.

Step 2 — Add the MX records

Remove any existing MX record pointing at your own mail server, then add Zoho's (India data center shown; use the .com versions if your Zoho account is on the US data center):

Priority 10   mx.zoho.in
Priority 20   mx2.zoho.in
Priority 50   mx3.zoho.in

Step 3 — Add SPF

If you don't already have an SPF record, add one. If you do, add Zoho's include to the existing one instead of creating a second TXT record — two SPF records is a common way to break SPF entirely:

Type: TXT
Host: yourdomain.com
Value: v=spf1 include:zoho.in ~all

Step 4 — Add DKIM

Zoho generates a domain key under Mail Admin → Domains → DKIM. Add it as a TXT record at the exact selector and host Zoho shows you — it's usually something like zoho._domainkey.yourdomain.com, but confirm in your dashboard since the selector name can change per account.

Setting Up Titan Email

Titan's setup is the same shape, different values. If you signed up through a reseller, the DNS records are usually auto-suggested inside the Titan onboarding wizard — copy them from there rather than from memory, since resellers sometimes use their own mail cluster.

Standard Titan records

MX   Priority 10   mx1.titan.email
MX   Priority 20   mx2.titan.email

TXT  yourdomain.com   v=spf1 include:spf.titan.email ~all

TXT  titan1._domainkey.yourdomain.com   (value shown in Titan console)
TXT  titan2._domainkey.yourdomain.com   (value shown in Titan console)

Titan also asks for a verification TXT record before it'll let you finish setup — same idea as Zoho's, just add it and wait for the check to pass.

The Step Everyone Skips: Fix Email Routing

This is the one that generates support tickets. Your MX records can be perfect and mail will still bounce, duplicate, or silently vanish if cPanel is still set to Local Mail Exchanger. Go back to Email → Email Routing and switch it to Remote Mail Exchanger. This tells Exim (cPanel's mail server) to stop trying to deliver mail locally and let it go wherever your MX records point.

If you leave it on Automatic Detection, cPanel only rechecks MX records at the moment you save that setting — it won't notice a change you make afterward. Set it explicitly to Remote so it doesn't quietly revert.

Verifying It Actually Worked

From a terminal, not a browser cache that might be lying to you:

dig MX yourdomain.com +short
dig TXT yourdomain.com +short
dig TXT selector._domainkey.yourdomain.com +short

Send a test email from an outside address (Gmail is fine) to your new mailbox, and send one back out. Check the headers on the reply for spf=pass and dkim=pass — most webmail clients show this under "Show original" or "View source."

Common Errors and What They Actually Mean

Prevention: What to Do Before the Next Change

• Keep a copy of your MX, SPF, and DKIM records somewhere outside cPanel — a note, a doc, anything — before you change providers again.
• Don't delete the old MX record until the new one has been live and tested for at least 24 hours.
• If you ever add a third mail-sending service (a CRM, a marketing tool, a contact form), add it to the existing SPF record's include: list — never create a second SPF TXT record.
• Set a calendar reminder to re-verify DKIM after any DNS migration or nameserver change, since it's easy to lose that TXT record in a bulk zone import.

Wrapping Up

Zoho Mail and Titan Email both run fine on a Getwebup-hosted domain — the DNS side is a handful of MX, TXT, and SPF/DKIM records, same as any external mail provider. The part that actually causes downtime is almost never the records themselves; it's cPanel's Email Routing setting quietly staying on Local after you've moved everything else. Check that first, and second, and after every DNS change you make down the line.