A username lookup answers a limited question: did a tool find a candidate public profile for this handle? Establishing that a profile exists, determining who owns it, and measuring how reliably a tool finds profiles are separate tasks. Keep those conclusions separate when comparing tools or investigating a surprising result.
A web response is not enough evidence
A missing-page message can accompany a success status; see Google’s example.
Check the final URL, the requested handle and actual profile details. A page that loaded successfully may still fail to confirm the candidate. A redirect, generic landing page, access restriction or empty response needs review before you treat it as a match.
| Review category | What the evidence supports | Next action |
|---|---|---|
| Confirmed public profile | A visible profile matches the requested handle | Investigate ownership separately |
| Unconfirmed candidate | A result needs manual checking | Inspect the final URL and page |
| Access unavailable | The request did not establish a result | Keep it separate from absence |
| Known profile missed | An owner-confirmed public profile was not returned | Record the conditions and method |
These categories are an editorial review framework, not verified descriptions of any app’s internal status flags.
Compare correct matches and missed known profiles
Separate correct candidates from missed known profiles. Metric definitions explain this distinction.
A useful evaluation starts with a reference set you can verify. A list of unknown usernames cannot establish how many true profiles a tool missed. Counting every returned link as correct also hides false matches. An unavailable lookup should remain identified rather than silently becoming a negative result.
Platform coverage is a supported-platform count. It does not establish the number of confirmed accounts found or an identity-verification success rate.
Use a reproducible review checklist
This is a suggested protocol, not a completed benchmark:
- Use your own public profiles or consented, owner-confirmed profile links.
- Record the exact handle, platform, date and access conditions.
- Save the tool’s result and the final profile URL.
- Check each candidate manually; label unresolved cases as unconfirmed.
- Record known profiles that were missed and distinguish access restrictions.
- Publish the method and limitations alongside any resulting measurement.
Different samples, access conditions and definitions can produce different results. A comparison should disclose those choices rather than presenting an unexplained percentage as universal accuracy.
What TraceSeek’s figures establish
The product fact sheet states 3,000+ supported platforms, 20–30 seconds and a free first scan. These are product statements. TruthsSeek has not published an audited accuracy percentage or a complete validation of every supported platform.
Use a scan to collect candidates, then review the evidence. A confirmed handle can establish a public profile; it still does not establish that two profiles belong to the same person.