Username Search & Checker — OSINT Lookup on 450+ Sites
Pricing
from $3.25 / 1,000 username checkeds
Username Search & Checker — OSINT Lookup on 450+ Sites
Find where a username is registered on 450+ social, developer, gaming and creative sites, like Sherlock with no install. Each site is found, not found or unknown; sites that answer any name are never billed as found. Filter by site or category.
Pricing
from $3.25 / 1,000 username checkeds
Rating
0.0
(0)
Developer
Automation Lab
Maintained by CommunityActor stats
3
Bookmarked
805
Total users
41
Monthly active users
20 hours ago
Last modified
Categories
Features
Share
Username Checker is the most comprehensive username lookup tool on Apify. Enter any username and instantly see where it is registered across 450+ social media, developer, gaming, music, video, and creative platforms — with direct profile links, platform categories, and a clear status for every site: found, not found or unknown.
Powered by the same platform database as the popular open-source Sherlock project, but delivered as a fully managed, no-install cloud API with batch processing, JSON/CSV/Excel export, and Zapier/Make integrations.
What does Username Checker do?
Username Checker scans 450+ social media and web platforms in seconds to tell you exactly where a username is registered. Enter any username and get a full report showing which platforms have a matching profile, complete with direct links, platform categories, and availability status.
The actor sends lightweight HTTP requests to each platform's profile URL and checks whether the profile exists. No browser automation, no headless Chrome, no Puppeteer — just fast HTTP checks that run on 512 MB of memory and finish in a few minutes per username.
Found means found. Many sites answer every profile URL with a normal page, so simple checkers report them as "found" for any name. Each run first checks a random name that nobody has registered: a site that "finds" it as well cannot confirm anything, so its rows are marked unknown and are never billed as found profiles. Blocked or failed requests are unknown too, not silently "available".
Use it to audit your own online presence, investigate a brand name before registering it, research someone's digital footprint, or verify that your desired handle is available everywhere you want it.
Who is it for?
🔎 OSINT researchers — Map a person's digital footprint across 450+ platforms in a single API call. Feed results into investigation pipelines or link analysis tools. Works like Sherlock username checker but with no local install required.
🏢 Brand managers — Check if your company or product name is already taken on major platforms before launching. Identify squatters and impersonators.
🎨 Content creators — Secure a consistent username across YouTube, TikTok, Instagram, Twitch, and 440 other platforms before someone else grabs it.
🛡️ Cybersecurity professionals — Detect fake accounts, monitor brand impersonation, and enumerate user presence across services during security assessments.
📊 Marketing agencies — Run username audits for clients. Export results to spreadsheets or feed them into dashboards via the API.
👤 Anyone picking a new username — Before you commit to a handle, find out where it is already taken and where it is still available.
Why use this checker?
| Manual checking | Username Checker | |
|---|---|---|
| ⏱️ Speed | 30–60 minutes per username | Under 60 seconds per username |
| 🌐 Coverage | 10–15 platforms you remember | 450+ platforms, every time |
| 📋 Output | Notes in a spreadsheet | Structured JSON with direct profile links |
| 🔄 Automation | Copy-paste in browser tabs | API, webhooks, scheduled runs |
| ✅ Accuracy | Depends on you | Random-name check on every site; unconfirmable sites are unknown, not billed as found |
| 💰 Cost | Your time | $0.005 per saved username-platform result |
| 🔗 Integrations | None | Zapier, Make, Google Sheets, Slack, 1000+ apps |
| 📈 Scalability | One at a time | Batch check up to 100 usernames per run |
| 🔧 Setup | Install Python + Sherlock locally | Zero install — runs in the cloud |
Platforms checked
Username Checker covers 450+ platforms across 9 categories:
📱 Social (58 platforms)
Twitter/X, Instagram, Reddit, TikTok, Snapchat, Pinterest, Tumblr, LinkedIn, Mastodon, Threads, Bluesky, VK, Telegram, Signal, Gravatar, About.me, Linktree, AllMyLinks, Clubhouse, Disqus, Kik, Keybase, Myspace, 9GAG, Plurk, pixelfed.social, and more
💻 Development (99 platforms)
GitHub, GitLab, BitBucket, Codeberg, HackerOne, Replit, CodePen, CodeSandbox, npm, PyPI, RubyGems, Docker Hub, Hugging Face, HackerRank, LeetCode, Codeforces, Codewars, Kaggle, DEV Community, Hashnode, Medium, Asciinema, Codecademy, SourceForge, TryHackMe, HackTheBox, Pastebin, and more
🎨 Creative (36 platforms)
DeviantArt, Behance, Dribbble, ArtStation, Flickr, Unsplash, VSCO, Wattpad, Archive of Our Own, Imgur, Giphy, Sketchfab, Issuu, Instructables, SmugMug, CGTrader, Cults3D, MyMiniFactory, Tenor, and more
🎮 Gaming (47 platforms)
Steam, Xbox Gamertag, Roblox, Minecraft, Lichess, Chess.com, Itch.io, Kongregate, CurseForge, Speedrun.com, osu!, FortniteTracker, PSNProfiles, RuneScape, Wowhead, GameFAQs, TETR.IO, Monkeytype, and more
🎵 Music (20 platforms)
Spotify, SoundCloud, Last.fm, Bandcamp, Genius, MixCloud, MuseScore, ReverbNation, Discogs, Freesound, Smule, Ultimate-Guitar, Rate Your Music, YandexMusic, and more
📹 Video (18 platforms)
YouTube, Twitch, Vimeo, DailyMotion, Rumble, Kick, Odysee, Trovo, Letterboxd, MyAnimeList, Anilist, Trakt, TheMovieDB, and more
💼 Business (34 platforms)
Freelancer, HubPages, Product Hunt, Gumroad, BuyMeACoffee, Ko-fi, Patreon, Redbubble, Cash App, Venmo, Slack, Open Collective, ResearchGate, Academia.edu, TradingView, Credly, and more
📰 News & Blogging (18 platforms)
Hacker News, Slashdot, WordPress, Blogger, BuzzFeed, Flipboard, LiveJournal, Wikipedia, Fandom, LessWrong, CNET, and more
🔧 Other (122 platforms)
Duolingo, Goodreads, Strava, OpenStreetMap, Apple Discussions, Scribd, Archive.org, BoardGameGeek, Geocaching, and 110+ more niche platforms and forums
Data you get
Every result row contains the following fields:
| Field | Type | Description |
|---|---|---|
username | String | The username that was checked |
platform | String | Name of the platform (e.g., "GitHub", "Twitter") |
category | String | Platform category: Social, Development, Creative, Gaming, Music, Video, Business, News, or Other |
url | String | Direct link to the profile page |
found | Boolean | true only when the site confirmed the profile (status is found) |
status | String | found, not_found, or unknown (the site blocked or failed the check, or answers every name so a profile cannot be confirmed) |
reason | String or null | Why a row is unknown or not checked: request_failed, site_answers_any_name, or username_not_allowed (the site's own username rules reject the name, so it cannot be registered there) |
httpStatus | Number or null | HTTP status the site answered with; null when no request was made or it failed |
By default, results include only found profiles. Turn on includeNotFound to save not_found and unknown rows too (for availability checks, treat only not_found as available), or use platforms and categories to limit checks to the sites relevant to your workflow.
How much does it cost to check usernames?
Username Checker uses pay-per-event pricing on Apify:
| Event | Price |
|---|---|
| 🏁 Actor start | $0.005 (one-time per run) |
| ✅ Username-platform result saved | $0.005 per saved result |
From 4 December 2026 the price will be $0.00475 per run start on every plan and $0.0052 per saved result on the Free and Starter plans ($0.00468 on Scale, $0.00416 on Business and higher). Until then the prices above apply.
Cost examples
| Scenario | Saved results | Cost |
|---|---|---|
| One username with 30 found profiles | 30 | $0.16 |
| One username, 4 selected platforms, all rows saved | 4 | $0.025 |
| Five usernames with 30 found profiles each | 150 | $0.76 |
One username, all 452 rows saved (includeNotFound) | 452 | $2.27 |
The result event is charged per row saved to the dataset, not per input username. With the default includeNotFound: false, only confirmed found profiles are saved and charged; unknown rows are not saved or charged. Enabling includeNotFound saves and charges every row: found, not found and unknown. Platform/category filters can reduce runtime and saved-row charges.
How to use
- 🔗 Go to Username Checker on Apify Store
- ✏️ Enter one or more usernames in the Usernames field (no @ symbol needed)
- 🎯 Optionally select exact Platforms or whole Categories; leave both empty for all 450+
- ⚙️ Choose whether to include not-found rows and set Max Usernames
- ▶️ Click Start to run the actor
- 📊 View results in the Dataset tab — use the "Found Profiles" view to see only confirmed matches
- ⬇️ Export results as JSON, CSV, Excel, or XML
- 🔗 Click any profile URL in the results to visit the profile directly
Input parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
usernames | String array | Yes | — | List of usernames to check. Plain usernames only — no @ symbol, no URLs. |
platforms | String array | No | All | Exact platform names to check, matched case-insensitively. |
categories | String array | No | All | Categories to check: Social, Development, Creative, Gaming, Music, Video, Business, News, or Other. |
includeNotFound | Boolean | No | false | Save both found and not-found rows. |
maxUsernames | Integer | No | 10 | Maximum number of usernames to process from the list. Range: 1–100. |
When both filters are supplied, the Actor checks their union and removes duplicate platform names. Unknown values are reported; a run fails clearly if none of the supplied names or categories match.
Example input
{"usernames": ["johndoe", "janedoe", "elonmusk"],"platforms": ["GitHub", "Reddit", "TikTok", "Instagram"],"categories": ["Development"],"maxUsernames": 10}
Output example
[{"username": "johndoe","platform": "GitHub","category": "Development","url": "https://www.github.com/johndoe","found": true,"status": "found","reason": null,"httpStatus": 200},{"username": "johndoe","platform": "Twitter","category": "Social","url": "https://x.com/johndoe","found": true,"status": "found","reason": null,"httpStatus": 200},{"username": "johndoe","platform": "Instagram","category": "Social","url": "https://instagram.com/johndoe","found": false,"status": "unknown","reason": "request_failed","httpStatus": null},{"username": "johndoe","platform": "Reddit","category": "Social","url": "https://www.reddit.com/user/johndoe","found": true,"status": "found","reason": null,"httpStatus": 200},{"username": "johndoe","platform": "Steam","category": "Gaming","url": "https://steamcommunity.com/id/johndoe/","found": false,"status": "not_found","reason": null,"httpStatus": 404}]
Each run produces up to selected platform count * processed username count result rows when includeNotFound is enabled. With default settings, only found profiles are saved. The run's status message says how many usernames and sites were checked, how many profiles were found and how many checks were unknown.
Tips for best results
🔤 Use plain usernames — Enter johndoe, not @johndoe or https://twitter.com/johndoe. The actor builds the correct URL for each platform automatically.
📝 Check variations — If your preferred username is taken, try variations in the same run: johndoe, john_doe, johndoe_, thejohndoe.
📦 Batch similar checks — Checking 10 usernames in one run is cheaper than 10 separate single-username runs (you save $0.09 on start fees).
⚡ Keep batches reasonable — The actor processes usernames sequentially. A batch of 100 usernames takes longer than a batch of 10. Use maxUsernames to cap large lists.
🎯 Select relevant sites — Use platforms for exact names and categories for groups. Selections are case-insensitive and combined, so platforms: ["GitHub"] plus categories: ["Social"] checks GitHub and every Social platform.
🔍 Filter results — Use the "Found Profiles" dataset view in Apify Console to see only platforms where the username exists, or the "All Results" view for the complete picture.
Integrations
Connect Username Checker to your existing tools and workflows:
🔗 Zapier — Trigger username checks when a new row is added to Google Sheets, then write results back automatically.
🔗 Make (Integromat) — Build multi-step workflows that check usernames, filter results, and send alerts to Slack or email.
🔗 Google Sheets — Export results directly to a spreadsheet for easy sharing and analysis.
🔗 Slack / Discord — Get notified when a username is found on specific platforms.
🔗 Webhooks — Receive results via HTTP webhook as soon as the run finishes.
🔗 REST API — Call the actor programmatically from any language or platform.
Learn more about integrations in the Apify integrations documentation.
API usage
Call Username Checker programmatically using the Apify API. Here are examples in popular languages:
Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: 'YOUR_API_TOKEN' });const run = await client.actor('automation-lab/username-checker').call({usernames: ['johndoe', 'janedoe'],maxUsernames: 10,});const { items } = await client.dataset(run.defaultDatasetId).listItems();// Filter to found profiles onlyconst found = items.filter((item) => item.found);console.log(`Found ${found.length} profiles across ${new Set(found.map((i) => i.platform)).size} platforms`);
Python
from apify_client import ApifyClientclient = ApifyClient('YOUR_API_TOKEN')run = client.actor('automation-lab/username-checker').call(run_input={'usernames': ['johndoe', 'janedoe'],'maxUsernames': 10,})items = list(client.dataset(run['defaultDatasetId']).iterate_items())found = [item for item in items if item['found']]print(f"Found {len(found)} profiles")
cURL
# Start the actor and wait for it to finishcurl -X POST "https://api.apify.com/v2/acts/automation-lab~username-checker/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \-H "Content-Type: application/json" \-d '{"usernames": ["johndoe"],"maxUsernames": 10}'
Get your API token from Apify Console Settings.
Server API: check a username over HTTP
Username Checker is also a Server Actor. Besides normal runs, it answers short HTTP requests directly, without starting a run for each username. Copy the server URL from the Actor's Server tab (do not build it from the Actor name) and authenticate with your Apify token. Use normal Actor runs for several usernames.
curl -sS "$SERVER_URL/username?username=apify" -H "Authorization: Bearer $APIFY_TOKEN"curl -sS "$SERVER_URL/username?username=apify&platforms=GitHub,Reddit&categories=Gaming&includeNotFound=true" -H "Authorization: Bearer $APIFY_TOKEN"
| Method and path | Input | Output and charge |
|---|---|---|
GET / | None | ready: true, the route, limits, platform count and categories; no check or charge |
GET /username | Query username (letters, digits, ., _, -, at most 64; a leading @ is removed); optional platforms (exact names) and categories, repeated or comma-separated, combined as a union like normal runs; optional includeNotFound (true/false, default false) | {ok,count,results} with the same rows as a normal run's dataset: the platforms where the username exists, or every answered platform with includeNotFound=true; one Username checked event per returned row, the same unit as a normal run; no start fee |
A request checks every platform by default (450+), at most 100 at a time and 8 seconds per platform, and usually answers in 20–25 seconds; select platforms or categories for a faster answer. Platforms that have not answered when the 45-second deadline approaches are left out of the response (neither found nor not found). Rows carry the same status, reason and httpStatus fields as normal runs; with the default includeNotFound=false only confirmed found rows are returned and charged. Unlike normal runs, an unknown platform or category name is rejected instead of ignored. A username found nowhere is a free 404. Each response is capped at 256 KiB, and one server works on at most three requests at once. Only one thing is cached: which sites "find" a random name, kept for up to 6 hours, so the first request after a server start makes two checks per site. Errors use { "ok": false, "error": { "code": "...", "message": "...", "retryable": false } }: 400 INVALID_USERNAME, UNKNOWN_PLATFORM, UNKNOWN_CATEGORY or INVALID_INPUT; 402 spending limit; 404 USERNAME_NOT_FOUND or unknown route; 405 wrong method; 502 PLATFORMS_UNREACHABLE (none of the selected platforms answered), UPSTREAM_ERROR or charging failure; 503 server busy or stopping; 504 TIMEOUT (no platform answered in time). Errors are free. Retry only when retryable is true. A successful answer can carry warning: { code: "CHARGE_INCOMPLETE" } when only part of its charge went through; you are charged only for what went through. The Server tab shows the full OpenAPI description.
Diagnostic reporting
When a run or server request fails, Username Checker sends sanitized diagnostic input, the exception and the Actor, build and run IDs to our private GlitchTip service so we can repair it. Secret fields and URL queries are removed, and reports are kept for 30 days.
MCP integration
Use Username Checker as a tool inside AI assistants via the Model Context Protocol (MCP).
Claude Code
Add the actor as an MCP tool from your terminal:
$claude mcp add --transport http apify https://mcp.apify.com?tools=automation-lab/username-checker
Or add this to your Claude Code MCP configuration:
{"mcpServers": {"apify": {"url": "https://mcp.apify.com?tools=automation-lab/username-checker"}}}
Claude Desktop
Add this to your Claude Desktop configuration file (claude_desktop_config.json):
{"mcpServers": {"apify": {"url": "https://mcp.apify.com?tools=automation-lab/username-checker"}}}
Cursor
Add the same mcpServers JSON to .cursor/mcp.json in your project.
VS Code
Add the server URL to your workspace MCP configuration under .vscode/mcp.json, using apify as the server name.
Example prompts
Once connected, Claude can check usernames for you directly in conversation. Try prompts like:
- "Check if the username
techguruis available across social media and developer platforms." - "Find where
brandlaunch2026is already registered and return the found profile URLs." - "Check these usernames for GitHub, Reddit, TikTok, and Instagram presence before I pick a brand handle."
Legality
✅ Yes. Username Checker only accesses publicly available profile pages — the same pages any person can visit in a web browser. It does not bypass any login walls, CAPTCHAs, or access controls. It does not scrape private data, personal information, or protected content.
The actor checks whether a profile URL returns a valid page or a "not found" response. This is functionally identical to typing a URL into your browser's address bar.
Key points:
📌 No authentication is used or bypassed on any platform.
📌 No private or protected data is accessed.
📌 No rate-limiting mechanisms are circumvented.
📌 Results contain only the username, platform name, profile URL, and existence status — no personal data is extracted from profiles.
Always ensure your use case complies with applicable laws in your jurisdiction and the terms of service of individual platforms.
FAQ
How long does a run take? A single username on all sites typically takes about 1–2 minutes; sites that are slow to answer get one more try. Checking 10 usernames can take 15 minutes or more, so the default timeout is 15 minutes; raise it for bigger batches. If the timeout is reached, rows already found are kept and the status message says so.
Why does the actor show 450+ platforms but I see fewer results?
By default only found profiles are saved. Turn on includeNotFound to get one row per platform; the "All Results" view then shows every found, not_found and unknown row.
Can I check if a username is available (not taken)?
Yes. Turn on includeNotFound and look for rows with status not_found — those are platforms where the username is free. Rows with status unknown could not be checked, so do not treat them as available.
Does it work with usernames that contain special characters?
The actor passes usernames as-is to each platform's URL template. Most platforms support letters, numbers, underscores, and hyphens. Spaces and special characters like @, #, or ! may produce unreliable results because most platforms do not allow them in usernames.
Can I schedule recurring checks? Yes. Use Apify Schedules to run the actor on any interval — hourly, daily, weekly. Combine with webhooks to get notified of changes.
What happens if a platform is temporarily down?
If a platform times out or the request fails, its row is unknown with reason request_failed (saved only with includeNotFound). Re-run the check later for those platforms.
How do I export results? In Apify Console, go to the run's Dataset tab and click the export button. Supported formats: JSON, CSV, Excel (XLSX), XML, and RSS. You can also fetch results programmatically via the API.
Is there a limit on how many usernames I can check?
Each run supports up to 100 usernames (controlled by the maxUsernames parameter). For larger volumes, run the actor multiple times or use the Apify API to start multiple concurrent runs.
Why is a username showing as "found" when the profile does not exist?
Some platforms return a normal page for non-existent profiles. The actor uses each site's own API or not-found message where one exists, and every run checks a random name first: a site that "finds" that name too is marked unknown (reason site_answers_any_name) instead of found. A site can still change its pages between checks; if you notice a consistent false positive, please report it.
Can I check only specific platforms?
Yes. Select exact names in platforms, whole groups in categories, or both. Matching is case-insensitive, mixed selections form a deduplicated union, and leaving both empty preserves the full 450+ platform scan.
Username Checker vs Sherlock
Sherlock is a popular open-source command-line tool for hunting down social media accounts by username. Username Checker is built on the same platform database but runs in the cloud with no installation required.
| Sherlock (open-source) | Username Checker (this actor) | |
|---|---|---|
| 🔧 Setup | Python install, pip, CLI | Zero install — just click Run |
| ☁️ Runs on | Your local machine | Apify cloud |
| 📤 Export | Terminal output / CSV | JSON, CSV, Excel, XML, API |
| 🔗 Automation | Shell scripts | Apify API, Zapier, Make, webhooks |
| 📦 Batch input | One username at a time | Up to 100 usernames per run |
| 🔔 Alerts | None | Webhooks, scheduled runs |
| 🌐 Platform count | ~400 | 450+ |
Use Username Checker when you want Sherlock's power without the local setup overhead, or when you need API access, batch processing, or integrations.
Related tools
🔗 Username Checker — This actor
🔗 Sherlock (open-source) — The Python CLI this actor is inspired by
Explore more actors from automation-lab on the Apify Store.