We need this. So much. Event just a few hundreds or at the bare minimum 50 aliases. And not under a shared limit with normal email addresses.

Currently, I see an option to create multiple aliases across different domains, but all aliases must point to the same inbox and a single email. This creates a limitation if I want finer control over how aliases from different domains are routed especially that you multiple domains from alias management.

Feature Request:

Add support for multiple bindings between aliases and inboxes, so that:
• Aliases created under different domains can be directed to different inboxes.
• Admins can define domain-specific routing rules (e.g., *@domain1.com *@domain2.com → inbox A, *@domain3.com → inbox B).

This would allow greater flexibility, improved organization, and brand/domain separation without requiring multiple instances or complex workarounds.

I created a new request here: https://protonmail.uservoice.com/forums/284483-proton-mail-calendar/suggestions/50418576-improved-alias-email-forwarding-for-multiple-domai

3 years to change a single limit!
Instead implementing AI slop into the ecosystem. Good job Proton.

Give us unlimited custom domain email addresses, or a separate higher limit for them. I don’t think the current limit is fair.

Like: https://tuta.com/blog/release-notes-unlimited-aliases

for context, i'm on Proton Unlimited. that said, i feel the limit makes sense to be applied ONLY to proton's domains, but for custom domains, it just doesn't make sense. it's our domain that we pay for separately, and on the paid plan it simply makes sense to at least have the domain emails not be part of that limit! and with other services, we can do infinite forwarding and "reply as" functionality, like i had setup in gmail before switching

for people like me that use it for organization of emails (recipient filtering) and use separate emails for different aliases i've set up, and similar uses, the limit of 15 that we have now is unacceptable. i'd even be fine if they lowered it to 10 for proton domains only as they need to make sure there's enough for everyone, but emails at your own domain should be excluded from that, instead of 15 across the board. it simply doesn't make sense if you want to send emails from this many aliases like i and many others do, for a number of privacy-related and personal reasons

that said, simplelogin can technically do forwarding from unlimited aliases, but it's only receiving, and sending is through tedious reverse aliases, that's just messy and tedious. let us do it in the protonmail inbox directly and with the ability to select it in the drop down of the email compose window, with all the PGP goodness protonmail offers, right there. now, the free aliases with proton pass work great, but for some things i'd rather use my own domain.

the current "solution" of simplelogin is a low quality and janky one to say the least. please remove custom domain emails from counting towards the limit, and for UI purposes, let us hide certain addresses from the drop down in the compose window, and add a manual typing mode, where you can type in the beginning of an email and it'll filter by that, including hidden aliases.

As more online services begin detecting and blocking email addresses associated with forwarding or masking services (e.g., those using generic alias domains like passmail), it would be highly beneficial if Proton Mail allowed users to create aliases that end with their own custom domain—for example, amazon0110@mydomain.com.

This feature would help maintain the privacy and organizational benefits of aliases while significantly improving compatibility with services that currently flag or block addresses from known alias providers. While this isn't a widespread issue yet, early signs—such as registration restrictions from services like Cursor—indicate this will likely become a more prominent barrier in the near future. Supporting custom domain aliases would future-proof Proton Mail’s alias system and give users greater flexibility and control over their digital identity.

It is already possible and include in proton pass paid user with SimpleLogin

I signed up for protonmail ultimate hoping to use the unlimited hide-my-email aliases, but was disappointed after attaching my custom domain that I couldn't then use it in the alias generator (either the one build into proton mail, or the proton pass one which are the same). I might be able to inconveniently add a subdomain to simplelogin, but it would be really inconveniant compared to the protonmail/protonpass integration.

+1
I don't see a compelling reason to use ProtonMail until this is implemented.

+1
I think the "unlimited" plan should have "unlimited" aliases. I don't like subaddresssing with +, because some sites don't handle them well, and it's easily detectable.
Ideally, I'd use one alias for each site I register to (banks, school, gaming accounts, etc).

I have a custom domain for ProtonMail and would like to use it to create my aliases in Proton Pass.
I do not want to configure another service (SimpleLogin) for this purpose !

You need to add your domain to SimpleLogin, since ProtonMail itself doesn't provide alias functionality.
Then you can use the domain is PP too.

With the growing popularity of Proton Pass and Hide Me, more systems will detect and block hide-me domains. To bypass this, offer the option to create an alias using my own domain.

It's one of the two showstoppers that prevent me from switching from Google Workspaces to Proton. My family is taking full advantage of multiple aliases for segregation of concerns (school, finance, etc) and I see no reason why they should be limited on a high tier account.

Another +3. One of the biggest features I am missing after moving from Fastmail. I don't see from a technical standpoint why removing this limit shouldn't be possible.

+3. Limiting and paying for aliases on Proton domains makes perfect sense. It makes absolutely no sense to have the same limits imposed on our own domains which we control. The storage space is paid for and shared between the mail boxes, it's not like they each have a separate allocation.

Please lift this arbitrary limitation.

It would be great if we could create email aliases using our custom domain directly through ProtonPass. I know this can be done via SimpleLogin, but thinking about a family plan where a spouse or children would use the service, it's complicated to deal with privacy education by asking them to use one portal to create emails and another to create and manage passwords and logins. Even for personal use, it's much simpler and faster to create aliases through ProtonPass directly via the app or extension.

Along with this, it would also be great if each family member could create their own aliases on their accounts using the custom domain of the family owner and each receive their emails related to their created aliases.

It would be great if we could create email aliases using our custom domain directly through ProtonPass. I know this can be done via SimpleLogin, but thinking about a family plan where a spouse or children would use the service, it's complicated to deal with privacy education by asking them to use one portal to create emails and another to create and manage passwords and logins. Even for personal use, it's much simpler and faster to create aliases through ProtonPass directly via the app or extension.

Along with this, it would also be great if each family member could create their own aliases on their accounts using the custom domain of the family owner and each receive their emails related to their created aliases.

Same request for me.

Today, I subscribed to ProtonMail. Immediately after subscribing, I realized that the limit of only 10 aliases for my custom domain is insufficient for my needs. I am not a fan of the catch-all feature, as it results in receiving emails like '{random}@mydomain.com.' Instead, I prefer to disable the catch-all feature and create a separate alias for each specific use case, ensuring that I do not receive spam under my domain.

While I am aware that SimpleLogin can fulfill this requirement, the challenge lies in configuring my domain on two systems simultaneously.

I kindly request ProtonMail to consider providing unlimited aliases for custom domains.