Password strength checker: how long to crack?
Type a password to see its strength score, how long it would take to crack in different kinds of attack, and specific tips to make it stronger.
Your password never leaves this page. It is checked by JavaScript in your browser and is not sent, logged or stored by EpiFive.
Guides that use this tool
- Entra Password Protection for On-Premises AD: Deploy Agents Step by Step
Block weak and organization-specific passwords on Active Directory domain controllers with the Entra Password…
- Plan a Microsoft 365 MFA rollout with Conditional Access and Authenticator
A phased plan to require MFA for every Microsoft 365 user: pick security defaults or Conditional Access, set…
How to use it
- Type or paste a password. Tap Show if you want to see what you typed.
- Read the score from 0 (very weak) to 4 (very strong) and any warning about why it is guessable.
- Check the crack times. The slow-hash row is the realistic one for a stolen database from a well-run site; the fast-hash row is the worst case.
- Follow the suggestions, or make a random one with the password generator.
What makes a password strong
- Length first: 14 or more characters, or a passphrase of four or more random words.
- No personal details: names, birthdays, phone numbers, vehicle numbers or your city.
- No reuse: one leaked site should never unlock another.
- Turn on two-factor authentication for anything important.
Related tools
- Password generator: Strong random passwords and passphrases made with your browser’s crypto API. Nothing leaves your device.
- Hash generator: MD5, SHA-1, SHA-256 and SHA-512 hashes of text or files, and checksum verification.
- Photo location (EXIF) remover: See the GPS location and camera details hidden in a photo, then save a clean copy without them.
- JWT decoder: Decode a JSON Web Token’s header and payload and read its expiry times. Decode only, no verification.
Related guides
Questions people ask
Is it safe to type my real password here?
The check runs entirely in your browser with the open-source zxcvbn-ts library. The password is not sent, logged or stored anywhere, and the page works even if you go offline after it loads. Still, the safest habit is to test a password that is similar to yours rather than the exact one.
How is the crack time estimated?
zxcvbn looks for patterns attackers try first: common passwords, dictionary words, names, dates, years, keyboard rows like qwerty, repeats and sequences, including l33t substitutions such as @ for a. It estimates how many guesses an attacker would need, then converts that into time for four attack speeds, from a rate-limited login page to a stolen database with a fast hash.
Why is “P@ssw0rd123!” rated weak when it has every character type?
Because it is a common word with predictable substitutions and a number and symbol tacked on the end. Attackers’ tools try exactly these patterns first. Length and unpredictability matter far more than symbols: four random words beat a short complex password.
What score should I aim for?
Aim for 4 (very strong) on email, banking, UPI and work accounts, and use a different password for each one. A password manager makes that practical. Turn on two-factor authentication too: it protects you even if a password leaks.
Does a strong score mean my password has not been leaked?
No. This checker estimates guessability; it does not look your password up in breach lists. If a password was ever used on a site that was breached, change it everywhere you used it, however strong it looks.