Enumerate a username across hundreds of platforms with sherlock, maigret and WhatsMyName, then correlate and confirm which accounts genuinely belong to the same person. Use for username OSINT and handle enumeration, "find all accounts for this username", cross-platform account correlation, nickname and screen-name pivots, or turning a handle into a real name. Applies to fraud and synthetic-identity investigation, recruitment and marketplace scam checks, trust-and-safety enforcement, insider-thre
Detected risks:
hunt-a-handle is an OSINT skill for username and handle investigation: enumerating a screen name across hundreds of platforms with tools like sherlock, maigret, and the WhatsMyName data set, then correlating and confirming which accounts genuinely belong to the same person. Its guiding thesis is that enumeration is the cheap half and confirmation is the real work — existence checks are HTTP heuristics that produce candidates, not identities, and pasting a tool's hit list into a report is the mistake that ruins these investigations.
The workflow starts with a required authorized-scope step (subject, objective, in-bounds selectors, out-of-bounds actions, jurisdiction) and a companion ethics document. It then guides enumerator choice (sherlock for breadth, maigret for parsed profile fields, WhatsMyName for readable match rules), systematic handle-variant generation (separator swaps, truncations, number suffixes, leetspeak, gamer-tag morphology), and a rigorous confirm-or-reject grading step using strong evidence (matching avatars verified against reverse image search, near-identical bios, self-declared cross-links, shared contact selectors) over weak signals. It documents common false positives — soft 404s, catch-all profile pages, CAPTCHA interstitials, squatted and impersonation accounts — and the collision problem where common handles map to many unrelated people.
It targets fraud and synthetic-identity investigators, recruitment and marketplace scam checkers, trust-and-safety teams, insider-threat analysts, and people auditing their own exposure. It explicitly forbids resolving ambiguity by logging in, messaging, or requesting follows. Despite these guardrails, the capability — correlating scattered accounts into a single real person — is dual-use and can be used to unmask or profile individuals, warranting elevated scrutiny.
sherlock for the largest fast existence sweep, maigret when you need parsed profile fields (display name, bio, IDs, location), the WhatsMyName detection list to see exactly why a hit fired, and manual visits for a known platform.
Enumerators only perform HTTP existence checks, which produce false positives from soft 404s, catch-all pages, CAPTCHA interstitials, and squatted or impersonation accounts; a hit is a candidate that must be confirmed with independent evidence like matching verified avatars or self-declared cross-links.
It requires a written authorized-scope note and forbids interacting with the subject — no logging in, messaging, or requesting follows — because that is out of scope and reveals the investigator's presence.
Handle collision: common or dictionary-word handles belong to many unrelated people, so confidence must scale with the handle's distinctiveness, and a bare handle match is the hypothesis being tested rather than evidence.
Quick Setup:
.claude/skills/Repository
useosint/osint-skills