Password Crack Time Calculator
“Time to crack” depends on two numbers: how many guesses the attacker needs, and how many they can make per second. This calculator estimates the first with the same pattern-aware method as the strength checker and lets you set the second.
The five scenarios in the table:
- Online, throttled: guessing through a login form that rate-limits, about 100 per second.
- Online, no throttling: a poorly protected API, 10,000 per second.
- Offline, bcrypt: a stolen database hashed with bcrypt cost 12, around 10,000 per second even on GPUs.
- Offline, SHA-256: 10 billion per second on an 8-GPU rig.
- Offline, MD5 or NTLM: 100 billion per second, the speed Windows password hashes fall at.
The hardware selector multiplies the offline rates: a single laptop GPU is about a tenth of a rig, a rented cloud cluster a hundred times more, a nation state ten thousand times. Times are for searching half the space, which is the expected effort.
What leaves your browser
The password is analysed in your browser only. Nothing is transmitted or stored.
Why is the MD5 time so much shorter than the bcrypt time?
MD5 was designed to be fast; bcrypt was designed to be slow and tunable. Against the same password, a bcrypt-protected database takes ten million times longer to crack.
My password says "centuries" but the strength checker says "weak". Which is right?
They should agree; both use the same estimator. If they differ, check the hardware setting on this page, which scales offline times.
Do attackers really have 8-GPU rigs?
Yes, and they rent bigger ones by the hour. Assume the SHA-256 or MD5 scenario when a site has been breached and you do not know how they hashed passwords.
What time is "safe"?
Anything beyond a few years against the fast-hash scenario is safe from realistic attackers. Beyond a few decades and you can stop worrying about the password itself.