How to Check If a Password Has Already Leaked Before You Reuse It
Check whether a password has appeared in a known data breach before you reuse it, using a check that never sees the password itself.
You already know the feeling. You are signing up for one more account, the password field is staring at you, and the easiest thing in the world is to type the password you already use everywhere else. But a password does not have to be guessed to hurt you. It only has to have leaked once, somewhere else, and then every site where you reused it is open to anyone holding that list.
That is what this post is for: a two-minute check you can run before you reuse a password, or before you keep using one you have had for years.
Why reuse is the part that hurts you
When a website gets breached, the passwords it stored usually end up in lists that get traded and sold. Attackers then take those lists and try each email and password pair on other sites, one after another, automatically. The technique is called credential stuffing, and it works because so many of us reuse the same password in several places. The attacker does not need to crack anything. They just need you to have used the same password on the breached site and on your email, your bank, or your work account.
Have I Been Pwned, the free breach lookup run by security researcher Troy Hunt, puts it plainly: password reuse is extremely common, and when credentials are exposed in a breach, attackers use the known combinations to get into your other accounts. Even small changes between sites do not save you. Attackers predict common patterns, so password1 on one site and password2 on another is barely better than using the same one twice.
The check that never sees your password
Typing your password into a random website to ask "is this safe?" sounds like a terrible idea, and on most sites it is. The one check worth using is built so your password never leaves your own device. It is called Pwned Passwords, and it is free.
Here is what happens when you run it. Your browser turns the password into a SHA-1 hash and sends only the first five characters of that hash to the service. The service sends back every hash ending it knows that starts with those five characters, and your browser looks for your full hash in that list on your own device. The full password, and even the full hash, never leaves your machine.
Take the most famous example: the SHA-1 hash of the word password starts with 5BAA6. Ask the service about that prefix and it returns close to two thousand matching endings, and your browser finds yours among them. The count next to it is the number of times that exact password has been seen in breach data: more than 52 million times. One password, seen 52 million times, because millions of people picked the same obvious word.
The technique is called k-anonymity, and the idea is simple: the service only learns that you asked about one of roughly two thousand hashes, not which one. NIST, the US National Institute of Standards and Technology, specifically recommends checking passwords against breached datasets, and this is the check they have in mind.
How to run the check in under a minute
Start with the password you reuse most. That is the one that matters, not a password you made up for a forum in 2019 and never used again.
- Open haveibeenpwned.com/Passwords in your browser. Type the address yourself rather than clicking a link in an email, so you know you are on the real site.
- Type the password into the box and run the check.
- Read the result. There are only two outcomes, and both are blunt.
While you are there, check your email address in the main Have I Been Pwned search too. It tells you which breaches your address appeared in, which is the other half of the picture.
What the answer actually means
If the result says the password has been seen before, stop using it. The site's own wording is that it has previously appeared in a data breach and should never be used, and if you have ever used it anywhere before, change it immediately. That applies even if the count is small. A password seen once is a password in an attacker's dictionary.
If the result says no pwnage found, that is good news with a limit. It means the password was not found in the breaches loaded into the service. It does not mean the password is strong. A short, predictable password that nobody has leaked yet is still a short, predictable password. The check answers one question, "has this leaked?", not "is this good?"
One more limit: breach data takes time to reach the service, so a password leaked last week might not show up yet. If a service you use announces a breach, check again.
The mistake I see most often
The mistake is not skipping the check. It is running the check on the wrong kind of site. Plenty of lookalike pages offer to test your password, and many of them send the whole password to their own server, where it is stored, logged, or sold. Only ever type a password into the site it belongs to, or into a checker that hashes it in your browser first. If a password checker cannot explain, in plain words on its own page, that only a hash prefix leaves your device, close the tab.
The second mistake is checking once and calling the job done. Passwords leak over time, not all at once. The password that was clean when you set it in 2023 may have leaked in a breach since. Recheck your most reused passwords every few months. It catches the one that went bad while you were not looking.
What to do first
Pick the password you reuse most and check it now, before your next sign-up. If it comes back clean, keep it, but only on one account. If it has been seen, replace it everywhere you used it, starting with your email, because your email is the key to resetting everything else. Generate the replacement with our Password Generator, 16 characters or more, and store it in a password manager instead of your memory. Then check the new password too. A fresh random password should come back with no pwnage found, and that is the result you want to see before you trust it. My earlier post on fixing your password habits covers the rules that actually work in 2026.
A new post lands here every day. If there is a topic you want covered, email ask@websmartstudios.com.