Maigret Username Scraper - Accounts Across 1,490+ Sites

Hunt a username across 1,490+ social networks and websites using the Maigret OSINT site database - the deep net for username investigations. For each handle you get every site where an account exists, the profile URL, the site category, and a discrimination-verified match status that suppresses false positives.

Filter by category, check up to 100 handles at once. No login, no API key.

What it does

• Checks a username against 1,490+ sites across 46 categories (social, coding, gaming, crypto, forums, photo, business, and more).
• Returns the sites where an account exists, each with the direct profile URL and its category.
• Verifies every hit (verifyClaims, on by default): re-checks each positive with a decoy handle and drops sites that can't distinguish a real account - so "found" means found.
• Category filter - restrict the hunt to, say, only coding or crypto sites.
• Optional full per-site audit (includeUnclaimed) for username-availability research.

Sherlock vs Maigret

Use Sherlock Username Scraper for a fast pass over ~481 well-known sites. Use Maigret when you want the widest possible net (1,490+ sites) and category filtering. Same verified-match engine underneath.

Example output

{
  "type": "account",
  "username": "torvalds",
  "site": "GitHub",
  "category": "coding",
  "url": "https://github.com/torvalds",
  "status": "claimed",
  "detectionType": "message",
  "httpStatus": 200,
  "source": "maigret",
  "checkedAt": "2026-08-27T05:30:00.000Z"
}

Field	Meaning
username	The handle that was checked
site	Site / network name
category	Site category (social, coding, gaming, crypto, ...)
url	Direct profile URL for that handle
status	claimed (account exists), or available / unknown when Include unclaimed is on
detectionType	How the site was checked: status_code, message, or response_url
httpStatus	HTTP status returned by the site

Input

Field	Description
Usernames	Handles to hunt (up to 100).
Max sites per username	How many of the 1,497 sites to check per handle (most-characterized first).
Site categories	Optional filter - only check sites in these categories.
Verify claims	Re-check positives with a decoy handle to kill false hits (recommended).
Include unclaimed / unknown sites	Also output where the handle was NOT found - full audit.
Include adult (NSFW) sites	Off by default.
Proxy	Residential proxies improve coverage.

Use cases

• OSINT & investigations - map the full online footprint of a handle.
• Brand protection - find impersonation accounts across the web.
• Username availability - see where a new handle is still free.
• Profile enrichment - resolve a handle to its profile URLs, by category.

Notes on accuracy

Username hunting is best-effort. claimed means the site's "not found" signal was absent and (with Verify claims on) the site could tell a real handle from a decoy. Sites that block datacenter IPs are reported as unknown, not guessed - use residential proxies for the widest coverage. A larger Max sites per username = more coverage but longer runs.

Run it from an agent (MCP / API)

Agent-ready: typed input schema, structured JSON output. An LLM agent or automation can call this Actor over the Apify API / MCP to answer "where does this username exist?" in one step. Pass usernames (optionally tags) and read the account records back.

FAQ

Login or API key? No - public presence signals only. Will it find every account? No tool can. Maigret maximizes coverage (1,490+ sites) and is honest about what it can't determine (unknown). Is this legal? It checks publicly observable existence signals. Use the results in line with each site's terms and applicable law.