You registered a domain for your side project. Now you need a professional address. You do not need another inbox to monitor.
Free custom domain email forwarding lets you receive mail at hello@yourdomain.com inside your existing Gmail or Proton account. There is no monthly fee. There is no new app to open.
This is not a hack. It is a standard DNS feature.
Large teams pay for managed mailboxes because they need shared drives and calendars. Solo founders usually just need to receive password resets, investor replies, and customer support threads. For that, forwarding is enough.
Why a Custom Domain Email Still Matters
Using yourname@gmail.com on a landing page signals that you are not fully committed. A custom domain email costs nothing beyond the domain itself and takes ten minutes to configure.
More importantly, it keeps you portable. If you switch email providers tomorrow, your address stays the same. Your users never need to update their contact list.
Ownership matters. When you rely on a consumer Gmail address, Google controls the namespace. They can lock accounts without warning.
With your own domain, you control the routing logic. You can point it anywhere.
Forwarding also reduces cognitive load. You check one inbox. One spam folder. One notification badge. The mail simply arrives in the place you already live.
It also makes your operation look larger than it is. A founder with a domain-matched address reads as more established than one using a consumer handle. Early customers notice these details.
A custom domain email gives you several practical wins:
- Portability. Move between Gmail, Proton, or Fastmail without changing your public address.
- Reusability. Use role addresses like
billing@andpress@that all land in your main inbox. - Trust. Corporate buyers and beta testers are more likely to reply to a domain they recognize.
Free Custom Domain Email Forwarding: Three Providers Compared
Not all forwarding services are equal. Some hide catch-all routing behind a paywall. Others force you to use their DNS hosting. Here is how the most common free tiers stack up.
| Provider | Free Tier | Catch-All | Outbound SMTP | DNS Requirement |
|---|---|---|---|---|
| Cloudflare Email Routing | Unlimited aliases | Yes | No | Cloudflare DNS only |
| ImprovMX | Available | Yes | No | Any provider |
| Forward Email | Available | Yes | No | Any provider |
Cloudflare offers the most generous free tier, but it is a closed ecosystem. If you prefer to keep DNS at Porkbun or Namecheap, use ImprovMX or Forward Email instead.
All three options preserve the original envelope sender. That means spam filters at Gmail or Proton see the real origin, not the forwarder. Delivery rates stay high.
If you already run DNS through Cloudflare for caching or Workers, Email Routing is the obvious choice. It lives in the same dashboard. You do not need to manage another vendor relationship.
Email Forwarding Setup Step by Step
The process is the same regardless of provider. You tell the world where to deliver mail for your domain. Then you tell your forwarding service where to send it.
Pick your provider. Sign up with the service that matches your DNS setup. If your domain already uses Cloudflare nameservers, use Cloudflare Email Routing. Otherwise, create an ImprovMX or Forward Email account.
Verify domain ownership. Add a unique
TXTrecord to your DNS zone. This proves you control the domain. The provider will give you a hostname and value that looks likeforward-email=abc123orcloudflare-verify=xyz.Add MX records. Delete any existing MX records first. Then add the ones your provider specifies. These entries tell other mail servers where to hand off messages.
Configure destination addresses. In your provider dashboard, map your custom address to your personal inbox. For example, route
hello@example.comtoyou@gmail.com.Test delivery. Send an email from another account to your custom address. Check your personal inbox. If it does not arrive within two minutes, check spam.
Here is what a typical ImprovMX zone file looks like for example.com:
example.com. 3600 IN MX 10 mx1.improvmx.com.
example.com. 3600 IN MX 20 mx2.improvmx.com.
example.com. 3600 IN TXT "v=spf1 include:spf.improvmx.com ~all"
Propagation usually takes a few minutes. You can verify your MX records from the terminal:
dig MX example.com +short
The output should show your provider's servers, not your registrar's default parking page.
If you see old records, flush your local DNS cache or use a public resolver like 1.1.1.1. Some registrars cache aggressively.
Sending Mail From Your Domain (The Reality)
Forwarding handles inbound mail. It does not let you send as you@example.com unless you add outbound SMTP. Most free tiers do not include this. Gmail allows you to add a "Send mail as" alias, but without authenticated SMTP through your domain, the message will still carry Gmail's infrastructure headers.
Replying to a forwarded message from your personal Gmail exposes your personal address in the Reply-To field unless you manually override it every time.
If you only need to receive contact form submissions and Stripe receipts, ignore outbound sending. Your customers do not care what your reply address is as long as you respond.
If you must send as your domain, consider a transactional email provider. Mailgun, Postmark, and SendGrid all offer SMTP credentials you can paste into Gmail's "Send mail as" settings. Their free tiers are generous enough for a solo founder's volume.
DNS Hygiene for Deliverability
Mail providers distrust new domains. A few extra records signal that you are not a spammer.
Add an SPF record. This lists which servers are allowed to send mail for your domain. Since your forwarder does not send on your behalf, a minimal SPF record looks like this:
"v=spf1 -all"
This tells receivers that nobody should send mail from your domain. It is honest and stops spoofing.
If you later add outbound SMTP through Mailgun, update the record to include their servers:
"v=spf1 include:mailgun.org ~all"
DMARC is optional for forwarding-only setups. Once you enable outbound sending, add a simple DMARC policy:
"v=DMARC1; p=none; rua=mailto:dmarc@example.com"
These records live as TXT entries on your apex domain. They cost nothing and prevent your domain from being used in phishing campaigns.
Check your work with online tools. The MX Toolbox SuperTool queries multiple global resolvers at once. It catches typos that local tests miss.
FAQ
Do I need Google Workspace to get custom domain email?
No. Google Workspace is a full productivity suite with calendars, storage, and shared drives. If you only need to receive mail at you@yourdomain.com, free forwarding is sufficient. You keep your existing Gmail inbox and pay nothing extra.
How long does email forwarding setup usually take?
The configuration itself takes five to ten minutes. DNS propagation is the variable.
Most global DNS resolvers pick up new MX records within a few minutes. Some older caches hold stale data for up to an hour. If your test mail bounces, wait thirty minutes and try again.
Can I forward to multiple inboxes at once?
Yes. Most providers let you create multiple destination rules. You can send support@example.com to one inbox and founder@example.com to another.
Some services also support catch-all routing, where anything @example.com lands in a single inbox. Check your provider's dashboard for alias limits on the free tier.
Will forwarded emails end up in spam?
Occasionally. The risk is low if your DNS records are clean and your provider has a good reputation.
To reduce friction, add your custom domain as an "allowed sender" inside Gmail or Proton. Never mark a forwarded test message as spam. Doing so trains the algorithm to distrust your own address.
What happens if my forwarding provider shuts down?
You lose no mail history. Forwarded messages already live in your destination inbox.
To restore service, you simply update your MX records to point at a new provider. That is the beauty of owning the domain. The address stays the same even if the vendor changes.