Brand Username and Impersonation Monitor

Monitor brand usernames, public handles, social profiles, and possible impersonation matches across public platforms with Sherlock and Maigret-powered checks. Use it as a brand username checker for current-run public profile review.

What this Actor does

Brand Username and Impersonation Monitor checks brand names, product names, organization names, usernames, and public handles across social media, developer sites, forums, marketplaces, and other public platforms. It helps teams find public profile matches, review username availability signals, and surface possible impersonation signals without logging in to platforms or collecting private data.

The Actor combines Sherlock username checker style discovery with Maigret username search coverage where possible. It normalizes results, merges duplicates, assigns confidence scores, and adds review-focused risk labels for the current run.

Use it as a brand username monitor, username availability checker, social media username checker, brand profile monitor, social profile finder, username search tool, public profile monitor, brand protection tool, Apify username checker, Sherlock username checker, or Maigret username search workflow.

Who this is for

• Startups preparing a product launch
• SaaS companies monitoring brand handles
• E-commerce brands checking public marketplaces and profiles
• Creators monitoring public creator handles
• Agencies managing brand protection for clients
• Brand protection teams reviewing possible impersonation
• Trademark teams checking public profile use
• Reputation monitoring teams tracking public brand mentions in usernames
• Product launch teams checking username availability before release

Use cases

• Check if a brand username is already used
• Review public profile matches for a current brand check
• Find public profile matches across platforms
• Surface possible brand impersonation signals for review
• Check username availability before a product launch
• Monitor product names and creator handles
• Build a current-run public profile review dataset

How it works

The Actor checks public platforms for the names you provide. It generates safe username variants, runs Sherlock as the fast primary engine, and uses Maigret for fallback, enrichment, and cross-checking with sensible defaults.

Results are merged, deduplicated, and normalized into a clean default dataset for the current run. Each result includes the platform, public profile URL, confidence score, risk label, source engines, and whether both engines agreed. If a run succeeds but produces no profile matches, the Actor emits one diagnostic dataset item explaining the likely cause instead of leaving users with a blank output. The Actor does not write persistent state, named datasets, key-value store summaries, or feed records.

Input

• brandNames: Brand names, product names, organization names, or usernames you own or are authorized to monitor.
• scanMode: Scan level. Choose fast, balanced, or deep.
• sources: Broad source groups to check, such as social, developer, forums, marketplaces, video, or all.
• includeVariants: Generate common username variants.
• maxVariantsPerName: Limit generated variants per brand name.
• maxSitesPerName: Limit platform definitions checked per username variant.
• maxResults: Stop after this many profile match records.
• proxyConfiguration: Apify Proxy settings for public platform checks and lightweight verification.

Default behavior:

• Runs a balanced scan.
• Checks common social, developer, forum, and marketplace platforms.
• Generates safe username variants automatically.
• Returns found or review-worthy results.
• Uses Apify Proxy by default.
• Caps platform checks and output size to keep broad scans practical.
• Does not write persistent monitoring state, named storage, or key-value store artifacts.

Output

Example output item:

{
  "recordType": "profile_match",
  "searchedName": "openclaw",
  "searchedVariant": "openclaw",
  "platform": "YouTube",
  "platformDomain": "youtube.com",
  "profileUrl": "https://www.youtube.com/@openclaw",
  "status": "found",
  "confidence": 0.92,
  "riskLevel": "review",
  "riskType": "possible_brand_match",
  "sourceEngines": ["sherlock", "maigret"],
  "engineAgreement": true,
  "scrapedAt": "2026-05-17T10:00:00.000Z"
}

What confidence means

High confidence means stronger evidence from engine agreement and/or lightweight public verification. Medium confidence means the result is likely relevant but should be reviewed. Low confidence means the match is weak, uncertain, unverified, or from a lower-relevance signal.

What riskLevel means

riskLevel is a prioritization label for brand review. It is not a legal conclusion and does not prove impersonation or infringement. review means a human should inspect the public profile before taking action.

Sherlock and Maigret engine behavior

Sherlock is used for fast username checks across supported public websites. Maigret is used for fallback, enrichment, and cross-checking. The Actor merges and normalizes results from both engines. When Sherlock and Maigret find the same public profile, engine agreement increases confidence.

Scan levels:

• fast: Uses Sherlock as the primary engine, with Maigret only as a fallback if Sherlock fails for a username.
• balanced: Recommended default. Uses Sherlock first, then Maigret for sparse results, important gaps, and enrichment.
• deep: Uses both Sherlock and Maigret for each checked variant. Keep maxSitesPerName practical when using sources: ["all"].

Source groups:

• all
• social
• video
• developer
• forums
• marketplaces
• gaming
• crypto
• music
• blogging

Storage behavior

The Actor only pushes current scan results and no-result diagnostics to the default dataset, which is the standard Apify result output. It does not create named datasets, write persistent state, save index stores, or write RUN_SUMMARY, RSS_XML, JSON_FEED, or debug records to the key-value store.

Python API example

from apify_client import ApifyClient

APIFY_TOKEN = "YOUR_APIFY_TOKEN"
ACTOR_ID = "thescrapelab/brand-username-profile-monitor"

client = ApifyClient(APIFY_TOKEN)

run_input = {
    "brandNames": ["openclaw", "openclawai"],
    "scanMode": "balanced",
    "sources": ["social", "developer", "forums", "marketplaces"],
    "maxSitesPerName": 150,
    "maxResults": 250,
    "proxyConfiguration": {"useApifyProxy": True}
}

run = client.actor(ACTOR_ID).call(run_input=run_input)

print("Current run results:")
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Limitations

• This Actor checks public web results only.
• It does not access private accounts or private data.
• It does not log in to platforms.
• It does not collect personal contact details.
• It does not prove legal impersonation.
• Some platforms may block automated checks or change their pages.
• Some results may be false positives or false negatives.
• Confidence scores are best-effort.
• Human review is recommended for important brand decisions.

Compliance note

Users are responsible for using the data lawfully and respecting platform rules and applicable laws. This Actor is for brand monitoring, username availability checks, and public profile review for names and usernames you own or are authorized to monitor.

FAQ

Does this Actor check all social media platforms?

No. It checks public platforms supported by the underlying username-check engines and the Actor defaults. Coverage can change as platforms change.

Does it use Sherlock and Maigret?

Yes. Sherlock is used as the fast primary engine. Maigret is used for fallback, enrichment, and cross-checking.

Does it require login?

No. The Actor does not use login credentials, cookies, or account sessions.

Does it collect private data?

No. It is designed for public profile matching only and does not collect private messages, hidden profile data, emails, phone numbers, or sensitive personal data.

Can it monitor new profiles over time?

It can be scheduled for repeated current-run checks, but it does not store cross-run state. Compare exported datasets in your own system if you need new or changed profile detection.

Can it check username availability?

Yes. It can help review public username availability signals by showing where matching public profiles are found. Availability should still be confirmed directly on the platform before business or legal decisions.

Why are some results uncertain?

Platforms may block automated requests, redirect profile URLs, return ambiguous pages, or change their public pages. Confidence scores reflect the available evidence and are best-effort.

Can I export CSV, JSON, or Excel from Apify?

Yes. Apify datasets can be exported in formats such as JSON, CSV, Excel, XML, RSS, and HTML from the dataset export options.

Can I schedule it?

Yes. You can schedule repeat runs in Apify to monitor public profile matches over time.

Is this a legal impersonation detector?

No. It identifies possible brand matches and possible impersonation signals for human review. It does not make legal conclusions.

Start monitoring

Run the Actor with your brand names or usernames to start monitoring public profile matches across platforms.