You bought the domain. You built the product. Now you need email that doesn't end in @gmail.com. The good news: free custom domain email forwarding exists, and it takes about fifteen minutes to set up. You don't need Google Workspace, Microsoft 365, or any paid mailbox to receive mail at you@yourdomain.com.
This guide walks through the exact email forwarding setup for a custom domain email address that lands in your existing Gmail or Outlook inbox. No credit card. No monthly fee. Just DNS records and a forwarding rule.
What You Need Before You Start
You need three things. All of them are free or already sitting in your account.
- A domain name registered with a provider that includes email forwarding.
- Access to that registrar's DNS settings.
- An existing inbox where you want forwarded mail to arrive.
Most registrars include basic email forwarding with domain registration. Cloudflare offers it through their free Email Routing product. Namecheap includes free forwarding on every domain. Porkbun does too. If you bought your domain from GoDaddy, forwarding is available but buried in their workspace upsell flow.
Some registrars advertise "free email" but mean a 30-day trial of a hosted mailbox. What you want is forwarding only. If the setup asks for a per-user license, you're in the wrong menu.
How Email Forwarding Actually Works
Email forwarding is not a mailbox. It's a relay. When someone sends mail to hello@yourdomain.com, your DNS records tell the sender's mail server where to deliver it. Instead of a mailbox server, the message goes to a forwarding service that rewrites the envelope and sends it to your personal inbox.
This matters for one reason: you can receive mail, but you can't send from that address without extra setup. Forwarding is receive-only. Sending from hello@yourdomain.com requires either a paid mailbox or a free transactional email service like Resend or Brevo configured with SPF and DKIM.
For most early-stage founders, receive-only is fine. You want customers to reach you. You can reply from Gmail with a "send as" alias later if needed.
Step 1: Find the Email Forwarding Section in Your Registrar
Log into your domain registrar. Look for a menu item called Email Forwarding, Email Routing, or Free Email.
Here's where it lives at the major registrars:
| Registrar | Forwarding Feature | Setup Path | Notes |
|---|---|---|---|
| Cloudflare | Email Routing | Domain → Email → Email Routing | Free, unlimited aliases, no mailbox included |
| Namecheap | Free Email Forwarding | Domain List → Manage → Advanced DNS → Mail Settings | 100 free forwarders per domain |
| Porkbun | Email Forwarding | Domain Management → Email Forwarding | Unlimited forwarders, clean UI |
| GoDaddy | Email Forwarding | Domain Settings → Manage DNS → Forwarding | Tries to upsell Microsoft 365; skip it |
If your registrar doesn't offer forwarding, you can move just your DNS to Cloudflare for free. Your domain stays registered where it is. Cloudflare's Email Routing works with any domain using their nameservers.
Step 2: Create Your Forwarding Rule
In the forwarding section, create a new rule. You'll typically fill in two fields:
- Alias or local part: the part before the
@symbol. Usehello,support,founder, or your first name. - Destination address: your existing Gmail, Outlook, or Proton inbox.
Create one rule for each address you want. Start with hello@yourdomain.com. Add support@ later if you grow a team.
Create a catch-all rule if your registrar supports it. A catch-all forwards anything sent to your domain, including typos like hlep@yourdomain.com. It's a safety net for early customer emails.
Step 3: Add the DNS Records
This is the part people get wrong. Forwarding requires specific DNS records. Your registrar will show you the exact values, but here's what you're adding and why.
MX Records
MX records tell the world where your mail should be delivered. For Cloudflare Email Routing, you'll add three MX records with priorities like 10, 20, and 30. For Namecheap, you'll add one MX record pointing to mx1.forwardemail.net or similar.
Here's a real example of Cloudflare Email Routing MX records:
Type Name Content Priority
MX @ route1.mx.cloudflare.net 10
MX @ route2.mx.cloudflare.net 20
MX @ route3.mx.cloudflare.net 30
TXT Records for SPF
Some forwarding services ask you to add a TXT record for SPF. This tells receiving servers that the forwarding service is allowed to send mail on your behalf. Without it, forwarded mail sometimes lands in spam.
A typical SPF record for forwarding looks like:
v=spf1 include:_spf.forwardemail.net ~all
Add exactly what your registrar tells you. Don't copy values from this article and paste them into your DNS. Every forwarding provider uses different endpoints.
Step 4: Verify and Test
Most forwarding services send a verification email to your destination inbox. Click the link. Then test the whole flow.
Send an email from a different account to your new custom domain email address. Use a personal Gmail or a friend's address. Check that it arrives in your destination inbox within a minute or two.
Then check the spam folder. If it landed in spam, your SPF record is probably missing or wrong. Fix that before you put the address on your website.
What About Sending Replies?
Forwarding is one-way. When you reply from Gmail, the recipient sees your personal address, not hello@yourdomain.com. That's fine for some founders. It's confusing for others.
You have three options for sending from your custom domain email:
- Gmail "Send mail as" alias: Gmail lets you add another address to send from. You'll need SMTP credentials from somewhere, which usually means a paid mailbox or a free transactional email service.
- Free transactional email: Resend has a free tier that includes sending from your domain. Brevo offers 300 free emails per day. Configure SPF and DKIM, then use their SMTP server in Gmail's "Send mail as" settings.
- Just receive: For the first few months, receiving is enough. Customers email you. You reply from Gmail. Nobody notices the mismatch unless you point it out.
Start with forwarding-only. Add sending later if you actually need it. Most solo founders don't for the first year.
Common Setup Mistakes
The email forwarding setup fails for predictable reasons. Here are the three I see most often.
- Wrong MX priority values. If you add two MX records with the same priority, some senders pick randomly. Follow the priority numbers exactly.
- Leaving old MX records in place. If your domain previously pointed to a website host with mail services, those MX records might still exist. Delete them before adding new ones.
- Forgetting the TXT record. Forwarded mail without SPF often gets flagged. Add the TXT record even if your registrar says it's optional.
Free Custom Domain Email Forwarding vs. Paid Mailbox
At some point, you might outgrow forwarding. Here's the honest comparison.
| Feature | Free Forwarding | Paid Mailbox (e.g. Google Workspace) |
|---|---|---|
| Receive email at your domain | Yes | Yes |
| Send from your domain | No (needs extra setup) | Yes |
| Multiple users | Limited or manual | Yes |
| Storage | None (relies on personal inbox) | 30 GB+ per user |
| Spam filtering | Basic | Advanced |
| Cost | $0 | $6–$18 per user per month |
For a solo founder validating an idea, forwarding wins. For a team of three handling customer support, a paid mailbox becomes worth it. The switch is easy: update your MX records and you're done.
FAQ
Is free custom domain email forwarding actually free?
Yes, with the right registrar. Cloudflare, Namecheap, and Porkbun all include forwarding at no extra cost with domain registration. Some registrars like GoDaddy technically offer it but push paid plans. Read the fine print before you commit to a registrar.
Can I reply from my custom domain email address with forwarding?
Not directly. Forwarding only handles incoming mail. To send from hello@yourdomain.com, you need either a paid mailbox or a free transactional email service like Resend or Brevo configured with SPF and DKIM. You can then add that address to Gmail's "Send mail as" feature.
How long does email forwarding setup take?
About 15 minutes. The DNS changes propagate quickly, usually within a few minutes for MX records. Some registrars take up to 24 hours to activate forwarding on their end. Test with a real email before relying on it.
What happens if my registrar doesn't offer forwarding?
Move your DNS to Cloudflare. It's free, your domain stays registered where it is, and Cloudflare's Email Routing gives you unlimited forwarding aliases. You only need to change your nameservers to Cloudflare's.
Will forwarded email land in spam?
It can, especially without a proper SPF record. Add the TXT record your forwarding provider specifies. If mail still lands in spam, ask the sender to mark it as "not spam" in Gmail. That trains the filter over time.