Monitor Lookalike Usernames for Impersonation

Impersonators register the near-miss variants — check them as a set. Thirdwatch's Username OSINT Scraper checks a username across 40+ platforms in one run and returns a per-site verdict with the profile URL — GitHub to Reddit to Keybase.

Skip the setup: Run this as a ready-to-go task on Apify — pre-loaded with the configuration from this guide.

Why monitor lookalike handles

Impersonation doesn't take your exact handle — it takes yourname_dev, yourname.official, yournamehq. The monitoring set is the variant list, not the single name.

usernames takes the whole variant list; each username × site combination returns its own row.

The checker resolves each platform's profile URL pattern and reports the verdict with the HTTP status behind it — one run replaces an afternoon of tab-checking.

How does this compare to the alternatives?

Why this Actor

• 40+ platforms per run — code, social, creator, and niche sites in one sweep.
• Clean verdicts per site: exists, not_found, or error — never ambiguous.
• profileUrl gives the canonical link when the account exists.
• httpStatus exposes the evidence behind each verdict.
• Bulk input — a watchlist of usernames runs in one go.

How to do it in 3 steps

Step 1: Configure the input

Set the inputs as shown below — usernames takes the targets, sites restricts the sweep to a subset — omit it to check all 40+ supported platforms.

Step 2: Run the Actor

Run it from the console, the API, or the linked saved task. One dataset row is written per site check.

Step 3: Use the output

Each row carries username, site, a status verdict (exists/not_found/error), the profileUrl when found, and the httpStatus behind the verdict.

{
  "usernames": [
    "pushpak",
    "pushpak_dev",
    "pushpak.dev"
  ]
}

Each dataset row looks like:

{
  "username": "pushpak",
  "site": "github",
  "status": "exists",
  "profileUrl": "https://github.com/pushpak",
  "httpStatus": 200
}

What to watch for

Verdicts are status-code based — a handful of sites rate-limit aggressively and may return error rows under load; retry those rather than counting them as absent. exists proves the handle is registered, not who owns it.

Related use cases

• Audit Your Brand Handle Across 40+ Platforms
• Check a Username Across Developer Platforms
• Check a Username Across Creator Platforms
• Sweep Social Platforms for a Username
• All Thirdwatch use-case guides

Run the Username OSINT Scraper on Apify Store — pay per result, free to try, no credit card to test.