floatboat
Open navigation menu

Sherlock

Sherlock checks usernames across supported sites. A terminal-enabled agent can run a scoped search, save candidate links, and prepare a table for the account owner to review.

Check an authorized username across selected sites

Give the agent an exact username and a short list of approved sites. Have it record public candidate URLs and leave ownership decisions for review.

Provide a handle you manage or have permission to check, the site list, and an output folder.

Copy the request into a new Floatboat conversation and provide the required material.

Download Floatboat

Your request for Floatboat

Preview and copy the request. It is not sent automatically from this page.

Reference: Sherlock
https://github.com/sherlock-project/sherlock

Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding.

My task:
Check whether Sherlock is installed. Prepare a search for my approved username on the sites I list, then show me the planned command before making network requests. After I approve the command, run it, save candidate URLs in the approved folder, and flag each row for manual verification.

Expected deliverable:
A candidate URL table with site coverage and a verification column.

About Sherlock

Sherlock is a Python command-line tool maintained by Sherlock Project. It takes an exact username and uses site-specific checks to find candidate public profile pages.

Limit a run to the sites in your account inventory, then export candidates as CSV or XLSX. Record the handle, site list and run date so another reviewer can repeat the same check.

An agent can invoke the installed CLI from an authorized shell. A matching handle gives the reviewer a page to inspect. Verify account ownership separately against your account records or another authorized source.

What the Sherlock CLI Returns

Choose the sites your review needs to cover and the format the account owner can work with. A scoped query and saved candidate table make each result easier to trace.

  • Exact username checks

    Check supported sites for public pages that match the handle.

  • Site selection

    Repeat the --site option for each approved platform to keep the run within scope.

  • Candidate exports

    Save candidates in CSV or XLSX and record verification status beside each result.

Sherlock Use Cases for Username Checks

A launch, a rename, a retirement, and a recurring audit each need a different record. Start with handles you manage or are authorized to check.

Check a brand handle before launch

Give the agent the proposed brand handle and the platforms in your launch plan. Ask for candidate links so the launch team can open each page and decide where to register or change the handle.

Reconcile old and new handles

Check both approved usernames against your account inventory. Flag candidates whose profile links or display names still need to be checked before the rename is marked complete.

Review accounts before retirement

Find candidates for a legacy team handle and save them in a review sheet. Ask the account owner to confirm which profiles the team controls before drafting the retirement checklist.

Repeat a platform check

Reuse an approved site list and compare a new run against the previous export. Label new candidates and unresolved site responses separately so reviewers can investigate the differences.

What You Need to Run Sherlock

Give the agent a working CLI, permission to reach the selected sites, and a folder for the candidate report before approving the query.

  • Installed CLI

    Follow the official installation guide and verify sherlock --version in the agent’s shell.

  • Approved scope

    Provide the exact handle and the supported sites that may be queried.

  • Writable output directory

    Use an approved folder for exports and any ownership verification notes.

Related Software Projects

Compare the workflows, operating requirements, and source licenses of these projects.

Sherlock FAQ

What input should I give Sherlock?
Supply an exact username and a bounded list of supported sites. Start with a handle you manage or have permission to check.
Does a hit identify an account owner?
A hit is a possible match flagged by Sherlock. Open the page and check authorized account records before attributing ownership.
How can an agent run Sherlock?
A terminal-enabled agent can call the installed CLI with approved inputs and network access to the selected sites.
Can I export candidates to a spreadsheet?
Sherlock supports CSV and XLSX. Keep the export in the approved folder and add a separate column for verification.
Why might a known profile be missing?
The site may be unsupported, have changed its responses, or limit requests. Check directly and record the coverage gap.
Does Sherlock read private profiles?
The CLI checks public site responses. The findings depend on what each supported website exposes and how its checks work.