Every year, data breaches expose billions of passwords. When a service you use is breached, the passwords from that breach are collected, traded, and tried against other services, in an attack called credential stuffing. A password that has appeared in a breach is therefore dangerous even if it looks strong, because attackers already know it and will try it everywhere. The Password Breach Checker tells you whether a password has appeared in known data breaches, by checking it against the Have I Been Pwned database of breached passwords, without ever sending the password, or even its full hash, to anyone. Only the first five characters of the password SHA-1 hash leave your browser, a privacy design called k-anonymity, and the comparison happens locally. If the password is found, the tool tells you how many times it has appeared and urges you to change it everywhere. If it is not found, the tool explains honestly that absence from the database does not guarantee the password is strong or safe.
What Is the Password Breach Checker?
The Password Breach Checker is a free browser-based tool that checks a password against a database of passwords exposed in known data breaches, operated by the Have I Been Pwned service. The database contains passwords that have appeared in breaches, stored as hashes, and the service offers a privacy-preserving lookup API that this tool uses. The lookup works as follows. Your browser hashes the password with SHA-1, producing a 40-character hexadecimal hash. It takes only the first five characters of that hash, called the prefix, and sends just the prefix to the Have I Been Pwned range API. The service returns all hash suffixes that share that prefix, typically several hundred entries, each with a count of how many times that password has appeared in breaches. Your browser then compares the remaining 35 characters of your hash, the suffix, with the returned list, locally, and reports whether a match was found and, if so, the count.
The privacy property is the point of the design. The service receives only five characters of the hash, which match hundreds of different passwords, so it cannot determine which password you checked. Your password itself never leaves the browser, and even the full hash never leaves the browser. The comparison, the counting, and the verdict all happen on your device. The tool states this in its hint, so you can verify the claim against the behavior: only a short prefix is sent, over HTTPS, to the Have I Been Pwned API endpoint for the range lookup.
The result has two forms. If the password is found, the tool shows a heading stating that it was found in data breaches, and a message giving the number of times it has appeared, formatted with thousands separators, and advising you not to use it, to change it everywhere you have used it, and to use a unique password for each account. If the password is not found, the tool shows a heading stating that it was not found in known breaches, and a message explaining that this means only that it has not appeared in the breaches this service knows about, not that it is strong or safe. If the service returns an error or the network fails, the tool shows an error explaining that the check could not be completed and suggesting you check your internet connection and try again.
How to Use the Password Breach Checker
- Enter the password. Type or paste the password you want to check into the Password field. The field masks the input, and a note in the tool explains the privacy design. Only the first five characters of the hash will be sent to the lookup service.
- Show the password if needed. Tick Show password to reveal the characters while you type, so you can confirm the password is exactly the one you intend to check. Keep the screen private while the password is visible.
- Click Check for Breaches. Press the button. It changes to a Checking message and is disabled while the lookup runs, and the result area shows that the check is in progress. The lookup needs an internet connection, because it queries the Have I Been Pwned service.
- Read the result. If the password was found, note the count: a password that has appeared millions of times is among the first tried in every attack. If it was not found, note the qualification: not found means not in this database, not that the password is strong.
- Act on a found result immediately. Change the password everywhere you have used it, starting with the most important accounts, and replace each one with a different generated password. Do not reuse the breached password with a small change, such as adding a digit, because attackers try common variations too.
- Follow up with strength and uniqueness checks. A password that is not found may still be weak. Check its strength with the Password Strength Checker, and make sure it is unique to one account, regardless of the breach result.
Key Features of the Password Breach Checker
- Privacy-preserving k-anonymity lookup. Only the first five characters of the SHA-1 hash are sent to the service. The password and the full hash never leave your browser, and the service cannot identify which password was checked from the prefix alone.
- Local comparison. The list of matching hash suffixes is returned to your browser, and the comparison with your full hash happens locally, so the service never learns whether a match was found.
- Appearance count. When a password is found, the tool reports how many times it has appeared in known breaches, giving a sense of how widely exposed it is.
- Clear action guidance. A found result advises changing the password everywhere and using unique passwords. A not-found result explains its own limits, so it is not misread as a safety guarantee.
- Live breach database. The check queries the Have I Been Pwned Pwned Passwords service, which is updated as new breaches are added, so results reflect the current state of the database rather than a fixed local list.
- Honest error handling. Service errors and network failures produce a clear message with the status or a suggestion to check the connection, rather than a misleading clean result.
- Button state feedback. The check button is disabled and relabeled while the lookup runs, preventing duplicate requests and making the progress visible.
Practical Use Cases With Concrete Examples
Checking a password before reusing it. You are about to use a familiar password for a new account. Check it first. If it has appeared in breaches thousands of times, choose a different password. The check takes seconds and prevents you from adopting a password attackers already know.
Auditing passwords after a breach announcement. A service announces a breach. Check the password you used for that service, and check any other password you suspect you reused. Change every password that is found, and change the breached service password even if it is not found, because the breach may not yet be reflected in the database.
Reviewing old passwords during a cleanup. Work through your password manager entries, checking the oldest or most reused passwords. Each found result is a priority for replacement. The count helps you prioritize: a password found millions of times should be replaced before one found a handful of times, though both should go.
Testing a new password idea. Before adopting a password you invented, check whether it has appeared in breaches. A clever-seeming password may already be in the database because someone else thought of it, or because it is a common phrase, name, or pattern. A not-found result is necessary but not sufficient; also check its strength.
Teaching credential stuffing. A trainer can demonstrate the checker with a well-known weak password, showing a large appearance count, to make the scale of breach exposure concrete. The demonstration explains why unique passwords matter: a breached password is tried against many services automatically, not just the service that was breached.
Verifying a generated password is not a known value. Generated passwords are random and should not appear in the database. Checking one and seeing a not-found result confirms, as expected, that the random value is not a previously breached password, while remembering that the real protection comes from randomness and uniqueness.
Tips and Best Practices
- Change a found password everywhere. A breach at one service exposes the password for all services where it was reused. Change it on every account, starting with email, banking, and password manager accounts, and use a different password for each.
- Use a password manager. Unique passwords for every account are only practical with a manager. Generate replacements with the Password Generator and store them in the manager.
- Enable two-factor authentication. A second factor protects an account even if its password is breached and tried elsewhere. Use an authenticator app or the OTP Code Generator to understand time-based codes.
- Do not make small changes to a breached password. Adding a digit, changing a letter, or appending a symbol creates a variant that attackers also try. Replace the password with a fully new random password.
- Recheck periodically. New breaches are added to the database over time. A password that is not found today may be found after a future breach, especially if you continue to use it on many services. Periodic checks catch that change.
- Check before adopting, not only after a breach. Make the breach check part of creating any new password, alongside the strength check. Prevention is easier than cleaning up after reuse of an exposed password.
- Understand what not found means. It means the password has not appeared in the breaches this service knows about. It does not mean the password is strong, unique, or safe from guessing. Always pair the breach check with a strength check.
Limitations
The Password Breach Checker has limits that are stated in its results and must be respected. A not-found result does not guarantee a password is strong or safe; it means only that the password has not appeared in the breaches known to Have I Been Pwned. Breaches that have not been reported, breaches not yet added to the database, and breaches held privately by attackers will not be reflected. The check covers passwords only, not email addresses, usernames, or other personal data, and it does not tell you which breach exposed a password or which accounts are affected. The lookup requires an internet connection and the availability of the Have I Been Pwned service; if the service is unreachable, the check cannot complete, and the tool reports an error rather than a result. The hash used for the lookup is SHA-1, because that is the format the Pwned Passwords API uses, and the privacy protection comes from sending only the prefix, not from the strength of SHA-1. The tool does not store results, does not monitor passwords over time, and does not change passwords for you. Finally, the tool cannot protect against a password that is guessed, phished, or observed, even if it has never appeared in a breach.
Frequently Asked Questions
Is my password sent to Have I Been Pwned?
No. Your browser hashes the password with SHA-1 and sends only the first five characters of the hash. The service returns all suffixes sharing that prefix, and the comparison happens in your browser. Neither the password nor the full hash leaves your device.
What does it mean if my password was found?
It means the password has appeared in known data breaches, and the tool shows how many times. Attackers have access to breach lists and will try the password against many services. Change it everywhere you used it, and replace it with a unique generated password for each account.
What does it mean if my password was not found?
It means the password was not found in the Have I Been Pwned database of breached passwords. That does not guarantee it is strong or safe. It may still be weak, guessable, or exposed in a breach the service does not know about. Check its strength as well.
Can the service tell which password I checked?
No, from the prefix alone. The five-character prefix matches hundreds of different passwords, so the service cannot determine which one you checked. The full hash and the comparison result stay in your browser.
Why does the check need the internet?
Because it queries the live Have I Been Pwned database, which is too large to include in a web page and is updated as new breaches are added. Without a connection, the tool cannot complete the lookup and reports an error.
Should I check every password I use?
Yes, over time, starting with reused passwords and passwords for important accounts. Prioritize found results for immediate replacement, and use a password manager to make unique replacements practical.
Related Tools
Related tools include the Password Generator for replacement passwords, the Password Strength Checker for strength ratings, the Password Entropy Calculator for brute-force estimates, the OTP Code Generator for second-factor codes, and the PIN Code Generator for numeric codes. Return to the homepage to browse all free tools.