Run Sherlock on your computer

Check the sites you choose and save a spreadsheet-friendly report of matches and failed checks.

Find where a username is used

Look for your old accounts or check where a username appears publicly. Supply one or more usernames and choose the sites to check. The report keeps the profile links, each site’s response and any checks that could not complete.

A matching username does not establish who owns an account. Sherlock can produce false matches when sites change their pages or block automated requests; use the links to check the result.

You bring

a folder containing search.json with usernames and sites arrays, optional timeout (1–60 seconds) and nsfw (false by default); optionally add sites.json with custom Sherlock definitionssearch

You get

one row per username and site, including profile URL, reported result and HTTP statusaccounts.csv
the complete structured report, including unavailable checksaccounts.json

Licences & source

Sherlock MIT. UGT's batch driver and checks are Apache-2.0.

Setup & verification

Sherlock at commit c588d7c8b476

Run on clean x86-64 (Intel/AMD) and ARM64 machines on 10 Nov 2026. Its check passed on a known sample and rejected deliberately broken results.

This checks the job this page describes, not every feature of the original project.

Known issues

Use this for public profiles you have a reason to check. Results do not identify a person or prove account ownership.
403, 429, server errors and failed connections are marked unavailable, not absent. A run where no site can give a usable response fails.
Sites change their detection rules. A pinned site definition can become stale even when installation still works. Custom definitions let your agent configure a site without changing the runtime.

Recipe details