Dehashed

Dehashed is a breach and leaked-credential search corpus. Inside UserSearch it is available as a Module (an integrated data source), letting you check whether an identifier appears in known public data breaches without leaving your search workflow.

What it is

Dehashed maintains a large index of records exposed in public data breaches and leaks. Given an identifier such as an email address, it can indicate which breaches that identifier appears in and surface the associated leaked data held in the corpus.

Official site: dehashed.com

What data it returns

When you run a search that uses the Dehashed Module, results are drawn from its breach corpus and can include:

• Which known breaches or leaked datasets an identifier appears in
• Associated leaked-credential and profile fields recorded in those datasets

Draft — awaiting confirmation

The precise fields Dehashed returns through UserSearch, its breach coverage and freshness, and whether leaked passwords or sensitive credentials are redacted (returned masked rather than in full) are not yet confirmed. Do not rely on specific coverage figures until verified. What is confirmed is that UserSearch integrates Dehashed and exposes it under the search types listed below.

Where it is used in UserSearch

Dehashed powers the following search types:

• Public Leaks — as an available Module for breach and leaked-credential lookups.
• Email — surfaced through the AI-Agent (including the Email OneScan bundle, the Module that runs several data sources at once).

How to access it in UserSearch

1. Choose the Public Leaks or Email search type.
2. Enter the identifier you want to check (for example, an email address).
3. Under the available Modules / data sources, ensure Dehashed is selected. In the Email AI-Agent flow it appears as one of the selectable Module tiles and may be included in the Email OneScan bundle.
4. Run the search and review the Dehashed results alongside the other selected Modules.

Reliability

Draft — reliability note

Breach-corpus data sources reflect datasets that have been collected and indexed over time; results depend on which leaks have been ingested and how recently. Treat breach findings from this Module as indicative, and corroborate with other Modules before drawing conclusions. Freshness, coverage, and redaction behaviour await confirmation.

Verified against UserSearch v2.0.20