Email aliases on a domain you own
Point a domain at YeyMail and every address on it becomes an alias: shop@you.com, bank@you.com, whatever you invent at the checkout. Unlimited, because the namespace is yours, and portable, because the domain is yours too.
Why your own domain beats a shared one
Aliases on @yeymail.com work in about a minute and cost you nothing to set up. They are a perfectly good place to start. But a shared domain has four limits that your own domain does not, and three of them only show up later.
- Some sites refuse them. Fraud filters keep lists of alias and disposable domains and reject signups from any of them. An ordinary domain you own is not on those lists. This is the single most common reason people move.
- The good names are taken. A shared namespace is contested, so you end up with a random tail on the readable ones.
- There is a ceiling. On the shared domain you get 500 addresses on Starter and 5,000 on Plus, and the count includes addresses you have deleted, because the claim on an address is permanent.
- They are not portable. Leave and the addresses go with the provider. On your own domain you repoint the DNS and keep every one of them, which is worth thinking about before dozens of accounts use them for password resets.
Unlimited, and why the word is safe here
On a domain you own, aliases are unlimited. Not capped high, not fair-use, unlimited: there is no per-domain allowance, because a namespace you own is not shared with anyone and there is nothing to ration.
That is deliberately not the claim we make about the shared domain, where the ceiling is real and the count includes deletions. Elsewhere on this site the word is qualified for that reason. Here it is not, and the difference is the point of the page.
The one bound that still applies is a creation rate, which exists to stop a script rather than a person: 300 new aliases a day on Starter and 600 on Plus. Nobody making addresses by hand reaches it.
Setting it up: MX, SPF, DKIM, DMARC
Four records, all of which the dashboard prints with the exact values for your domain. You paste them into your registrar or DNS host and YeyMail re-checks until they go live, then emails you when the domain is ready.
- MX sends mail for the domain to us. This is the one that makes aliases work at all.
- SPF tells receiving servers that we are allowed to send on the domain, so replies and alias-sent mail are not treated as forgeries.
- DKIM signs outgoing mail cryptographically. Without it, mail sent as your alias lands in spam far more often.
- DMARC is optional and worth adding. It tells receivers what to do with mail that fails the first two, and it is what stops somebody else spoofing your domain.
There are step-by-step walkthroughs for the common hosts, including Cloudflare and Namecheap, in the setup documentation. If the domain already receives mail somewhere else, changing the MX record moves all of it, so read that section first.
Catch-all, without the usual spam problem
With catch-all on, every address on your domain works whether you created it or not. You can invent one at a checkout or read one out on the phone and it simply arrives. The classic objection is that a catch-all is a spam magnet, because dictionary attacks try thousands of names against a domain that accepts all of them.
Forward and block rules are the answer: you decide which patterns reach you and which are refused at the door, so the convenience survives without the flood. Catch-all is a Plus feature, and it is not included in the trial.
What happens if you stop paying
This is the question worth asking any alias provider before you depend on one, so here is ours plainly. If a subscription ends, custom domains pause. Aliases on them stop forwarding and you cannot create new ones.
Aliases on the shared @yeymail.com domain keep forwarding at 20 messages a day, with no end date, and the kill switch keeps working on everything. Anonymous replies stop entirely.
The reason a custom domain is still the safer choice is that the domain and its DNS never stopped being yours. Point the MX record at another provider and every address you built continues to exist. That is not true of an address on somebody else’s shared domain, which is exactly why the ownership matters.
Limits by plan
- Trial: 1 custom domain. Free for 7 days, no card, on the Starter feature set with lighter limits.
- Starter, $0.99 a month: 5 custom domains, unlimited aliases on each.
- Plus, $4.99 a month: Unlimited custom domains, unlimited aliases on each, plus catch-all with rules and inbound webhooks.
Common questions
Yes. You point a few DNS records at YeyMail and every address on that domain becomes an alias you control, forwarding to the inbox you already read. Aliases on a domain you own are unlimited, because the namespace is yours rather than shared with other customers.
An MX record so mail is delivered to us, an SPF record so receivers know we may send on the domain, and a DKIM record so outgoing mail is signed. A DMARC record is optional but recommended. The dashboard shows the exact values for your domain and re-checks them automatically until they are live.
Generally no, and this is the main practical reason to use one. Some sites block the well-known alias and disposable domains by name. An address on an ordinary domain you own does not appear on those lists, so it behaves like any other mailbox.
The domain pauses: aliases on it stop forwarding and you cannot create new ones. Aliases on the shared yeymail.com domain keep forwarding at a reduced rate, and the kill switch keeps working on everything. Because the domain and its DNS remain yours, you can point it at another provider and keep every address.
One during the trial, five on Starter, and unlimited on Plus. The number of aliases on each of those domains is unlimited on every plan.
New to the idea? What an email alias is covers the mechanism, and how to stop spam emails covers why one address per site is the structural fix.