Domain URL matching rules
Proton pass should have URL matching rules like bitwarden. This makes it easier to handle different usecases.
For instance, at work I have different usernames/passwords on different subdomains and I would like to be able to limit certain credentials to specific subdomains and have others shared accross multiple subdomains.
So that would be great to have a diffrent matching rules like:
- root domain
- hostname
- starts with
- regex
- exact match
- ...
-
Adel Alzubeir commented
I regret the move from Dashlane to Proton. This one is extremely annoying
-
Anonymous
commented
This is actually a blocker for me to move from Bitwarden to ProtonPass
-
Pham
commented
Comment for Proton Pass Feedback Thread (“Domain URL Matching Rules”)
As an active Proton ecosystem user running a self-hosted domain (e.g. example.net), I can confirm that the current substring-based URL matching in Proton Pass severely limits usability for anyone who uses their own domain for both email and internal services.
Example:
All of my logins use @example.net as the username, and I host services like
nextcloud.example.net, grafana.example.net, and truenas.example.net.
When I visit any of those sites, Proton Pass lists every vault item containing “example.net” anywhere in the record — dozens of unrelated logins — instead of only the one matching subdomain. This makes the extension nearly unusable for homelab or enterprise setups.What’s needed:
Proton Pass should implement configurable domain-matching rules, just like Bitwarden and 1Password:Exact host match (grafana.example.net)
Base domain match (*.example.net)
Starts-with / wildcard (service*.example.net)
Regex (for advanced users)
Multiple URLs per credential
This would allow Proton Pass to support professional and self-hosted use cases while maintaining strict security boundaries between services. It’s also essential for organizations that share a common apex domain across many logins.
Until Proton supports per-entry match modes, anyone with a homelab or corporate domain faces an autofill list so long it borders on unusable.
“Let all things be done decently and in order.” — 1 Corinthians 14:40, KJV
Precise domain matching is the digital equivalent of order. Please prioritize this improvement soon.— A long-time Proton user and self-hoster
-
Noon
commented
Baffled this isn't already a feature. I'm finding posts about this (and CS responses) from over 2 years ago.
-
Renaud Dufour commented
I come from keepass and this is a must have. Without more flexible matching rules I see too many accounts for a given domain and picking the correct one is a pain.
-
Hakim Bawa commented
Same as Justin below, I also have a home lab and tons of services, each with different logins. Having a way to match urls would be really useful
-
cpsibo
commented
Adding my vote. This is a really important feature for professionals and home labbers. Without a "starts with" or similar rule, you can have dozens of accounts show up for everything under a domain.
-
Bede
commented
Any update on this? It was marked as under review over a year ago and there hasn't been an update since then.
This is a critical feature for me and I can't switch to Proton Pass until it is implemented.
-
Justin Packwood
commented
I really do love proton pass and migrated from dashlane (initially caused by pricing but I was already using proton mail so it only made sense). However the lack of this feature is really becoming a pain. I do a lot with my homelab and I use a specific domain for tons of internal services, and not being able to properly handle all of these logins for all of the subdomains is becoming a huge issue.
-
[Deleted User]
commented
This is a must have - considering going back to bitwarden. But otherwise Protonpass is excellent!
-
rada
commented
still nothig?? is really pretty annoying
-
Evan
commented
Why has this not been implemented yet? Over 1400 votes
-
xesy83eo
commented
I still cannot leave bitwarden until this is implemented.
-
Alex
commented
I have similar issue with third level domains. For me I need only option for exact match for domain additional to current behaviour.
-
Joachim D commented
Agreed - this is critical for homelab users. Won't somebody think of the nerds!?
I love the product - plz plz add this feature, guys 🙏🙏🙏
-
Rune Nielsen
commented
Any updates on this? I have a lot of services running on subdomains and it makes Proton Pass useless for signing in to these when there's 30+ entries in the dropdown
-
Cornald
commented
It's annyoing and insecure to use the clipboard to enter credentials.
I'm on my way to leave Bitwarden but this one makes ist really hard. -
Rock
commented
Still no movement on this? This is pretty wild. I want so bad to leave Bitwarden for Proton Pass, but every time I try, I realize that it's simply impossible to manage my logins without having fine grain control over domain matching.
-
Benjamin commented
Similar features were requested and acknowledged by Protonpass support team TWO YEARS AGO (Source: https://www.reddit.com/r/ProtonPass/comments/14mhv21/comment/jqlz94k/?)
It still has not been implemented. This should be a fairly simple thing to modify or add; I don;t understand why it's been years and we are still waiting for ONE of these services to offer this.
-
erphise
commented
I am leaving 1Password the minute this comes out.