In addition to these I also find, personally, that having multiple different accounts on the same domain is pretty common. If you go to the subdomain/FQDN level

In addition to these I also find, personally, that having multiple different accounts on the same domain is pretty common. If you go to the subdomain/FQDN level, it might be less common, but then you have the problems that (a) companies change their login subdomain even more often and (b) With a vault, I can choose whether I want the URL to be matched to the base domain/public suffix, to the host/subdomain, to the whole path, etc., for each entry. And in fact I do have pretty much every option my manager (Bitwarden) offers in use (except maybe "regular expression"). Without a vault, you have to remember which option you chose, which means you effectively have to use the same method for every site (or at least for most sites, whatever you don't log in to often enough to remember). It also causes problems for those companies which have "SSO" by using the same credentials across multiple different subsidiaries/affiliates on different domains - I'm thinking here about United Healthcare, who have sign-in at `healthsafe-id.com` for insurance, and at `healthsafeid.optumbank.com` for FSA, using the same set of credentials (and yes, obviously this is a terrible practice on their part, but you often don't have any real choice about using companies with these terrible practices). And it also makes any integration/automation (i.e. at its most basic "press a hotkey to inject password keystrokes for the current selection") need, as you mention, a list of exceptions/mappings (or else to not work for any sites like these).