Security guide

How to Check If a Password Was Leaked

Learn safe ways to respond to possible password leaks without pasting real passwords into untrusted websites.

Summary

If you suspect a password was leaked, the safest response is often to replace it rather than paste it into unknown websites. A leak check can be useful only when the service has a trustworthy privacy design and you understand what is being sent.

Use the password strength checker for local pattern analysis, but do not treat it as a breach database.

What to do first

Change the password from a trusted device. If the same password was reused, change every affected account. Start with email, banking, work, cloud storage, and password-manager recovery accounts.

Review account state

Revoke active sessions, check recovery email and phone settings, review forwarding rules, remove suspicious app access, and enable MFA or passkeys.

Detailed guidance

This guide focuses on checking whether a password may have appeared in breaches without exposing it carelessly. It is written for users who heard about a breach and want to respond safely, so the practical goal is not to create a dramatic security claim. The goal is to choose a password habit that can survive everyday use: sign-in forms, password managers, mobile keyboards, account recovery, shared devices, and the occasional service with strange validation rules. A secure recommendation is only useful if a real person can follow it consistently.

The safest starting point is randomness plus uniqueness. Randomness means the value is selected from a large space by a cryptographically suitable random source, not invented from a birthday, a pet name, a keyboard pattern, or a favorite quote. Uniqueness means the same password is not used anywhere else. A password that is long but reused can fail quickly after one unrelated breach, while a unique random password limits the damage to the single account where it was used.

For this topic, a practical preset is local pattern analysis first, then trusted breach-alert services when needed. You can apply that preset with the password strength checker and then store the final value in a trusted password manager. PwdGen generates values locally in the browser with Web Crypto; the generated password is not sent to a PwdGen server. That local design reduces server-side exposure, but it does not protect against every threat. A malicious browser extension, a compromised device, a phishing page, or unsafe clipboard handling can still expose a secret after it is generated.

The most common problems to avoid are typing real passwords into unknown websites, searching exact passwords in logs, and assuming no result means no risk. These problems matter because attackers rarely need to brute-force every possible password when human habits give them a shortcut. Credential stuffing, phishing, leaked password lists, and account-recovery abuse are often more realistic than a pure mathematical search. That is why the best advice combines password quality with account-level controls such as MFA, passkeys, recovery-code storage, and regular review of recovery email or phone settings.

Use this checklist when applying the recommendation:

• Change reused passwords after a breach.
• Start with email and high-value accounts.
• Use trusted breach notification tools only.
• Never paste a sensitive password into random pages.

If a website rejects the ideal setting, do not force the password into a weaker pattern by hand. Adjust one variable at a time. If symbols are rejected, keep uppercase, lowercase, and numbers enabled and increase length. If a maximum length is low, use the largest accepted length and make sure the value is unique. If a password must be read aloud, printed, or typed on a television or router screen, consider excluding confusing characters and increasing the length to compensate for the smaller alphabet.

Finally, remember the boundary of password advice. A strong password is one layer of defense, not a guarantee. It cannot make a phishing page safe, fix malware, or compensate for a service that stores credentials poorly. The useful habit is boring but durable: generate a unique value, store it safely, protect the recovery path, and replace it quickly if you suspect exposure.

A safe next step

After reading this guide, do one small account audit instead of trying to fix everything at once. Pick the account that would cause the most trouble if it were taken over, confirm that its password is unique, and check the recovery email, recovery phone, MFA method, and backup-code storage. If any part of that chain is weak, improve that part before moving to lower-risk accounts. This order keeps the work manageable and protects the accounts that attackers are most likely to use as a stepping stone. For how to check if a password was leaked, the best outcome is a repeatable habit: generate locally, store carefully, and avoid reuse.

Frequently asked questions

Should I paste my password into random leak-check sites?

No. Only use trusted breach-check services with clear privacy design, or change the password instead of testing it.

What should I do after a leak?

Change the affected password, change reused passwords, revoke sessions, review recovery settings, and enable MFA.

Can PwdGen check breach databases?

No. PwdGen provides local strength and crack-time estimates, not a remote breached-password lookup.