Maigret Username OSINT — 3000+ Sites | $19/1K

Maigret Username OSINT Scraper

The Actor scans usernames against Maigret's bundled public profile URL database across 3,000+ sites and returns one dataset item for each found account. On the Free plan, the listed primary event is $0.019 per result and an Actor Start event is $0.00005.

• Scan public profile URLs without supplying an API key, cookies, or login.
• Investigate a username across social networks, forums, gaming, dating, and coding platforms.
• Extract profile URLs, site categories, HTTP status, popularity rank, and linked IDs.
• Check candidate handles for recruiting, background checks, or fraud investigations.
• Monitor brand and trademark names across selected site categories.

What you get

The Actor emits one dataset item for each account that Maigret finds.

Field	What it contains
username	The normalized username scanned
site_name	Name of the platform where the account was found
site_url	User profile URL returned by the site
profile_url	Direct URL to the found profile
site_url_main	Main URL of the platform
site_tags	Site categories such as social, photo, video, gaming, coding, blog, music, and news
http_status	HTTP response status from the profile URL
ids_usernames	Other usernames identified on the site
ids_links	External profile links extracted from the page
rank	Alexa-based site popularity rank; lower values indicate greater popularity
query_time_ms	Time used to check the site in milliseconds; may be null

Sample output

This is one real record from the dataset sample.

{
  "username": "elonmusk",
  "site_name": "WordPress",
  "site_url": "https://elonmusk.wordpress.com/",
  "profile_url": "https://elonmusk.wordpress.com/",
  "site_url_main": "https://wordpress.com",
  "site_tags": ["blog"],
  "http_status": 200,
  "ids_usernames": {},
  "ids_links": [],
  "rank": 34,
  "query_time_ms": null
}

Pricing

This Actor uses pay-per-event billing. The two priced events are:

• apify-default-dataset-item is the primary event, described as one scraped result with all fields.
• apify-actor-start is charged when the Actor starts running.

On the Free plan, 1,000 results = $19.00 on Free. One Actor Start event costs $0.00005 on Free, so a run with 1,000 listed primary results would have $19.00 in primary event charges plus $0.00005 for one Actor Start event. At the Free-plan rates, 10,000 results = $190.00 on Free and 10,000 Actor Start events = $0.50 on Free.

The Actor lists an account-found event, but no price is shown for it in the current pricing information.

Plan	apify-default-dataset-item	apify-actor-start
Free	$0.019 per event	$0.00005 per event
Bronze	$0.01881 per event	$0.0000495 per event
Silver	$0.01862 per event	$0.000049 per event
Gold	$0.01843 per event	$0.0000485 per event
Platinum	$0.01824 per event	$0.000048 per event
Diamond	$0.01805 per event	$0.0000475 per event

Apify's Free plan includes $5 of monthly platform usage credit. Using one Actor Start event at $0.00005 on Free, the calculation floor(($5 - $0.00005) / $0.019) gives 263 primary events within that credit.

Platform usage is included in the event prices and paid by the Actor developer, so the user does not pay platform usage separately for this Actor.

How to use

1. Open the Actor from your Apify account.
2. Enter one or more usernames in the required usernames list.
3. Choose the scan scope with topSites, and optionally filter sites with tags.
4. Set timeoutPerSite and maxConnections when you need to adjust waiting time or parallelism.
5. Run the Actor and review the dataset records for found accounts.
6. Repeat the run through Apify Schedules; a weekly or monthly schedule is a suitable starting point for recurring username audits.

Example input:

{
  "usernames": ["elonmusk"],
  "topSites": 100,
  "tags": [],
  "timeoutPerSite": 5,
  "maxConnections": 50
}

Export the Apify dataset as JSON or CSV, or read it through the Apify dataset API.

Input parameters

Parameter	What it does	Default
usernames	Required list of usernames or handles to scan; each username triggers a separate scan	Required
topSites	Checks the top ranked sites up to this number; 0 selects all bundled sites	100
tags	Restricts the scan to sites matching the supplied category tags; an empty list scans all categories	[]
timeoutPerSite	Number of seconds to wait for each site before moving on; accepted range is 1–30	5
maxConnections	Number of sites checked in parallel; accepted range is 1–200	50
disableUsageStats	Disables the usage statistics described below when set to true	false

The Actor accepts handles such as @handle and supported profile URL forms, then removes the leading @ before scanning. Duplicate normalized usernames are scanned once.

Tags are applied before the top-site limit. Common tags include social, photo, video, gaming, dating, coding, blog, messaging, music, news, and adult.

Limits and edge cases

Condition	What you see	What to do
A Free-plan run reaches the 25-account output cap	A partial result is reported, with the Free-plan preview limited to 25 accounts per run; later usernames may not be scanned	Upgrade to any paid Apify plan to remove the Free-plan output cap, or run smaller input lists
usernames is empty or missing	The run fails, records the empty-input reason in OUTPUT, and nothing is charged	Add one or more non-empty handles
A tags filter selects no sites	The run returns no accounts, reports that the filter removed all sites, and nothing is charged	Clear the filter or use tags such as social, coding, photo, video, gaming, blog, or music
The username is not found on the checked sites	The run succeeds with an explained empty result and no accounts returned	Check spelling, widen topSites, set topSites to 0, or clear tags
Site checks time out, are blocked, or have transport errors	Incomplete checks are skipped; when the result is suspect, the Actor makes a second pass on some incomplete checks. A partial result can state that accounts may be missing	Raise timeoutPerSite, lower maxConnections, or retry the run
More than half of the completed checks are unknown after retrying and no account is returned	The run reports a blocked or incomplete scan and fails without a charge	Retry with a longer timeout and lower parallelism
An internal scan error affects one username in a multi-username run	Results for other usernames may be delivered, while the affected username is reported as missing from the partial result	Retry the affected username
topSites is 0	The Actor selects all approximately 3,000 bundled sites for the scan	Use a smaller top-site value when a narrower scan is sufficient

FAQ

How much does it cost to scrape a username's accounts?

The current model is pay per event. The primary dataset event costs $0.019 per result on Free, and an Actor Start event costs $0.00005 on Free. For example, 1,000 results = $19.00 on Free, plus $0.00005 for one Actor Start event.

Why did the run return no accounts?

A username may not match any of the selected sites, or a tags filter may have removed all sites. The Actor explains these cases in the run status and OUTPUT record. Widen topSites, use 0 to select all bundled sites, clear tags, or check the username spelling.

Why is my run not working?

Timeouts, blocks, and transport errors can leave site checks incomplete. The Actor may retry incomplete checks when the result is suspect. If the scan still cannot complete, raise timeoutPerSite, lower maxConnections, and retry. An internal scan error is reported separately from a username that simply has no match.

Is scraping public profile data legal or allowed under site ToS?

The Actor checks public profile URLs directly and does not require a login, cookies, or an API key. Source terms and applicable law depend on your use case, so review the relevant site terms and legal requirements before using the data.

Related actors

• Bluesky Scraper — extract posts, profiles, and followers for Bluesky-related follow-up work.

Usage statistics

This Actor creates a small, content-free summary at the end of each run, used only to monitor reliability and improve this Actor. No input values, credentials or scraped data are sent.

A copy of the exact record for your run is saved as USAGE_STATS in your own Apify key-value store.

To opt out, set disableUsageStats to true in the input. Nothing is sent then.

Full list of collected fields