Check If Your Password Was Leaked — Without Sending It Anywhere
Have I Been Pwned's Pwned Passwords tool checks your password against real breach data using a privacy trick: only the first five characters of a hash leave your device.
When a website gets breached, attackers often walk away with its user database, including password hashes. Those hashes get traded, dumped publicly, and eventually collected into giant breach compilations. A password that has appeared in a breach is a password an attacker can try first, no matter how complex it looks. The good news is that you can check whether your password is in those compilations — without ever sending the password itself to anyone.
What Have I Been Pwned is
Have I Been Pwned is a free breach-lookup service run by security researcher Troy Hunt. It collects data from breached websites, loads the email addresses into a searchable index, and lets anyone check their own address for free. As of mid-November 2026, its home page listed just over 1,050 breached websites and about 17.9 billion breached accounts. It has two separate tools: one checks whether an email address appears in breach data, and the other — Pwned Passwords — checks whether a specific password has ever appeared in a breach. The second tool is the one this guide is about.
It is important to understand what a result means. A hit does not mean someone is logged into your account right now. It means your exact password is sitting in a public breach list, so anyone holding a hashed password database can crack yours instantly — no guessing required, because the answer is already known. A clean result does not mean the password is strong, only that it has not been seen in the breaches this service has loaded. Breaches whose data was never published will not appear.
How the check stays private: k-anonymity
Sending your password to a website to ask whether it leaked would be a terrible idea. Pwned Passwords does not do that. It uses a technique called k-anonymity, documented in the service's own API reference. Here is exactly what happens:
1. Your device hashes the password. Your browser turns the password into a SHA-1 hash — a 40-character string of hexadecimal characters that cannot be turned back into the password. For example, the word "password" hashes to a value starting with 5BAA6.
2. Only the first five characters leave your device. Your browser sends just that five-character prefix to the service. The other 35 characters stay on your machine, and the password itself never leaves it.
3. The service returns every matching hash ending. The server replies with the remaining characters of every breached hash sharing that prefix — typically hundreds of candidates, each with a count of how often it was seen.
4. Your device checks for a match. The comparison happens locally, in your browser. The service cannot tell which candidate was yours, because it only ever saw five characters — one of about a million possible prefixes.
Two honest caveats. First, k-anonymity hides your password among many candidates; it does not make the request invisible — the service sees your IP address and the prefix. Second, the email-address search works differently: you do type your address in, and the site says searches are not logged and no passwords are stored next to emails — though, as its own FAQ admits, you cannot prove a website is not logging you.
How to run the check, step by step
1. Type the address yourself. Type haveibeenpwned.com into the address bar yourself. Do not open it from search ads or from links in email or social media. Any site that calls itself a breach checker but asks for a full password or a card number is not this service.
2. Check your email first. Enter the email address on the home page and read the result. A green result means no breach found in the data loaded so far. A red result lists the breaches the address appeared in, with dates and what was exposed.
3. Check the password itself. Go to the Pwned Passwords page and type the password into the checker. It uses the same k-anonymity method: the password is hashed in your browser and only the five-character prefix is sent. Read the count: a password seen millions of times is a password to retire immediately.
4. Act on a hit. Change the password everywhere you used it, starting with email and banking, and turn on two-factor authentication. A leaked password is not a judgment on your memory — it is a signal to replace it with a long, random, unique one from a password manager.
Built-in checks you may already have
You do not have to visit a website at all. Google Account has a password checkup built in, Apple's iCloud Keychain flags compromised passwords, and Mozilla Monitor pulls from public breach data — all without asking you to type a full password or card number. These are good routine monitors. The direct check at Have I Been Pwned is worth running whenever you hear about a major breach, or once a year as a habit. Either way, the rule is the same: if a password has been seen in a breach, replace it, and do not reuse the replacement anywhere else.