How long would it take to crack your password?
For a password of 12 random characters using all four character types, the honest average answer is about 34 thousand years against someone who already has your stolen password hash and is throwing real hardware at it. Make it 20 characters and that number jumps to roughly 123 quintillion years. Here is exactly where those numbers come from.
Oddlyplay's password generator prints a bits of entropy figure next to every password it makes, and that number is not a vibe, it is a real calculation. Entropy is just length times how much each character or word is worth, measured in bits, and every bit you add doubles the work an attacker has to do. That is why going from 12 characters to 20 does not make a password a bit stronger, it makes it roughly 123 quintillion years stronger.
Where the number actually comes from
Switch on uppercase, lowercase, digits and symbols and you get a pool of 88 possible characters for every position. The amount of information one character carries is log base 2 of that pool size, about 6.46 bits, so a 20 character password is 20 times that, roughly 129 bits. A passphrase works the same way with words instead of characters: a list of 1,024 words carries exactly 10 bits per word, so five words is 50 bits.
What do these numbers mean in actual time
The generator assumes an attacker already has your stolen password hash and is running 100 billion guesses a second, roughly what a rack of current graphics cards can do against a fast hash like SHA256. The time shown is the average case, half the total keyspace, since on average you get found halfway through the list rather than at the very end. A few real examples straight off the tool:
- 8 lowercase letters only: about 37.6 bits, average crack time around a second.
- 12 characters using all four types: about 77.5 bits, around 34 thousand years.
- 5 words from the 1,024 word passphrase list: 50 bits, around an hour and a half.
- 6 words from the same list: 60 bits, around 67 days.
- 8 words from the same list: 80 bits, around 192 thousand years.
- 20 characters using all four types: about 129.2 bits, around 123 quintillion years.
Does the hash the site uses actually matter
Enormously. The 100 billion guesses a second assumption is for a fast hash. A site using a slow, deliberately expensive hash like bcrypt or Argon2 can push that crack time out by a factor of thousands, because each single guess costs the attacker far more computing time. On the other end, a site that stores your password as plain text makes every number on this page meaningless, because there is nothing left to crack, your password is just sitting there in a database. You cannot tell which kind of site you are dealing with from the outside, which is exactly why making your own password strong is still worth doing regardless.
How many bits is actually enough
Roughly 75 bits and up is comfortable for a normal account on a site that hashes passwords properly. Past 100 bits your password stops being the weak point in your setup at all, and the real risk shifts to phishing, reusing the same password on two sites, or malware already sitting on your own device. Going from 128 bits to 256 buys you nothing you could ever actually use, since the smaller number was already far beyond any realistic attack.
Does adding one exclamation mark on the end really help
Barely. Swapping a letter for a lookalike number or sticking a symbol on the end feels clever, but attackers run exactly those substitutions as a standard rule set on top of a dictionary, so the real gain is tiny. What actually moves the number is length, and after that, drawing every character from the full available pool rather than a predictable corner of it. That is the whole reason this tool leads with bits and a crack time instead of a vague colored strength bar.
Should I change my password every few months just in case
No, and this is not just an opinion, both NIST and the UK's National Cyber Security Centre now advise against forced rotation. People asked to change a password on a schedule tend to pick a weaker one with a counter stuck on the end, which is worse than leaving a genuinely strong one alone. Change a password when you actually have a reason: a breach notice, a login you shared with someone, a device you lost. Otherwise make it long once, keep it in a password manager, and add a second factor where you can, since that stops the attacks that actually happen to ordinary people far more often than brute force guessing ever does.