Documentation

How to use the web interface responsibly.

This documentation reflects the current official WhatsMyName product: a browser-based username search that returns source responses for manual OSINT review.

Open the search tool

Basic workflow

1. Enter a handle

Start with a public username, nickname, or handle. Avoid private secrets, passwords, personal tokens, or information unrelated to the public-source check.

2. Review responses

Results are grouped by source and status. A found result links to a public page that should be opened and reviewed before it is used in any report.

3. Document context

Record the username searched, source URL, snapshot timing, and why the result is relevant. Do not treat a username match as a confirmed identity.

Available controls

The interface is intentionally small so the review process remains understandable.

Search submits the current handle to the lookup service and returns source responses when available.

Rescan requests a fresh lookup. Use it when the snapshot is old or when a platform recently changed.

Found, Not found, and All filters help separate positive profile leads from negative responses.

Category filters use the local source catalog to group responses such as software development, gaming, community, finance, or media sources.

Safe Mode hides Adult-category responses from default result views. It is a frontend visibility default, not identity verification or a promise that the backend skipped those checks.

AI/crawler summary is available at https://whatsmyname.io/llms.txt for agents that need the official site URL, canonical pages, source-count limits, and contact details.

Limits and error handling

Some public sources rate limit, block automated requests, change URL patterns, or return ambiguous responses.

A not-found result can be a real negative response, a temporary failure, or a platform-specific parsing limitation.

A found result can be a coincidence when different people use the same handle on different platforms.

Free request limits may apply. If a limit message appears, wait for reset or narrow the search later.

Tips for more reliable results

A few habits make the tool noticeably more useful. They come from watching how careful researchers work versus how first-time users tend to rush.

Start exact, then vary. Run the precise handle first for a clean baseline before testing separators, numbers, or alternate spellings.
Filter before you read. Use the found and category filters to focus on the platforms that matter for your purpose, rather than scrolling the entire response set.
Open every lead you keep. The status label is a best guess. The live public page is the real evidence, so confirm it yourself.
Rescan when it counts. If a result will inform a decision, request a fresh lookup so you are not relying on a stale snapshot.
Treat negatives as information. A not-found result can mean a different spelling is needed, or that a lead should be dropped.

For the full evaluation method, including how to judge whether a match is strong or weak, see the username search guide. To understand how the found and not-found labels are produced, read how it works.

Frequently asked questions

Do I need an account to use the tool?

No. The search runs in your browser without sign-up. Daily request limits keep the free service stable for everyone.

What does the rescan button do?

Rescan asks the service for a fresh lookup instead of reusing a stored snapshot. Use it when a result matters and you want the current state of a public page.

Why did I see a request-limit message?

Free usage is capped per day to keep the service available. Limits reset automatically, so you can return later or narrow your search to the handles that matter most.

Questions about a specific use case?

This page documents the public web interface: the browser search experience and the supporting methodology pages. If your use case is not covered here, the publisher is happy to help.

Contact