Quick answer
How do I set up email forwarding on a domain?
Here is how to set up email forwarding on a domain at Shroudname: open the Forwarding tab, click Add an alias under Email forwarding, type the address (such as contact) and the mailbox to forward to, then click Save email forwarding. The destination confirms once by email. Up to 20 aliases are free, one of which can be a catch-all.
In brief
- What it does: mail sent to contact@yourdomain lands in a mailbox you already have; no new mailbox to manage.
- Confirmation: each destination gets a link and reads Waiting for confirmation until it is clicked.
- Limits: 20 aliases at most, one catch-all, and no destination on the same domain.
- Requirements: Shroudname's nameservers and no MX records already pointing elsewhere.
- Receive only: replying goes out from your personal mailbox; sending as the domain needs a mail provider.
What are the steps on the Forwarding tab?
Six steps, all free. The domain must use Shroudname's nameservers, or the tab says the settings work only there.
Open the Forwarding tab
In My domains, click Manage on the domain, then Forwarding. The second card is Email forwarding, which receives mail in an existing mailbox.
Click Add an alias
In Address, type the part before the @, such as contact, hello or a word only you know. Letters, digits, dots, hyphens, underscores and + are allowed.
Fill Forward to
Enter the mailbox that should receive the mail. It must be on another domain: forwarding to an address on this same domain is refused.
Optional: Add a catch-all
A catch-all, Every address, receives mail for any address of the domain that has no alias of its own. Only one is allowed.
Click Save email forwarding
Each new destination shows Waiting for confirmation, and a link goes to it.
Click the confirmation link
Open the message at the destination and follow the link. The alias turns Confirmed and mail starts flowing; send a test from another address.
Which way of receiving mail fits your domain?
Forwarding, a mail provider and an alias service solve different problems; the right one depends on whether you need to send as the domain.
| Option | Receives | Sends as the domain | Set up in |
|---|---|---|---|
| Shroudname email forwarding | Yes, to an existing mailbox | No | Forwarding tab, free |
| A private mail provider | Yes, in a new mailbox | Yes | DNS tab, MX and SPF records |
| An alias service with your domain | Yes, through aliases | Yes, by replying through the alias | The service's dashboard and DNS tab |
| No mail at all | No | No | No email template, null MX |
Why does forwarding need a confirmation and no MX records?
The confirmation proves the destination agreed to receive the mail, and the MX rule avoids two systems claiming the same domain's mail. Without the first, anyone could point a domain's mail at a stranger's inbox; without the second, part of the mail would go to the old server and part to the forwarder.
If the domain already has MX records, the tab shows Your domain already receives mail, with an Open DNS button. Remove those MX records in the DNS tab to use forwarding here, or use the mail provider's own forwarding instead.
The confirmation link is not the domain contact verification that ICANN requires; that one is described on verify the domain contact email. Both can point to the same mailbox, and the domain email can even be an alias of this domain's forwarding, as long as the alias keeps working.
Does email forwarding hide your real address?
It hides it from people who write to you, not from people you answer: a reply leaves from the personal mailbox, with its own address in the From line. That is the main limit to know before you set up email forwarding on a domain.
Two ways around it:
- A private mail provider on the domain, so replies leave as you@yourdomain; see how to set up a private email on your own domain.
- An alias service that relays replies through the alias, explained in how to use an email alias for domain registration.
Forwarded mail can also fail SPF checks at the destination, since the forwarding server is not listed in the sender's SPF record. RFC 7208 describes the problem; DKIM signatures usually survive forwarding, which is why most providers still accept the message.
Which domain is best for email forwarding in 2026?
A short name on a common extension is best, because people type it right the first time; .com, .me and .email all read naturally in an address. The Private mail domain set groups .com, .me and .email for $60.47 a year.
According to Shroudname's survey of 12 November 2026, a .email domain renews for $29.49 at Shroudname against $37.40 on average at Namecheap, Dynadot, GoDaddy, Cloudflare and Njalla, and the price stays the same every year. Forwarding itself costs nothing on any extension, so how to set up email forwarding on a domain is the same few clicks whatever the name ends in. The account behind the domain needs no email at all, as domain registration without email explains.
Frequently asked questions
How many forwarding addresses can I create?
Up to 20 per domain, and one of them can be a catch-all. Each destination confirms once.
Can I forward to a Gmail or Proton address?
Yes, to any working mailbox on another domain. Forwarding to an address on the same domain is refused.
Why do I see Waiting for confirmation?
The destination has not clicked the link yet. Mail is forwarded only once it is confirmed; check the spam folder of the destination.
Does forwarding work with Cloudflare or custom nameservers?
No. Email and web forwarding at Shroudname need its own nameservers; elsewhere, set up forwarding at the DNS provider.
Is a catch-all a good idea?
It catches any address, typos included, but also spam sent to random names. A few named aliases are usually the better choice.
Verdict
- Add an alias, save, confirm: three clicks and one link give a domain address that lands in a mailbox you already use.
- Need to send as the domain? Pair the domain with a mail provider or an alias service instead of plain forwarding.
Sources (2)
- RFC 7208: Sender Policy Framework (SPF), section on forwarding — IETF (read 2026-11-16)
- RFC 5321: Simple Mail Transfer Protocol — IETF (read 2026-11-16)
Forward your domain's mail
Up to 20 aliases and a catch-all, free on every domain using Shroudname's nameservers.