WhatsMyNameOur purpose
WhatsMyName.me helps you collect leads for an investigation you are entitled to conduct. It brings public profile checks, email account signals, and available web references into a single browser workflow. The researcher remains responsible for deciding whether a lead is relevant.
Two research workflows
Username research
The configured scan API covers 2,539 sites in 17 categories. Additional checks use bundled public-site rules. These catalogs can overlap; their counts do not represent a combined unique total.
Email research
The configured email API covers 220 sites in 20 categories. Results indicate whether a service appears to recognise an address; they do not confirm a breach, mailbox access, or the identity of its owner.
How a scan works
- Validate the input and prepare the configured categories and site rules. Some local username rules depend on the browser language.
- Send username checks to the checker and category API; send email checks to the email category API. The browser displays progress and source responses as they arrive.
- Interpret available status codes, response text, and provider status fields. Public-page checks do not execute a target page’s JavaScript.
- Combine matching results, reduce duplicates, and show source links or platform homepages. Available public-web references appear separately.
- Review the original source and scan log before treating a result as evidence.
Timeout and retry boundary: the browser does not set a dedicated scan-API request timeout. If a category page encounters a network or HTTP error, it tries the remaining configured API endpoints by weight, at most once per endpoint for that page. Invalid JSON and unsuccessful business responses do not trigger failover. Once all endpoints fail, the category is recorded as a partial error and other categories continue when possible. The separate Radar IP request has an enforced ten-second cURL timeout.
Read the result, then verify it
A positive card means a configured check returned a matching signal. A negative means the check did not confirm one. Unknown and error responses remain inconclusive. A displayed confidence value can reflect a rule match; it is not a calibrated probability of identity.
- 403/429 responses, IP controls, rate limits, CAPTCHA, JavaScript-only pages, changed rules, and outages can hide an existing account.
- A reused username, generic response, redirect, or stale source can produce a misleading match. No overall accuracy percentage is claimed.
Why some profile links are unavailable
Many email checks use registration or password-recovery responses to determine whether an address is recognised. That response usually does not reveal a username or user ID, so a profile URL cannot be constructed. View may lead to the platform homepage for further research.
Names, emails, and other details extracted from a username result are clues requiring corroboration; matching text alone does not connect two accounts to the same person.
History, privacy, and web context
Privacy Mode prevents the scan from being added to this site’s search history. It does not make requests anonymous or prevent processing by scan services, public websites, analytics, or advertising services. Public-web results may still be cached for seven days.
History can be linked to a browser identifier before Google is connected. Public-web search depends on availability and country rules. AI Search Results and AI Summary are currently disabled in the public interface.
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 searches of Google's index do not affect scan progress or establish account ownership. You can inspect and copy each generated query before opening it.
Use the service responsibly
Use the smallest amount of data needed and keep source URLs, dates, and context with important findings. Do not infer ownership, intent, wrongdoing, or a person’s location from a handle or email signal. Do not use an unverified result alone for decisions affecting someone’s rights or opportunities.
Sources and corrections
This hosted service combines local rule definitions and external services. Referenced platforms and project names belong to their owners; a mention does not imply endorsement. We make no claim to operate those platforms or to be their official representative.
Report a broken check or inaccurate description with the platform, approximate time, observed status, and a safe public example. Source behavior changes, and corrections need enough context to reproduce the issue.