Problem
When visiting a website like subdomain2.example.com, the password manager extension currently shows all credentials matching the base domain example.com, including unrelated subdomains. This creates clutter and forces the user to search manually each time.
Example saved credentials:
example.comsubdomain.example.comsubdomain2.example.com
When accessing subdomain2.example.com, the list should prioritize credentials in the following order:
subdomain2.example.com— exact matchexample.com— parent domain- Other subdomains like
subdomain.example.com
Current Behavior
- All matches for
example.comand its subdomains are shown together. - Users must scroll or start typing the subdomain name to find the correct entry.
I’ve reviewed the Preferred entries feature in Kee 3.6+, but it doesn’t address the issue of prioritizing logins by subdomain — relevant credentials can still appear below less specific matches.
Expected Behavior
- Automatically prioritize credentials by domain specificity:
Exact match with current subdomain
Base domain (e.g. example.com)
Other sibling subdomains
Why this matters
- Greatly improves usability when working with multiple subdomains.
- Enables quick mouse-based selection instead of needing to type to filter every time.
- Reduces the chance of choosing the wrong credentials.
- Matches user expectations in modern, multi-subdomain setups.
Optional Enhancements
- Group suggestions visually (e.g. section headers or icons for “Exact match”, “Base domain”, etc.)
- Allow toggling this prioritization in settings (for advanced users)
Improving the matching logic to prefer exact subdomain entries will enhance UX, reduce errors, and make credential selection faster and more intuitive.