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
- ...
-
T
commented
I definitely posted in support of this before, but now that I have services hosted under my own domain this is more needed than ever for me.
-
Anonymous
commented
Thank you very much for implementing this feature.
It was critical from a security perspective, and it finally makes Proton Pass a useful password manager.
There is one more thing missing to make it convenient to use: I would like to be able to set the default behavior for new entries (for example, to the exact domain), so that I don't have to modify it manually every time I create a new entry.
Thank you!
-
s.c.
commented
I agree with Tundor below. I’ve been waiting for this feature to become available for nearly a year now. It’s been teased for weeks. The iOS release notes listed support for URL matching. Finally it was enabled and I’m very disappointed that the feature is basically non-existent on iOS and iPadOS. I understand that this is a limitation of Apple’s AutoFill APIs. Maybe Proton can extend the Safari extension to iOS so that the extension can be used instead of AutoFill API to workaround these limitations. It’s really needed especially as so many smaller websites are using Shopify and they all have the some root domain of shopify.com.
-
Tundor
commented
Since today it seems to be available and I appreciate it very much, thank you!
However I want to raise one problem on iOS:
It is stated, that as per iOS API the exact host matching is not working and hence deactivated. While this is true for the keyboard integration, when you click on the "key" icon to open the selection from proton pass this could very well be implemented. Bitwarden and 1password have exactly this behaviour, once you see the login details in the app, it is correctly filtered. Please consider improving this as well, as it has been shipped today on iOS it is not useful. -
IetIesAai
commented
According to their latest announcement this should be available now, together with folders, but haven't yet found how to use it....
-
Matttiiisss commented
come on guys... it's so late and i need this for my business
-
Jason
commented
This has been cooking since 2024?! Lets get this going!
-
Bernhard
commented
This is a blocking issue for me. I've up to 45 password entries for a single base domain. Without support to change domain matching from base domain to host and preferably also other models supported e.g. by Bitwarden, my migration is blocked.
-
Kai Fett commented
I was really hoping after the announcement in June that there will be some improvement.
Currently Proton Pass is of very limited use for me, as I have multiple accounts on different applications in the same domain and always have to manually search for the right entry.
-
dnbt
commented
Just moved from Bitwarden and like many I like to self-host so separating hosts/subdomains from domains is essential. Quite disappointing this isn't already implemented, but optimistic given the roadmap (https://proton.me/blog/pass-roadmap-spring-summer-2026) that we'll see it soon!
-
David
commented
Came from Bitwarden, and it's confusing this is not a feature. This was raised three years ago as of this comment.
-
Marco
commented
This is an important feature indeed. Please implement it
-
Proton User Voice
commented
Pretty wild that such an essential feature hasn't been implemented yet.
-
Marc H
commented
I just moved over to proton pass from Bitwarden and just noticed this feature wasn't a thing.. crazy.. WE NEED IT!
-
Jake
commented
I self-host as much as I can; considering many of us use Proton for the privacy benefits, I'm assuming many others self-host many of their services. I've got many subdomains — having them mapped correctly is critical.
-
Jack
commented
I’m paying for Proton Pass and need this for self-hosted services. I run multiple apps under different subdomains like ser1.example.com and ser2.example.com, each with separate credentials. Proton Pass currently treats them as the same site and suggests unrelated logins. Please add hostname/exact URL matching rules so credentials can be limited to a specific subdomain.
-
Jack
commented
would be possible to have it implemented? i do self hosting and it is annoying to see a huge list of passwords that are not even for it.
it is already one of the top 10 upvoted and nothing was done about it.
it makes me wonder if i should move back to bitwarden that has this available even on free plan. -
Datatan
commented
This is absolutely essential. I'm glad to see this mentioned in the Summer roadmap for 2026. I hope it gets delivered.
-
Anonymous
commented
Good day everyone. Just wanted to update this thread with something I just read. According to the Proton Pass spring and summer 2026 roadmap (https://proton.me/blog/pass-roadmap-spring-summer-2026), it appears that this feature is coming.
If reading this correctly it will be called URL matching and this is what was written in that post:
"URL matching will allow you to configure autofill exactly the way you want, allowing Proton Pass to suggest information for the exact website you’re visiting, a highly requested update."
-
Tundor
commented
Shouldn't this be flagged as planned? It was mentioned on the Roadmap for Summer 26, or did I completely get that wrong?