Sherlock vs Maigret vs MyRecon: Username Search Compared

Updated 8 October 2026 · MyRecon editorial

Quick answer: Sherlock is a focused local username checker, Maigret adds enrichment and reporting options, and MyRecon provides a browser workflow with public-source leads and coverage context. Choose for your setup and evidence needs. A bigger result list is not proof of better accuracy.

Scope and publisher disclosure

MyRecon publishes this comparison and is one of the products discussed. We reviewed the official sources on 8 October 2026 and checked MyRecon's source for the features described here. This article compares workflows and explains how to evaluate findings. We did not run a new all-platform performance benchmark for this article.

See the Sherlock repository, Maigret repository and their current help before installing. Documentation and bundled site rules can differ between releases, so record the version you actually run. MyRecon's access conditions can also change.

How the workflows differ

For Maigret's configurable reporting and scope, consult its command-line options. MyRecon's full username workflow retains unresolved responses separately; that helps show the observation boundary, but does not remove the need to open important sources yourself.

Three reasons output counts disagree

Different catalogues: tools may check different platform sets, mirrors or URL forms. Count exact account namespaces and source addresses before comparing totals. Different evidence rules: one checker may accept a page that another treats as ambiguous. Different conditions: blocks, timeouts, redirects and source changes can alter an observation even with the same handle.

A report with 20 links is not automatically better than one with 12. Some may be duplicate addresses, mentions instead of profiles, generic pages or uncertain leads. Conversely, a conservative tool may miss a real account because it cannot obtain decisive public evidence. Both false positives and false negatives matter, and unknowns need their own count.

A fair small comparison you can reproduce

1. Define the question. For example, evaluate public account existence on a few named platforms for accounts you control.
2. Write a reference record. Use current account-specific pages or official source responses. Keep ambiguous references unscored.
3. Record the setup. Include versions, site rules, selected sites, timeouts and check dates. Preserve command settings or the web scan record.
4. Compare shared source addresses. Separate the shared platform view from each full-catalogue view.
5. Review each disagreement. Determine whether the original page supports, contradicts or fails to resolve the claim.
6. Publish the limits. State the usernames, platforms and conditions covered, alongside unknowns and exclusions.

The recorded MyRecon comparison data and reproduction notes illustrate why evidence and catalogue scope matter. That recorded case concerns one username; it cannot establish overall tool accuracy. The homepage also explains the separate daily benchmark's restricted platform scope. Read the methodology rather than extending a narrow result to every website.

Illustrative local commands

These examples are based on documented options and were not executed for this article. Replace YOUR_HANDLE with an account you control or an identifier within your authorized task, and confirm the installed version's help first.

sherlock YOUR_HANDLE --site GitHub --csv
maigret YOUR_HANDLE --site GitHub --no-recursion --html

Both examples deliberately start with one named site. Disabling Maigret recursion keeps discovered identifiers from silently expanding this exercise. In MyRecon, start the same handle in the username tool, inspect that platform's result and record any scope or access difference. Equivalent input alone does not make endpoints, timing or validation rules identical.

Frequently asked questions

Is Maigret more accurate than Sherlock?

A larger catalogue or richer report does not establish greater accuracy. Compare the same source addresses, supported reference outcomes, tool versions and unresolved checks before making a scoped conclusion.

When should I choose MyRecon instead of a local CLI?

Choose MyRecon when browser access and visible source leads suit your task. Choose a local tool when you need to control the environment and its configuration. MyRecon access depends on guest previews, sign-in, allowances and plan.

Do all three tools prove who owns a profile?

No. A username match is a candidate account. Similar handles, copied photos and inferred links can connect unrelated people; ownership and identity require separate confirmation.

Try the MyRecon browser workflow or read the username tool selection method and account enumeration false-positive guide.

More from the MyRecon blog · Browse all guides