Forward Email From Your Domain Without Buying Hosting

You bought a domain for your business but haven't picked a hosting plan yet - maybe the site is still "coming soon." You still want to hand out you@yourdomain.com on a business card instead of a Gmail address, and you don't want to pay for a full mailbox just to make that happen. Good news: you don't have to. Email forwarding gets you there for free, using nothing but DNS records.

What "forwarding-only" email actually means

There are two very different things people call "domain email," and mixing them up is where most of the confusion starts:

• Hosted mailbox - a real inbox that lives on a mail server (Zoho Mail, Google Workspace, Titan, or cPanel webmail). You log in, send, receive, and store mail there. This costs money per user.
• Forwarding-only alias - no inbox exists at all. Mail sent to you@yourdomain.com is caught at the DNS level and immediately relayed to an inbox you already have, like yourname@gmail.com. There's nothing to log into and usually nothing to pay for.

If you just need people to be able to email your domain and have it land in your existing Gmail or Outlook inbox, forwarding-only is the right tool. It also works even if your domain has zero web hosting attached - you don't need an A record pointing anywhere for this to function, because email routing only cares about MX records, not the website.

Why this trips people up

The usual symptom: someone sets up forwarding, sends a test email, and either nothing arrives, it bounces, or it lands straight in spam. The root causes are almost always one of these:

• The domain's nameservers or MX records still point at a previous host (a parked-domain placeholder, or a registrar's default "coming soon" MX).
• Only the MX record was added - no SPF record for the forwarding service, so receiving mail servers can't confirm the forwarder is allowed to send on the domain's behalf.
• A catch-all alias was left on by default and is now forwarding every spam bot's random guess (info@, admin@, sales@, test123@) straight into the inbox.

Setting it up: Cloudflare Email Routing (free, no card needed)

This is the fastest option if you're comfortable changing nameservers. Steps:

1. Add the domain to a free Cloudflare account and switch your registrar's nameservers to the two Cloudflare gives you. (If your domain is registered with Getwebup, this is a one-time change in Domain → Manage Nameservers.)
2. In the Cloudflare dashboard, go to Email → Email Routing and click Enable. Cloudflare adds the required MX and a Cloudflare-specific TXT record to your zone automatically - you don't type these by hand.
3. Under Destination addresses, add and verify the personal or work inbox you want mail delivered to (you'll get a confirmation email to click).
4. Under Routing rules, create an alias: e.g. hello@yourdomain.com → your verified inbox. Repeat for each alias you need (sales@, support@, etc.), or use "Catch-all address" only if you actually want every misspelled address to forward too.

Setting it up: ImprovMX (free, keeps your existing nameservers)

If you don't want to touch nameservers - say your domain already has hosting-independent DNS you'd rather not disturb - ImprovMX works by adding records directly in your existing DNS zone (cPanel's Zone Editor, or your registrar's DNS panel):

Type: MX   Name: @   Priority: 10   Value: mx1.improvmx.com
Type: MX   Name: @   Priority: 20   Value: mx2.improvmx.com
Type: TXT  Name: @   Value: v=spf1 include:spf.improvmx.com ~all

Then in the ImprovMX dashboard, add your domain, create the alias-to-inbox mapping, and verify. Propagation for MX/TXT changes usually completes within 30-60 minutes, though it can take longer depending on the previous record's TTL.

Important: if the domain currently has an active mailbox somewhere (cPanel webmail, an old Google Workspace subscription), remove or replace those MX records first. Two sets of MX records fighting each other is the single most common reason forwarding "sometimes works."

The part everyone skips: replying and SPF alignment

Forwarding solves receiving. Replying is a separate problem, and it's where most setups quietly break:

• Reply-from mismatch: if you just hit "Reply" in Gmail, it sends from your @gmail.com address, not @yourdomain.com. To reply as your domain, add a "Send mail as" alias in Gmail settings using SMTP credentials from a real mailbox provider - forwarding-only services generally don't give you outbound SMTP, since there's no mailbox to send from.
• SPF alignment on forwarded mail: when a message is forwarded, the receiving server sometimes evaluates SPF against the forwarder's IP rather than the original sender's. If your domain's own SPF record doesn't include the forwarding service (include:spf.improvmx.com or Cloudflare's equivalent), some strict mail servers will flag the forwarded copy as a soft-fail and route it to spam.
• DMARC and forwarding don't mix well by default. If you later add a strict DMARC policy (p=reject) on the domain, some forwarded mail can fail DMARC checks entirely on the receiving end, because the forwarder didn't rewrite the sender in a DMARC-compliant way. Keep DMARC at p=none or p=quarantine while relying on forwarding, and only move to p=reject once you're on real hosted mail with proper DKIM signing.

Quick troubleshooting reference

When to graduate to a real mailbox

Forwarding is genuinely fine for a solo business owner routing a handful of addresses to one inbox. It stops being enough once you need: shared team inboxes, calendar and contacts sync, mail that survives you losing access to the destination Gmail account, or a strict DMARC policy for deliverability. At that point, moving to Zoho Mail, Titan, or Google Workspace with proper MX records gives you a real mailbox with its own SMTP, DKIM signing, and storage - forwarding was just the free bridge to get you there.