How to Check If Your Password Has Been Leaked (Safely)

How k-anonymity lets you check a password against billions of breached records without ever revealing it — plus what to do in the first hour if yours shows up.

The quick answer

Use a breach lookup that works on k-anonymity — for example the Pwned Passwords range API model — where only a 5-character hash prefix ever leaves your device. Never type a real password into a random "check my password" website: the checker itself may be the thief. If a password appears in any breach corpus, retire it everywhere immediately.

How k-anonymity keeps your password private

  1. Your device hashes the password (SHA-1) locally. The password itself never travels.
  2. Only the first 5 hash characters are sent to the lookup service — a prefix shared by hundreds of unrelated hashes.
  3. The service returns every hash suffix in that range, and your device compares locally. The operator learns nothing about which password you checked, let alone the password.

The same principle powers reputable third-party services such as Have I Been Pwned's Pwned Passwords and the built-in leak warnings in password managers and browsers.

The golden rule of password checking

A leak checker can only be trusted if (a) it never receives your password or even its full hash — only a prefix — and (b) you have reason to trust the operator. When in doubt, don't type real credentials anywhere. Practice on the fully local checker, where verification is one developer-tools network tab away.

If your password shows up: the first hour

  1. Change it on the breached service immediately — from the real site, not an email link.
  2. Change every account that reused it. This is the step people skip and the one attackers bank on.
  3. Sign out other sessions where the service offers it; revoke unknown app connections.
  4. Expect phishing. Breach news always brings follow-up scam waves referencing the incident.

The full ordered playbook: What to Do After a Data Breach.

Try the mechanics locally

Our Breach Check page demonstrates the entire model in your browser: SHA-1 hashing, prefix extraction, and prefix matching against a tiny built-in demo corpus. It is transparently labeled a demo — a real deployment would point the same architecture at a licensed range API. That's how this pattern should work everywhere.

Frequently asked questions

Is it safe to type my password into a breach checker?

Only if it uses k-anonymity (your password or full hash never leaves your device) and you trust the operator — otherwise no. A fully local analyzer (like OMP's) that makes no network calls is the safest form.

What does it mean if my password is in a breach corpus?

That exact string is in cracking dictionaries used by bots worldwide — even if it wasn't leaked from your account. Common words and patterns appear there regardless. Treat it as burned: never use it again, anywhere.

If my password is NOT found, am I safe?

No — "not found" only means absent from that corpus. New breaches surface constantly, and targeted guessing doesn't need lists. Strong + unique + 2FA is the durable defense.

How do hackers actually get password lists?

From breached service databases (especially those stored with fast or unsalted hashes), credential-stealing malware, and phishing. Lists are then merged into "combo lists" traded in criminal ecosystems.

How often should I check for leaks?

Don't schedule it — automate it. Password managers and modern browsers monitor continuously and alert you. Manual spot-checks are reassuring; continuous monitoring is protection.


Hands-On Security Practice

Apply what you learned with our zero-telemetry tools and references:

Put it into practice: run your next password through the local checker — it never leaves your browser.

Keep reading

Related guides