Username Search & Lookup — Sherlock OSINT on 400+ Sites
Pricing
Pay per event
Username Search & Lookup — Sherlock OSINT on 400+ Sites
Search a username across 400+ sites (Instagram, TikTok, GitHub, Reddit, X, Steam, Twitch) and get a profile URL for each hit. Open-source Sherlock engine (MIT). Free plan checks the top 100 sites; paid plans scan all 400+ at $0.02 per account found. No API keys.
Pricing
Pay per event
Rating
5.0
(1)
Developer
Daniel Carter
Maintained by CommunityActor stats
2
Bookmarked
612
Total users
77
Monthly active users
2 days ago
Last modified
Features
Share
Username search and lookup: enter a username, get one row per site where that account exists, out of 400+ social networks and websites. Each row carries the profile URL, for example johnsmith on GitHub returns https://github.com/johnsmith. It runs the standard open-source OSINT tool Sherlock with zero setup and no API keys.
| Free plan | Paid plan | |
|---|---|---|
| Usernames per run | 1 | Up to 5 |
| Sites checked per username | Full 400+ list | Full 400+ list |
| Accounts shown with site and link | Found on the top 100 sites | Every account found |
| Accounts returned per run | Up to 5 | Every account found |
| Price | $0.02 per username scanned + $0.02 per account found | $0.02 per username scanned + $0.02 per account found |
| Locked part | Accounts found on sites outside the top 100: the notice row at the end of every free run says how many, by category (for example Developer & tech 33, Gaming 18). Their site names and links are locked. Also counted: usernames not scanned and found accounts held back | Nothing locked |
Built for account auditing, brand protection, security research (authorized), due diligence, and journalism. Run it on the Apify platform with API access, scheduling, integrations, and monitoring built in.
Free plan: 1 username, the full site list scanned, up to 5 accounts shown. Runs started from an Apify free plan scan the first username across the full 400+ site list, return up to 5 found accounts from the top 100 sites, and tell you how many more accounts they found on all other sites, by category. The names and links of those are locked; the number is what the scan found, not an estimate. Every paid plan scans up to 5 usernames and returns every account found with its site and link. This is a plan limit, not an error: a free run finishes normally with a status message saying what was found and what is locked.
This Actor wraps the open-source Sherlock (MIT) and is not affiliated with the original project. It checks only public account existence. Use only for lawful purposes and on accounts you own or are authorized to investigate. Comply with GDPR, PIPA, CCPA, and applicable laws.
Why use Sherlock Username OSINT?
- Sherlock, zero setup — no install, no API keys, no configuration
- 400+ sites — GitHub, Reddit, Instagram, TikTok, X, and hundreds more
- Bulk — up to 5 usernames per run (paid plans)
- Structured JSON — site name, profile URL, HTTP status, response time
- Pay per use — $0.02 per username scanned plus $0.02 per account found. No subscription, no monthly fee.
How to use Sherlock Username OSINT
- Enter one or more usernames (or a single username).
- (Optional) Limit to specific sites, raise the timeout, or include NSFW sites.
- Click Start and read the results in the Output tab.
Input
| Field | Type | Description |
|---|---|---|
usernames | array | Up to 5 usernames (letters, digits, . _ -); free plan: the first one |
username | string | Single-username alternative |
timeout | integer | Per-request timeout in seconds (5–120, default 60) |
sites | array | Limit the search to these sites only (optional) |
includeNsfw | boolean | Include NSFW sites (default false) |
{"usernames": ["johnsmith"],"timeout": 60}
Output
One dataset item per found account. Usernames with no results return a single "No accounts found" row.
{"username": "johnsmith","siteName": "GitHub","profileUrl": "https://github.com/johnsmith","siteMainUrl": "https://github.com/","status": "Claimed","secondLook": "confirmed","httpStatus": 200,"responseTimeS": 0.41,"scannedAt": "2026-06-11T10:32:00.000Z"}
You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.
Data table
| Field | Description |
|---|---|
username | The username searched |
siteName | Site where the account was found |
profileUrl | Direct URL to the discovered profile |
siteMainUrl | Home URL of the site |
status | Claimed when the account exists |
secondLook | What a second check of this hit showed (see below) |
httpStatus | HTTP status returned by the site |
responseTimeS | Site response time in seconds |
Second look: which hits to trust
Some sites answer a name that does not exist the same way as one that does, and which sites do so changes from day to day. So every account found is checked again in the same run: the username is scanned once more on the sites that reported it, next to a random name nobody uses. Each row says what that showed:
secondLook | Meaning |
|---|---|
confirmed | Found again, and the site did not "find" the random name |
site-answers-any-name | The site also "found" the random name in this run, so its answer does not tell whether this account exists. Open the profile URL to check |
not-found-on-recheck | The site said the name is free on the second scan |
not-checked | The second scan got no usable answer from this site |
No row is removed and every row handed over is charged as before; filter on
secondLook = confirmed when you only want the checked hits. The second look
makes a run take longer, most on usernames with many hits.
Pricing
This Actor uses pay-per-event pricing with two events:
| Event | Price | When it is charged |
|---|---|---|
username-checked | $0.02 | Once per username whose site scan completed — also when no account was found, because "this username exists nowhere we checked" is the answer you asked for. Not charged for a username rejected before scanning (invalid characters) or a scan that failed on our side (engine error, timeout, missing report). |
account-found | $0.02 | Once per account found (a site where the username is Claimed). |
A username that exists on 20 sites costs $0.02 + 20 × $0.02 = $0.42; a username with no results costs $0.02. Apify platform compute is billed separately per your plan.
Each row is handed over and then charged, one at a time. When the run's charging limit cannot cover the next row, the run stops there and finishes SUCCEEDED with a "Charging limit reached" row: nothing past the limit is handed over, and nothing handed over is left uncharged.
If the platform restarts a run (a server move or a resurrect), the restarted run does
not hand over or charge again what is already in the dataset. Because the platform can
show the last rows and charges a few minutes late, a restarted run first waits about
3 minutes and then checks what the earlier attempt already handed over; a run that
is not restarted does not wait, unless reading its restart record from its own
key-value store fails (then it waits the same way). A run that cannot save its
restart record there and read it back stops before scanning and charges nothing. When scanning a
username again after a restart fails, the accounts found before the restart stay and a
notice row (noticeCode: restart-rescan-incomplete) names that username. When the run
cannot prove what it already handed over, it stops with a notice row (
noticeCode: restart-unsettledFree plan coverage. Free-plan runs scan 1 username on the full 400+ site list and return up to 5 found accounts from the top 100 sites; paid plans scan up to 5 usernames and return everything. The notice row at the end of every free run (
noticeCode: free-plan-previewlocked.byCategory,
freePlan.accountsLockedOtherSites). That count comes from the scan itself
(locked.isEstimate: false); the site names and profile links of those accounts are
never in the dataset, the log or the key-value store. Categories are coarse labels from
the site name and web address. With a sites filter the counts are left out (they would
show whether an account exists on a site you named), and the notice says so. The output fields and prices are identical on every plan.
Status and notice rows are never charged.
Tips
- Limit
sitesto the platforms you care about for faster, cheaper runs. - Increase
timeoutif you suspect false negatives from slow sites. - Schedule recurring runs to monitor when a brand or handle appears on new platforms.
🔗 Related Actors by ntriqpro
Next steps for profiles you find. When the accounts handed over to you include a Threads profile or a YouTube channel, the run ends with an unbilled notice row (noticeCode next-step-threads or next-step-youtube) that links the Actor below and carries an input to paste (nextActor.exampleInput). No other Actor is started and nothing extra is charged. Profiles locked on the free plan are never put in it.
-
Found a Threads profile? Copy its username or profile URL into Threads Scraper to collect posts, replies and engagement, or monitor new posts across runs. Threads Scraper
{"usernames":["<Threads username from your results>"]} -
Found a YouTube channel in your results? Paste its channel URL into YouTube Email Finder to look for public emails in About text and linked websites. Emails behind sign-in are not accessed. YouTube Email Finder
{"channels":["<YouTube channel URL from your results>"]}
- Username Checker & Search — OSINT Across 3000+ Sites Maigret — Username search across 3000+ social, forum, gaming, dating and developer sites, with a profile URL per hit.
- Email OSINT Lookup — Accounts, Profiles & Domain Footprint — Build a public-source digital footprint report from an email, username, domain, or authorized phone number.
- Email & Username Account Finder — Social Footprint Check — Give it one email or username and get back the platforms where that identity is registered — GitHub, GitLab, Instagram, Twitter, Reddit, Tumblr and more — plus a Gravatar/GitHub profile and a 0–100 exposure score.
- Username Lookup — Social Media Account Search 200+ Sites — Username search across 200+ social media, developer, gaming and creator platforms.
- Instagram Reels & Comments Scraper | Brand Monitor — Collect public Instagram reel metrics and sample comments for brand reports.
- Threads Scraper - Posts, Replies, Search & New Post Monitor — Threads scraper with no login: an account's posts with history, every reply as its own row, keyword search results, plus the e-mails, link domains, mentions and hashtags found in them.
FAQ, disclaimers, and support
Is this legal? Checking whether a public account exists is generally lawful, but you are responsible for how you use the results. Do not use this tool for harassment, stalking, or any unlawful purpose. Comply with all applicable laws and platform terms.
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 keep copies of your inputs or results outside your own Apify run; searched identifiers are masked in run logs. These roles are governed by the Standard Actor Contract (§5.2) that applies to this Actor on Apify. Public availability of a profile is not, by itself, a lawful basis — you need your own. Not a consumer reporting agency. Do not use results to make decisions about employment, credit, housing or insurance. Use this Actor only for lawful purposes and only on usernames you own or are authorized to investigate.
Why didn't it find an account I know exists? Some sites rate-limit or block automated checks, which can cause false negatives. Raising the timeout can help.
Found a bug or want a feature? Use the Issues tab. Custom solutions available.
Tell us what output you need
Missing a field, a source, or an export shape? Open a request on the Issues tab and describe the output you want: the columns you need, an example row, or the tool you feed the data into. We read every request, answer on the same thread, and build the ones that fit this Actor.
缺少你需要的字段、来源或输出格式?请在 Issues 标签页告诉我们你想要的输出(需要的列、示例行,或你用来处理数据的工具)。我们会阅读每一条请求并在同一帖子里回复。
Leave a review
A short review on the Reviews tab, good or bad, helps other people find this Actor and tells us what to build next. Found a bug or need a feature? Open an issue on the Issues tab and we'll look into it.