Maigret Username Checker — OSINT Search Across 3000+ Sites
Pricing
$20.00 / 1,000 profile founds
Maigret Username Checker — OSINT Search Across 3000+ Sites
Enter a username and see where that handle is registered across 3000+ social, forum, gaming, dating and developer platforms — with a direct profile URL for each hit. Powered by the open-source Maigret engine (MIT); rated 5.0★ by users; JSON, CSV and Excel export plus REST API and scheduling.
Pricing
$20.00 / 1,000 profile founds
Rating
5.0
(3)
Developer
daehwan kim
Maintained by CommunityActor stats
3
Bookmarked
766
Total users
139
Monthly active users
2 days ago
Last modified
Share
Maigret Username OSINT Search
Find all online accounts linked to a username in seconds. This username OSINT / people-search tool checks a username across 3000+ websites — social media, forums, dating, gaming, and developer platforms — and returns every matching profile. A fast reverse username lookup powered by maigret (MIT License), ideal for background checks, fraud investigation, and mapping someone's online footprint.
Legal Disclaimer: This Actor is an unofficial integration of maigret and is not affiliated with, endorsed by, or sponsored by the original maigret project or its maintainers. Use responsibly and only on usernames you have authorization to investigate.
What does Maigret Username OSINT Search do?
This Actor runs the open-source OSINT tool maigret to search for a given username across thousands of social networks, developer platforms, forums, and more. It returns a structured dataset of all sites where the username was found — profile URLs, site tags, and HTTP status codes. Personal profile details (full name, avatar, bio, location) are not collected unless you explicitly switch on extractProfileFields.
Use it to find someone by username, run a social media username search, perform background checks, or investigate fraud and impersonation. Built for security researchers, OSINT investigators, journalists, recruiters, and developers who need automated username reconnaissance.
Why use this Actor?
- 3000+ sites checked — GitHub, Twitter/X, Instagram, Reddit, TikTok, LinkedIn, and thousands more
- Account existence by default — results tell you where an account exists, nothing more
- Optional profile details — full name, avatar, bio and location can be saved too, but only if you turn
extractProfileFieldson - Tag-based filtering — filter by category (social, coding, video, dating, etc.)
- Structured JSON output — ready to integrate with Apify datasets, webhooks, or downstream pipelines
- Scheduled runs — set up recurring username monitoring via Apify Scheduler
- API access — call via REST API, MCP, or Apify Console
How to use Maigret Username OSINT Search
- Open the Actor in Apify Console and click Try for free
- Enter a username in the
Usernamefield (e.g.,john) - Configure options — set
Top N sites(default 500), timeout, or tag filters - Start the Actor and wait for results (500 sites ≈ 1–3 minutes)
- Download results from the Output tab as JSON, CSV, or Excel
Input
Batch searching: put your whole investigation list into usernames and the Actor searches each one in turn, writing every result to the same dataset. One run, one export — no need to start the Actor once per person.
| Field | Type | Description | Default |
|---|---|---|---|
usernames | array | Usernames to search. Accepts a list — add as many as you need | — |
username | string | A single username (legacy field, still supported) | — |
maxUsernames | integer | Safety cap on usernames searched per run | 100 |
topSites | integer | Top N sites by Alexa rank (0 = all 3000+) | 500 |
timeout | integer | Per-request timeout in seconds | 30 |
tags | string | Comma-separated tag filter (e.g. social,coding) | — |
excludeTags | string | Comma-separated tags to exclude | — |
sites | string | Specific site names to check (e.g. GitHub,Instagram) | — |
noRecursion | boolean | Disable recursive search for related IDs | false |
extractProfileFields | boolean | Opt-in. Also save personal profile details (full name, bio, avatar, location) | false |
printNotFound | boolean | Include "not found" sites in output | false |
Example input:
{"username": "johndoe","topSites": 500,"timeout": 30,"tags": "social,coding","noRecursion": false}
Output
Each dataset item represents a site where the username was found. This is the default output — account existence only:
{"username": "johndoe","siteName": "GitHub","profileUrl": "https://github.com/johndoe","siteMainUrl": "https://github.com","status": "Claimed","httpStatus": 200,"isSimilar": false,"alexaRank": 65,"tags": ["coding"],"scrapedAt": "2026-04-16T00:00:00.000Z"}
With extractProfileFields: true, each item additionally carries the personal profile details found on the page:
{"fullName": "John Doe","bio": "Software Engineer","image": "https://avatars.githubusercontent.com/johndoe","location": "San Francisco, CA","extractedIds": {"github_id": "12345","fullname": "John Doe"}}
You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.
Data fields
| Field | Format | Description |
|---|---|---|
username | text | Searched username |
siteName | text | Website name |
profileUrl | link | Direct profile URL |
status | text | Claimed (maigret found the username on this site — this is what is charged) / Not Found / Unknown |
httpStatus | number | HTTP response code the site returned. Usually 200. A non-200 code (e.g. 429 too many requests, 401/403 login-or-block, 404) does not mean the account is absent — it is how the site treated the request. See Pricing below. |
alexaRank | number | Site Alexa rank (lower = more popular) |
tags | array | Site category tags |
scrapedAt | date | Timestamp |
fullName | text | Full name — only with extractProfileFields: true |
bio | text | Bio/description — only with extractProfileFields: true |
image | link | Profile avatar URL — only with extractProfileFields: true |
location | text | Location — only with extractProfileFields: true |
extractedIds | object | All extracted identifiers — only with extractProfileFields: true |
Pricing / Cost estimation
This Actor is billed per result: $0.02 per profile found (event: profile-found). Sites where the username is not found are free, and so are runs that find nothing. Apify platform compute is included.
You are charged once for each site where maigret finds the username (status: "Claimed"). Runs that find nothing cost nothing. If a run stops on an engine error before a result is produced, that result is not charged.
Every result carries the site's HTTP response code in httpStatus. Most are 200. Some sites return a different code — 429 (rate-limited us), 401/403 (the profile needs a login, or the site blocked the request), or occasionally 404 for a private or restricted profile. These codes describe how the site answered our request, not whether the account exists, so they are included in the result and charged like any other match. A small number may be false positives from the underlying engine. Because the status code is provided on every row, you can spot the non-200 results and re-check those links yourself — verifying limited or blocked results is left to you.
Typical costs, based on measured runs across the default top 500 sites:
| What you search | Profiles usually found | Cost |
|---|---|---|
| 1 common username | 100–150 | $2.00 – $3.00 |
| 1 rare username | 5–20 | $0.10 – $0.40 |
| 10 usernames | 500–1,500 | $10.00 – $30.00 |
New Apify users receive free monthly credits to get started. To cap spending on any single run, set a maximum cost in the Actor's Run options — see the next section for exactly what happens when a run reaches it.
Large batches and the run charge limit
Every Apify run has a maximum cost, which you set per run (or per schedule) in the Actor's Run options. This Actor can search up to 500 usernames in a single run, and a big batch can easily find more profiles than the default limit covers.
When a run reaches its charge limit, this Actor stops searching and finishes successfully with everything it found up to that point, plus a final Charging limit reached record explaining what happened. You are never charged past your limit, and the run is not reported as a failure.
To get the full batch, do one of the following:
- Raise the run's maximum cost in Run options before starting, or
- Split the usernames across several runs — for example 50 usernames per run instead of 500.
Tips and Advanced Options
- Speed up searches: Set
topSitesto 100–200 for quick checks on major platforms - Category focus: Use
tags: "social"to check only social networks, or"coding"for developer platforms - Specific sites: Use the
sitesfield to check a small custom list (e.g."GitHub,Twitter,Reddit") - Monitoring: Schedule this Actor weekly to detect new account registrations for a username
- Disable recursion: Set
noRecursion: trueto skip recursive sub-searches (faster, less data)
FAQ, Disclaimers & Support
Is this legal?
This Actor searches publicly accessible pages only — the same pages anyone can view in a browser. However:
- By default the Actor records account existence only — which site, which URL. Personal profile details are collected only if you switch on
extractProfileFields, and doing so makes you the data controller for that personal data - Only search usernames you are authorized to investigate (your own, or with explicit permission)
- Comply with applicable laws including GDPR, CCPA, and local privacy regulations
- Do not use results to harass, stalk, or harm individuals
- The Actor does not access private data, bypass authentication, or scrape restricted content
Legal Disclaimer
This Actor is an unofficial integration of maigret (MIT License). It is NOT affiliated with, endorsed by, or sponsored by the original maigret project or its authors. The Actor author provides this tool for legitimate security research, journalism, and authorized investigations only. Users are solely responsible for ensuring their use complies with applicable laws and the Terms of Service of checked websites. The author accepts no liability for misuse.
Privacy & data responsibility
You are the data controller for every search you run with this Actor; ntriqpro is a data processor acting solely on your instructions. You are responsible for having a lawful basis and a legitimate, purpose-limited reason for each lookup, and for complying with GDPR, PIPA, CCPA, and other applicable privacy laws. We do not store your results — output is written only to your own run's dataset and is never retained on our side. Use this Actor only for lawful purposes and only on usernames you own or are authorized to investigate.
Known Limitations
- Some sites may block automated requests (rate limiting, CAPTCHA)
- Results accuracy depends on the maigret database (updated automatically)
- Very common usernames may return false positives on some sites
Support
- Found a bug? Open an issue in the Issues tab
- Need a custom OSINT solution? Contact via the Apify platform
🔗 Related Actors by ntriqpro
Running several of these by hand? OSINT Recon Suite takes one target — username, email, domain or phone — runs Maigret, Sherlock, holehe, theHarvester, WHOIS and dnstwist against it, then correlates everything into a single risk-scored report. One input, one report, instead of six separate runs to stitch together yourself.
Build your full OSINT stack:
- email-osint-search — Email OSINT — find which 120+ sites an email is registered on
- phoneinfoga-osint — Phone number OSINT — carrier, country & footprint
- dnstwist-osint — Typosquatting & phishing domain detector
- subfinder-osint — Subdomain finder for attack-surface mapping
- gitleaks-secret-scanner — Find leaked API keys & secrets in public repos
⭐ Love it? Leave a Review
Your rating helps professionals discover this actor. Rate it here.