I don't like password managers that are software installed on one machine. I don't use one machine. I use many machines, over different OS's, and in many different locations. Laptop A, desktop B, phone C, Work A, Work B, House A, House B, Friend C, Client D, etc. And can you imagine the grief if your password file got lost or corrupted?
Why do people keep recommending password managers that are local, and are not cloud based? It makes no sense unless you are chained to your mum's basement.
But as soon as you go cloud based, you open yourself up a whole new set of risk vectors.
This is what I do, and I share it with all, to criticise or to gain. Each to their own. And it is the password I use for this site, and for all others. (Public websites with logins, online shops etc).
DNS.1A$.fixedsecretpassword.#hash#
example
techpowerup.com@1A$.12345.XX
The @1A$ deals with those horrible password complexity requirements you get on some sites, ie, "you MUST have a number, you MUST have upper case, you MUST have a non-letter-number character", the fixedsecretpassword is a password that is common to 99.9% of the sites where I am registered, and the #hash# is a two letter cipher at the end that is based on some easy algorithm that is uniquely mine and I can work out in half a second when drunk, and based off the DNS.
I do not use 2FA on ANYTHING other than banking sites. The fewer times you use 2FA the less likely you are to be compromised or spoofed.
These passwords are unique to each and every website, and will not be machine hacked in any plausible form. And if any one were, the risk of quickly finding the others is remotely small. It would need human intervention to spot the readable pattern. So that is the risk, a nefarious person who got a copy of a password from one site, getting the gist of the password structure, and
wanting to spend their time hacking others trial and error on the .xx hash. But they'd never reach a banking site, and any shopping site requires 2FA after CC entry. Don't let websites store your CC!
I could upgrade and make it human unreadable, converting the DNS to a cipher. e.g.
http://practicalcryptography.com/ciphers/simple-substitution-cipher/. This would immediately stop any pattern spotting by human intervention.
E.g. but infinite others
But I can't be bothered...