This is extremely important to me and I believe every single Password Manager no matter what should have this critical and crucial feature; it's something that if any password manager lacks makes the password manager feel a lot less efficient to use so I would definitely love for this feature to be added as I used it all the time in the past with my former Password Manager.

This would be extremely useful. For example I would love to separate by port.

I second @Todd R's comment from August 28, 2023.

Would like to have all of the items below as options:
- "full URL" to match the whole host address, port and full path
- "exact host" to avoid matching any subdomains
- "exact port" to avoid matching services on the same host which use different ports
- "exact path" to ensure matching a for login page, and not a user management page

Subscribed to pass plus only to find out this essential feature is missing. Going to cancel my sub. I will resubscribe once this feature is added.

This feature is essential, proton pass is useless for my home network without this.

This functionality should be at the core of the application. As others have pointed out, if you use this for work then it's often the case that internal domains are the same but individual systems are called with fqdn. server-a.domain.com or server-b.domain.com etc

I’m considering to abandon my Proton Pass subscription and go back to my previous Password Manager due to the lack of this feature.

I'll use proton pass when this feature will be available. For now, proton pass is unusable for me

Just another human chiming in that Proton Pass isn't valid or usable for me without, at the very least, subdomain/host-based differentiation for logins.

Yes that's essential to me as well

This is absolutely critical if you host multiple services with different authentication on multiple subdomains, like I do. I don't quite get why this isn't already implemented.

I still want get prompted to autofill the main login page, to NS1 for example, but NOT have a proton icon on every field on subsequent pages because then I am creating DNS records and never want that saved and the fill box is small enough without a icon in it I have to work around. I disabled for this site now, so my work is much less impacted but I lost my autofill on parent login page. Specifically, keep autofill on https://my.nsone.net/#/login but disable on https://my.nsone.net/#/connect/dashboard or anything else https://my.nsone.net/#/* thats not "login". So either allow exact only match, just not domain, or allow regex I can exit to exclude as my regex skills permit.

Adding a regex option for matching could solve it for all.

This is a must have feature. Hoping this can happen ASAP.

This really is a crucial feature. Just allowing us to match by hostname (e.g. I want to match against "foo.bar.com", not "*.bar.com") would solve 99% of usecases.

This isn't just a self-hosted thing (though I use it for that as well) - there are many services that have a "companyprefix.appname.com" format, where you very often have many accounts for. This includes ubiquitous things like Slack, or anything logging in via Auth0.

This feature would be very much appreciated. I set up Proton Pass but realized this did not work. It is too crucial of a feature.

This is what's keeping me from switching from Bitwarden right now. Crucial for self-hosting when you have several logins at the same domain but at different ports.

If you self-host some stuff this is crucial!

Please! I have many services run locally at my home on different ports

I have different services on their own subdomains and each have their own logins. But when I try to login to sub1.domain.com it suggests logins for sub2.domain.com, sub3.domain.com, and sub4.domain.com. But the browser plugin only shows two suggested logins and how often do you think it’s the right one?