The short version: forwarding receives, it does not send
Namecheap's Free Email Forwarding is a relay. Mail sent to [email protected] arrives at Namecheap's forwarding servers and is passed on to an inbox you already own. Namecheap says you cannot create full mailboxes or send outgoing mail from a forwarding address, and points people who need that to its paid Private Email service. [1]
That makes forwarding a good fit for a domain that mostly receives: a contact address on a landing page, a newsletter's reply-to inbox, or a side project you check once a week. It is a poor fit for a business that sends quotes, invoices or support replies all day, because every reply needs a workaround that the forwarding service does not provide.
What Namecheap's free forwarding includes
The limits below come from Namecheap's two setup articles. None of them are hard to live with for a one-person business, but the MX conflict matters if you already run any mail service on the domain. [1] [2]
| Item | What Namecheap documents | What it means for you |
|---|---|---|
| DNS required | BasicDNS, PremiumDNS or FreeDNS [1] | The domain must use Namecheap's nameservers; on third-party DNS you would set up mail elsewhere |
| Forwarders | Up to 100 forwarding addresses [1] | Plenty for role addresses such as hello@, billing@ and press@ |
| Catch-all | One catch-all, forwarding to one address only [2] | Every unknown address lands in a single inbox |
| MX records | Set automatically when you choose Email Forwarding in Mail Settings [1] | Any existing MX records for another mail service stop applying |
| SPF record | Shown in Advanced DNS and required for forwarding; do not delete it [1] | Leave it in place when you tidy DNS |
| Other mail services | Cannot run alongside Private Email or any other email service [1] | It is forwarding or a mailbox provider, not both |
| Setup time | Allow about an hour for a new forwarder to be ready [1] | Test after an hour, not after a minute |
| Sending | Not supported; no outgoing mail from the forwarding address [1] | Replies need a separate SMTP server |
Setup: the MX switch, forwarders and catch-all
Order matters. Switch the domain's mail settings first, then add addresses. Namecheap's catch-all article says your MX records must already point to free forwarding before you can add a catch-all. [1] [2]
- Sign in, open Domain List and click Manage next to the domain. [1]
- On the Advanced DNS tab, find Mail Settings and choose Email Forwarding. Namecheap sets the MX records automatically when you save all changes. [1]
- On the Domain tab, scroll to Redirect Email and click Add Forwarder. Enter the alias (the part before the @) and the full address to forward to, then save. [1]
- For a catch-all, click Add catch all in the same Redirect Email section and enter one destination address. [2]
- Wait about an hour, then send a test from an account other than the destination inbox. Namecheap says tests sent from the forward-to address itself will most likely fail. [1] [2]
- Leave the SPF record that Namecheap shows in place; its article says forwarding needs it. [1]
Replying as [email protected]: why you need a separate SMTP server
Forwarding gets mail in. Getting a reply out with your domain in the From line requires a server that will accept and send mail for that address. Gmail's 'Send mail as' feature lets you add another address and choose it on the From line. For work, school or domain addresses, Gmail asks for an SMTP server, a username and a password, and lists SSL on port 465 or TLS on port 587 as common combinations. [3]
Namecheap's forwarding service does not provide an SMTP server, so the login has to come from somewhere else. Gmail's help page gives smtp.gmail.com as an example server. Using your own Google account there generally means an app password, and Google says app passwords work only on accounts with 2-Step Verification turned on. They are not offered when 2-Step Verification uses only security keys, on work or school accounts, or with Advanced Protection. [3] [5]
The bigger issue is timing. Google's notice says that starting January 2027, Gmail will remove 'Send as' for third-party email addresses, together with POP fetching and Gmailify, and that Google Workspace aliases are not affected. Google says Gmail may restrict new configurations during the Q3 to Q4 2026 transition. The notice does not specifically address a custom domain address sent through an outside SMTP server. Treat any Gmail 'Send as' setup you build now as temporary until your own Gmail settings show otherwise. [3] [4]
Google's own suggested alternatives are to use the provider's website or app, a desktop mail client with IMAP and SMTP, the Gmail mobile apps, or Google Workspace for a custom domain. [4] In practice, people who need to reply as the domain every week usually end up paying for a mailbox.
Catch-all: when it helps and when it hurts
Namecheap describes the catch-all as receiving mail sent to any address on the domain that is not set up as a mailbox or alias, such as a misspelled address. [2] That is useful in the first months of a new domain, when you have printed an address on a flyer or told people a slightly different one on a call.
The cost is that a catch-all also accepts mail sent to addresses you never created, including addresses spammers guess. Since a catch-all can point to only one address, all of that lands in one inbox. [2] A sensible pattern is to switch the catch-all on for a few weeks, see which addresses people actually write to, create named forwarders for those, and then remove the catch-all.
When to upgrade from forwarding to a real mailbox
Use this as a decision table. If two or more rows land in the right-hand column, forwarding has stopped saving you money and started costing you time.
- Namecheap's own next step is its Private Email service, which its forwarding article recommends for a full account that can send. Check current pricing on Namecheap's site before you buy. [1]
- Google points custom-domain users to Google Workspace. [4]
- If you only need occasional sending, compare a free mailbox plan first; our Zoho Mail guide covers the limits to check.
| Your situation | Free forwarding is enough | Pay for a mailbox |
|---|---|---|
| How often you reply from the domain | Rarely; replying from a personal address is acceptable | Daily or for clients, invoices or support |
| Who reads the mail | One person | Several people need their own logins or shared folders |
| Where you read mail | One Gmail inbox | Several devices, or a desktop client with IMAP |
| Reliance on Gmail 'Send as' | None | You depend on it after January 2027 [4] |
| Other mail services on the domain | None | You want a provider's mailboxes, which cannot share the domain with forwarding [1] |
Pre-launch checklist
- Mail Settings set to Email Forwarding and saved; no MX records left over from an old provider. [1]
- Forwarders created for every address printed on your site, invoices and social profiles.
- Catch-all on only if you have a reason, with a date to review it. [2]
- Test messages sent from a different account an hour after setup. [1]
- A written plan for replies: a mailbox provider, or an SMTP login you know will keep working after Gmail's January 2027 change. [4]
Questions before you decide
How many forwarding addresses does Namecheap allow?
Namecheap's forwarding article says you can create up to 100 forwarding addresses on BasicDNS, PremiumDNS and FreeDNS. A catch-all is separate and can forward to only one address.
Can I send email from a Namecheap forwarding address?
No. Namecheap says the service is forwarding only: you cannot create full mailboxes or send outgoing mail from the forwarding address. It points to its Private Email service for a full account.
Can I use free forwarding and Private Email on the same domain?
No. Namecheap says Free Email Forwarding cannot be used with Private Email or any other email service at the same time, because each needs the domain's MX records.
Will Gmail's 'Send mail as' keep working with my domain address?
Google says that from January 2027 Gmail will remove 'Send as' for third-party email addresses, along with POP fetching and Gmailify, and that Google Workspace aliases are not affected. Its notice does not single out custom domain addresses sent through an outside SMTP server, so check your Gmail settings before relying on one.
Why did my test email not arrive?
Namecheap warns that a test sent from the same address you forward to will most likely fail. Send the test from a different account, and allow about an hour after creating a forwarder before testing.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Namecheap Knowledgebase: How to set up Free Email Forwarding Accessed 30 Oct 2026
- Namecheap Knowledgebase: How to set up a catch-all (wildcard) email address Accessed 30 Oct 2026
- Gmail Help: Send emails from a different address or alias Accessed 30 Oct 2026
- Gmail Help: Learn about changes to third-party email account support in Gmail Accessed 30 Oct 2026
- Google Account Help: Sign in with app passwords Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.