About / Product notes

A focused workspace for public signals—and the uncertainty around them.

Discover Profile organizes username and email account checks in one browser-based workflow. It helps you collect and review leads; it does not verify identity, ownership, intent, or wrongdoing.

01 / Purpose

Why this workspace exists

Public-information research often starts with small, repeatable checks: whether a handle appears on a public site or whether a provider returns an account-context signal for an email address. Repeating those checks across unrelated tools makes it easy to lose the source, the status, or the limits of the result.

Discover Profile brings a deliberately narrow set of those checks together. The product is designed to make collection and review easier while leaving scope, corroboration, interpretation, and every consequential decision with the researcher.

02 / Workflows

What the site actually checks

A returned card, a missing result, or an error is a system state to investigate—not a conclusion about a person or organization.

Username17 categories · 2,518 checks

Public-site presence checks

The browser can run up to four /api/scan category lanes concurrently. Pages within each category remain sequential. As responses arrive, the workspace updates site, found, error, and page counts, marks completed categories, and keeps every returned site row available in the response log.

A matching handle may be shared, stale, copied, or unrelated to the subject.

Try username research
Email20 categories · 168 services

Account-context signals

The email workflow checks 168 configured account services across 20 categories and keeps registered, not-registered, unknown, and error responses distinct. Many checks rely on account-recovery behavior, so they may indicate registration without revealing a username, account ID, or profile URL.

It does not access an inbox, send mail, or prove who controls an address.

Try email research
03 / Product facts

A bounded description of the service

Coverage depends on source availability, provider behavior, and the selected workflow. Category, check, and service counts describe configured coverage—not a promise that every source will respond or that every possible account will be found.

Delivery
Browser-based research interface; no local toolkit installation is required.
Data origins
Weighted scan API endpoints selected independently for each request, plus the public-source account services represented in their category responses.
Response log
Every returned site row is shown, including negative, unknown, and error states. Per-category site, found, error, and page totals are calculated in the browser from paginated API responses. Progress closes at 100% when the API reports that no next page remains.
Scope
The current interface does not add Worker-based site batches, indexed web-search panels, AI lead generation, AI summaries, or target-IP lookup.
History
In standard mode, positive results can be associated with the current browser identifier or connected Google profile. Privacy Mode skips application task creation and history storage, while the configured scan service still receives the query. Individual tasks and the current application account can be permanently deleted from the user workspace.
04 / Interpretation

Results are leads, not proof

Public profiles can be copied, usernames can be reused, and provider data can be stale. A missing result can also reflect a blocked request, rate limit, changed page, or unavailable service.

Open material sources, compare dates and context, look for independent corroboration, and record uncertainty before relying on a finding.

Read how results are produced
Working principles
  • 01

    Authorized scope

    Research only identifiers and systems you have a legitimate basis to investigate.

  • 02

    Minimum necessary data

    Submit and retain only what the question requires.

  • 03

    Source-first verification

    Treat summaries and result cards as navigation aids, not final evidence.

Corrections & feedback

Report a source, product, or privacy issue.

Include the affected URL, what appears wrong, and only the minimum context needed to review it.

Contact the team