About / How it works

Public signals.
Context you can inspect.

SpiderFoot.app brings username discovery and email registration checks into one browser workspace. Follow possible accounts, review the returned evidence, and keep the uncertainty visible.

01 / Purpose and coverage

One place to collect and review leads.

Checking a public footprint often means repeating small searches and keeping track of where each result came from. This workspace keeps those checks together, with source links, additional profile clues when available, and a complete live response log.

Username discovery

Enter an exact handle without spaces, up to 100 characters. Positive account signals appear as possible matches. Extra information returned by a positive source may also provide possible names, aliases, or email addresses, with source attribution.

2,500+configured checks
15+source groups
4parallel groups
Search a username

Email registration signals

Enter a complete email address to check supported services for registration-style signals. Many checks do not return an account username or profile link. The workflow does not open the inbox, send mail, or verify mailbox delivery.

200+configured checks
20+source groups
1group at a time
Review an email

These figures describe the current configuration. They do not promise that every source will respond or that every account will be found.

Username source coverage

CategorySite checks
Social280
Creator41
Dev456
Creative144
Community576
Gaming213
Entertainment108
Music125
Learning267
Shopping56
Donation7
Finance151
Email1
Other79
Dating9
Political4
Adult22

Email source coverage

CategorySite checks
Social18
Dev21
Creator13
Community5
Shopping18
Entertainment13
Other14
Gaming5
Learning29
Jobs14
Music5
Travel4
Fitness5
Hosting2
Crm4
News8
Sports7
Dating11
Women Health7
Adult17
02 / Our method

From an identifier to reviewable results.

Both workflows follow the same path. Their positive-result rules differ, while all returned source rows remain available in the live log.

  1. 01

    Choose one identifier

    Start with an exact username or complete email address you are authorized to investigate.

  2. 02

    Check the input

    The workspace trims the value and applies the selected workflow's format rules before scanning.

  3. 03

    Check source groups

    The browser requests the configured scan service, one category and page at a time. Username categories can run in parallel.

  4. 04

    Keep the responses

    Returned statuses, links, reasons, and extra fields stay together in expandable category reports.

  5. 05

    Collect positive signals

    Found username rows and Registered email rows become possible-match cards, with duplicates removed by source name and URL.

  6. 06

    Review the source

    Open the original site, check the context and date, and compare independent evidence before linking identities.

Understanding progress

Progress follows the number of checks reported by the scan service. Pages within each category run in sequence. The indicator reaches 100% when the run has finished, including runs with request errors; it does not certify complete coverage or accurate results.

Pause prevents new requests while active requests finish. Restart begins another run and ignores late responses from the earlier one. A failed page is reported rather than automatically retried.

03 / Reading a result

Each status describes a check.

A detection result and an identity conclusion are different things. A real public profile can still belong to someone other than the person you had in mind.

Returned statusHow it appearsHow to interpret it
Username: FoundPossible-account card and live logA candidate account signal. Verify the page and its owner independently.
Email: RegisteredPossible-account card and live logA registration signal, which may not expose a username or profile URL.
Not Found / Not RegisteredLive log onlyA negative response from that particular check at that time, not universal absence.
Unknown / other statesLive log onlyNo exact positive classification. Leave the result unresolved.
SkippedLive log, with a reason when returnedThe check was not performed. Do not interpret it as a negative result.
Error / timeout / failureLive log and applicable error indicatorsThe check was unsuccessful or incomplete. Account existence remains unresolved.

Status labels and extra fields originate in the scan responses. A matching handle, avatar, name, or email signal alone does not establish identity, ownership, activity, or intent.

04 / Coverage and uncertainty

Public sources change. Results can have gaps.

Shared services have limits

Source sites can respond differently to shared server addresses, regional restrictions, bot protection, rate limits, or temporary outages. A blocked request, timeout, or missing match can describe the request path rather than the absence of an account.

Private, renamed, deleted, or dynamically rendered profiles may be missed. Generic login pages and changed routes can also create misleading signals.

Verify before relying on a finding

  • Open the original source and confirm that its content matches the identifier.
  • Compare dates and independent context; allow for reused, copied, or impersonated handles.
  • Keep failed checks unresolved and record alternative explanations.

For investigations needing a local command-line workflow, explore User Scanner. A different network may produce different results; it does not guarantee complete coverage.

05 / Privacy and history

Choose what stays in your search history.

Standard scans

A task is created before scanning. Positive matches can be saved to the current browser identifier or connected account. The full live log and its negative or failed checks are not saved as positive matches.

Privacy mode

Off by default. Enable it before a scan to skip task creation and history saving. The scan service still receives the identifier and request information; this setting does not make a scan anonymous.

Data controls

Review or rerun saved tasks from the user workspace. Permanently delete individual searches, or delete the current account and all its linked search history. Google login is optional.

Google Dorks search shortcuts

After you submit a query, Google Dorks offers search links based on that exact username or full email address. Each shortcut explains its scope through a question-mark help button. Opening a link sends the generated search to Google in a new tab, including when Privacy Mode is enabled. These are independent searches of Google's index; they do not affect the scan progress or establish account ownership. You can inspect and copy every generated query before opening it.

Read the full Privacy Policy

An independent browser service.

SpiderFoot.app is an independent website for authorized public-source research. It is not the official SpiderFoot project, SpiderFoot HX, or an Intel 471 product. Third-party projects, sources, libraries, names, and logos retain their respective owners and licenses.

The current website focuses on username and email checks, source review, and history controls. It does not provide private-account access, verified identity reports, or a guarantee that a source's classification is correct.

Help us keep the details accurate.

Report a broken source, an incorrect result, or a statement about our method that needs correction. Include the affected page and only the context needed to reproduce the issue.

Contact support