Guide / Result accuracy
Interpret Username Search Results
Version 3.1 is not available yet. This page accompanies a prelaunch preview. Check the App version you actually have for its controls and purchase access.
A field guide to public profiles, Not Found, Blocked, Unknown, and Source Conflict—including what each status cannot prove. This guidance is about public-source research methods. Check the App version you installed for its actual interface and purchase access.
Read a match as a lead
A website response can suggest that a public profile exists at a username URL. It does not identify the person behind that page. Open the original URL and check that it is a profile, not a generic landing page, redirect or error template.
Separate absence from uncertainty
No result from one check is not proof that the handle is free or that a person has no account. A request can be blocked, time out or receive a changed response. Keep these states distinct instead of converting them into a simple absent count.
Look for conflicts
If a rule reports a match but the public page looks unrelated, preserve the conflict and review it manually. Pages can be stale, reassigned or copied. A higher count of matches or checked sites is not automatically better evidence.
Document what matters
Record the source URL, observation date, site behavior and why the lead is relevant to your authorized question. Avoid collecting unrelated posts, private data or credentials. Explain uncertainty wherever you share a finding.
Next step
Read the method and limitations to interpret a lead, or contact support if a result or purchase needs help.