> For the complete documentation index, see [llms.txt](https://docs.whatsmynameapps.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whatsmynameapps.us/osint-username-search.md).

# OSINT Username Search

**Open-source intelligence (OSINT)** uses lawfully accessible public information to answer a defined research question. Username enumeration can help identify public profile leads.

## Investigation checklist

1. Define a legitimate purpose and the username you are checking.
2. Run an [OSINT username search](https://whatsmynameapps.us/osint-username-search/).
3. Review matches, non-matches, and blocked or unknown statuses separately.
4. Verify important findings directly on the original websites.
5. Keep source URLs and a date for each observation.
6. Distinguish verified facts from hypotheses in your notes.

## Limits

Automated profile checks can produce false positives and false negatives. Similar handles, abandoned accounts, impersonation, and blocked requests can all affect interpretation. Do not use the results to harass, impersonate, or expose private individuals.

Related guide: [reverse username lookup](/reverse-username-lookup.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.whatsmynameapps.us/osint-username-search.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.