Is my password out there?
20 minEasyAssume at least one of your passwords is in a breach dump — for most people with an email address older than a few years, it is. The useful question isn't whether, it's which, and what it still unlocks.
Check, in this order
- Every email address you own at haveibeenpwned.com. Old addresses too — they're often the recovery address on an account you forgot about.
- Your password manager's breach report. Bitwarden, 1Password, Chrome, Safari, and Firefox all have one built in. This is better than any external check, because it compares your actual passwords against known leaks.
- Reused passwords. Same tool, different report. Reuse is what turns one breach into ten compromised accounts.
- Your own name and handles in a search engine, in quotes. Try your username, phone number, and email — usernames are the strongest link between accounts you think are separate.
- Your phone number. If it's tied to your email and public somewhere, you're exposed to SIM-swap attacks against SMS 2FA.
Fix in this order
- Email first. It resets everything else. New unique password, then 2FA.
- Your password manager's master password. Long passphrase, never reused, never typed into anything else.
- Banking and payments. Then add 2FA.
- Anything sharing the breached password. Your manager will list them.
- Move 2FA off SMS for anything that matters. App or hardware key.
- Delete accounts you don't use. An unused account is a breach waiting to happen, and it still holds your data.
Keeping private information from resurfacing
- Use email aliases for new signups. When one leaks you know exactly who leaked it, and you can kill the alias without changing your real address.
- Stop answering security questions honestly. Store random strings in your manager instead — a real answer is researchable.
- Never paste secrets into search boxes, notes apps, or a chatbot. Anything that syncs is a copy you no longer control.
- Check what you publish. Screenshots leak email addresses, photos of a badge leak an employer, and a window in the background leaks a location.
- Scrub your public repositories. If you write code, an API key committed once stays in the git history even after you delete the line.
- Set a yearly reminder to repeat the checks above. New breaches land constantly.
Be careful which checkers you use. Never type a live password into a website to "test" it. Legitimate checks either use your password manager locally, or — as Have I Been Pwned does — check a partial hash so the full secret never leaves your device. Any site asking for the plain password is either careless or hostile.
Next
Cleaning up your trail
Shrinking what's already out there about you.
1 hourModerate