WhatsMyNameAppA practical place to follow public clues.
A research question often begins with a username or email address. Checking sources one at a time can make it difficult to keep track of a match, a failed request, or the context behind a returned value.
WhatsMyName App brings those observations into a browser-based workspace: possible account cards, related public clues, and a category-by-category response log. The researcher remains responsible for the scope, interpretation, and verification of every finding.
A useful starting point for research. A returned signal alone cannot establish identity, account ownership, intent, or wrongdoing.
Two ways to start exploring.
Username research
Look for public accounts using an exact handle. Positive responses can also supply possible names and email clues through their extra fields.
Email registration signals
Check whether sources report a registration signal for a complete email address. A source may report a signal without returning a username or public profile.
Coverage describes configured checks. Sources can change, block requests, or become unavailable, so a configured count does not guarantee that every check will succeed.
From one identifier to a reviewable result.
The username and email tools use the same research flow, with separate input rules and positive-status classifications.
- 01
Enter
Submit an exact username without spaces, up to 100 characters, or a complete email address.
- 02
Check
The browser trims the input and applies the format rules for the selected tool.
- 03
Scan
The scan service receives the identifier and checks one category and page at a time.
- 04
Collect
Every returned row stays in the live log, including negative, skipped, unknown, and error responses.
- 05
Organize
Exact positive states become possible-match cards, deduplicated by source name and URL.
- 06
Verify
Open the original source, compare independent details, and keep uncertainty in your conclusion.
Progress, pages, and controls
Username scans can process up to 4 categories concurrently; email categories are checked sequentially. Pages within a category remain sequential. Where several scan endpoints are configured, each request uses a weighted selection from that configuration.
Progress follows the number of modules reported by the scan service. It stays below 100% while requests remain and reaches 100% when the run ends. A category can finish with an error, so completion measures the end of the workflow rather than the success of every source.
Pause holds further requests while an active request may still finish. Restart begins a new run and ignores late responses from the earlier run. Failed pages are shown in the log; the browser does not silently turn a failed check into a negative result or automatically retry it.
Read the status before drawing a conclusion.
Swipe to read the full table
| Response | What the workspace does | How to read it |
|---|---|---|
| FoundUsername | Creates a possible-account card and keeps the row in the log. | A candidate source response, requiring verification of the actual page and its owner. |
| RegisteredEmail | Creates a registration-signal card and keeps the row in the log. | A registration-style observation. It does not establish a data breach, mailbox access, or who controls the address. |
| Not found / Not registered | Preserves the negative response in the live log. | A negative observation from that check at that time, not proof of permanent absence. |
| Unknown / Skipped | Keeps the returned status and any explanation in the log. | The check did not meet the exact positive rule. Read the reason before interpreting it. |
| Error / Timeout | Shows the unsuccessful response or request error. | An unresolved check, with no reliable conclusion about account existence. |
Extra fields and related clues
For username results, the workspace extracts possible names and email addresses from positive rows when those fields are available. Values are grouped with their sources and may include aliases, unrelated names, or automated email addresses. Source links, favicons, cards, and visual similarities do not independently verify a person's identity.
Keep incomplete checks in context.
Public services control their own routes, account-recovery behavior, regional restrictions, rate limits, and anti-automation systems. Shared scan infrastructure can encounter HTTP 403 responses, CAPTCHAs, temporary blocks, or timeouts. A missing match can describe those conditions rather than an absent account.
- A reachable URL may be a login screen, generic page, or soft 404; inspect its content.
- Private, renamed, deleted, or dynamically rendered profiles may be missed.
- People can share, reuse, copy, or impersonate a username. Corroborate with independent details.
- Results can differ by time, network location, and source availability. Record that context when repeating research.
Use the original source as your primary evidence, the returned status and fields as supporting observations, and the workspace as a way to organize them. The current tools do not add AI summaries, web-search panels, inbox access, or credential verification.
Choose what becomes saved history.
Standard mode
A task is created before the scan. Positive matches can be saved as they arrive, and the task is marked complete when the run ends. The full live negative/error log is not saved as a set of positive matches.
Privacy mode
Enable it before scanning to skip task creation and saved history for that run. The scan service still receives the submitted identifier and the request information needed to perform its checks.
History belongs to the current browser visitor or connected account. Individual tasks and the account with all linked history can be permanently deleted through the account menu. Read the Privacy Policy for cookies, providers, and other data handling.
Help improve the next research trail.
For a false positive, a missing result, a broken source, or an outdated description, include the scan type, affected platform, approximate time, observed status, and the smallest public example needed to explain the issue.