How Breach and Password Exposure Checks Work
Understand breach lookups, password hash prefixes, provider limitations, and appropriate next steps after a match.
Email and password checks are different
An email breach lookup asks a data provider whether an address appears in known incidents. A password exposure check can use a hash prefix so the plain password is not sent to the provider. A match means the value appears in a known dataset; it does not prove which person used it or that every related account is currently compromised.
Respond to a meaningful match
- Change the affected password anywhere it was reused.
- Use a unique generated password for each account.
- Enable multi-factor authentication.
- Review account sessions, recovery methods, forwarding rules, and recent security events.
- Be alert for targeted phishing that uses exposed profile details.
Privacy and provider limits
The password tool should never need your original password on the server when it implements prefix-based checking. Email lookups necessarily submit the requested address to KitBeam's backend and configured breach provider. Provider coverage is incomplete, and absence from results is not proof that credentials are private.
Avoid unsafe reactions
Do not contact people named in a dataset, attempt to access accounts, or download illicit breach collections. Use reputable notification services, preserve evidence where appropriate, and follow your organization's incident-response process.