UsernameLink practical guides
How to check whether a public profile is the right match
A matching username is a useful lead, but it is not proof that two accounts belong to the same person. Follow the source links, record what you can actually see, and keep uncertain matches separate.
1. Start with a handle you can explain
Copy the username from a profile or message the owner shared with you. Record where you got it. A display name such as “River Stone” can be different from the account handle, such as “riverstone_dev.” Keep dots, underscores, and hyphens in your notes; similar spelling is a separate lead, not an automatic match.
UsernameLink accepts a handle without @ and normalizes the search to lowercase. The original platform's page is the place to check the displayed spelling and its username rules. Do not turn an AI-suggested alternate handle into an established connection without further evidence.
2. Open the original page, not just the summary
Read the full address before opening a link. Check the platform's domain and the visible account handle, rather than trusting a familiar title or avatar. A search result can point to a post, a mention of the handle, or an old page instead of the current profile.
Use a browser window signed out of that platform to see what is publicly readable. This is a visibility check, not a promise of anonymity. If you meet a login wall, a private profile, or an error, record that limitation. It does not establish that an account is absent. Do not bypass access controls to fill the gap.
3. Prefer direct cross-links to resemblance
A link from an owner's known website to a profile is more useful than the same photograph appearing twice. Look for the exact destination URL. A link back to the same website adds context, although neither link is an identity document or a guarantee that an account remains under the same control.
A repeated full name, location, biography, or avatar can support a hypothesis, but each can be shared, copied, or outdated. Several weak similarities do not become a direct ownership statement. Where the connection matters, ask through an already trusted contact channel whether that specific URL is theirs.
A worked example: three similar profiles
Suppose a designer gives you their portfolio, and it links directly to a code profile named “riverstone_dev.” A photo-sharing account has the same handle and avatar, but no cross-link. A forum account has a similar name and a conflicting biography. These are fictional examples, not claims about real accounts.
| Candidate | Observation | Conclusion |
|---|---|---|
| Code profile | Known portfolio links to its exact URL | Directly linked by the known source |
| Photo profile | Same handle and avatar only | Possible; ownership unresolved |
| Forum profile | Similar handle, conflicting context | Do not combine with the others |
The useful output is three separate assessments. A single merged biography would hide the uncertainty and could attach someone else's statements to the designer.
4. Keep a short evidence worksheet
For each candidate, write down:
- The full source URL and the date you opened it.
- The visible handle and whether the profile was readable while signed out.
- The exact cross-link or statement supporting the connection.
- Any conflicting details, access limits, or unresolved questions.
Keep observations separate from interpretations: “the portfolio links here” is an observation; “every account with this name is theirs” is an inference. A stored search or an AI summary can be older than the live page. When they disagree, revisit the source and leave the claim unresolved if you cannot explain the difference.
5. Use the result proportionately
Public profile discovery can help you check a shared account or review your own presence. It is not identity verification for consequential decisions. Do not publish a dossier, contact a person repeatedly, or use an uncertain match to accuse them. If the check has no clear purpose or consent, stop rather than collecting more information.