MyRecon OSINTChoose an OSINT workflow by task and evidence
The useful comparison is the question a tool can answer, the evidence it returns and the work needed to verify that evidence. A tool directory or the largest site count cannot settle whether a workflow meets your task. Start with the detailed Sherlock comparison, then use the decision criteria below.
Compare MyRecon and BeenVerified: search inputs, public workflows, and verification limits. Choose an OSINT tool for authorized research. MyRecon vs DeHashed: compare breach and footprint workflows
Compare MyRecon and DeHashed: search inputs, breach workflows and verification limits. Choose an OSINT tool for authorized research. MyRecon vs Intelligence X: compare OSINT search workflows
Compare MyRecon and Intelligence X: search inputs, search archives and verification limits. Choose an OSINT tool for authorized research. MyRecon vs LeakCheck: compare credential and breach workflows
Compare MyRecon and LeakCheck: search inputs, credential exposure and verification limits. Choose an OSINT tool for authorized research. MyRecon vs Sherlock: Workflow, Cost & Limits
Compare Sherlock local CLI research with MyRecon browser access, current scan limits, paid features and public-source verification requirements.
Username discovery: browser or local command line
MyRecon offers a browser username workflow with free guest previews, five signed-in standard scans per day and an optional paid pack. Its standard catalogue has 500+ platforms; Extended is a separate paid scope. Sherlock, Maigret and WhatsMyName have official project repositories and different interfaces or data models. Review each project's current documentation before installation. Prefer a local tool when scripted integration and local output control matter; prefer browser access when installation is impractical. Both require opening original sources and interpreting unavailable checks.
Breach exposure is a different question
Have I Been Pwned documents searches against its breach dataset. A breach entry can indicate exposure in that dataset; it does not prove that an account remains active, identify every service using an address or establish that a current password is compromised. A public username sweep cannot substitute for breach review. Choose the input and result type you need first, then follow the data source's response guidance.
Specialist tools and data providers
Graph tools, business-data APIs and search aggregators can have different inputs, data rights and subscription terms. Do not assume that they provide the same service as a username checker. Check what a returned relationship actually means and whether the data is suitable for your authorized purpose. This page does not claim to have tested commercial providers or compare their current subscription prices. Use their official documentation and terms before purchasing or sharing personal identifiers.
A reproducible comparison sheet
Use an account or identifier you control. Record the version, date, input, scan scope, expected positive and negative controls, returned URLs, unavailable checks, and manually verified outcomes. Separate setup effort from request duration. A successful HTTP response is not proof of a profile, and a random-looking username is not a verified negative control. Keep results that cannot be checked in the denominator as unavailable rather than silently excluding them.
Worked decision and published limits
Illustrative task: find and close your own old accounts from two remembered usernames. A browser sweep plus saved signup emails can be enough; a graph platform may add setup without resolving ownership. A task requiring repeatable local exports may favor a CLI. The homepage includes a recorded MyRecon username case with captured evidence, but its small scope is not a general accuracy score and is not a same-scope benchmark of every tool named here.
Official instructions and sources
Updated October 3, 2026. Worked examples are illustrative; external account flows were not tested on personal accounts.
MyRecon Android is in closed testing for eligible testers. App availability and details.