Methodology
How we test, what scans measure, and where they can't help
Last reviewed: October 2026 · maintained by the TruthsSeek field desk
What a username scan measures
A username scan answers one narrow question: does a public profile matching this exact handle exist on this platform, and is it active right now? It works because the handle is part of the profile URL on most platforms, so existence can be checked with a single request — no login, no insider data. TraceScan runs this check across 3,000+ platforms in parallel, completing a full sweep in 20–30 seconds.
How scan results are reported
Every platform check returns one of three states — and the difference matters: Found (a public profile matching the handle responded and is active), Not Found (the platform answered that no such public profile exists), and Unavailable (the platform could not be verified this round — rate limits, downtime or login walls; repeated briefly, then reported honestly rather than guessed). Repeated scans of the same handle within a short window may be served from a short-lived cache (up to 24 hours) instead of re-checking every platform; results older than that are re-verified live.
How we test claims on this site
- Hands-on first. Every method we publish was executed by us on real handles before it was written up.
- Named limits. Where a method breaks — login walls, soft 404s, handle truncation — we say so in the same section, not in a footnote.
- Facts dated. Coverage numbers and platform behaviors are stated with a last-verified month, and pages carry real update dates.
- No invented evidence. We never publish statistics, case studies or quotes we cannot verify. Where we cite known scam patterns, they're described qualitatively.
Where false matches come from
| Failure mode | What happens | Counter-move |
|---|---|---|
| Handle collision | Two unrelated people registered the same string on different platforms | Confirm a second signal: avatar, bio link, posting pattern |
| Stale cache | Instant tools show last month's data; the account since died or renamed | Use live scans; check status flags, not just existence |
| Impersonation | A near-copy profile deliberately mimics the target | Compare creation dates, follower graph, content continuity |
| Platform walls | Private or numeric-ID platforms hide membership entirely | Absence of a hit is never proof of absence |
| Variant blindness | The person uses truncated or modified handles elsewhere | Sweep separators, suffixes and truncations deliberately |
What a result can and cannot prove
Can: establish that a public identity exists under a handle today, describe its surface (bio, links, activity), and connect platforms where the same string and signals recur.
Cannot: prove two profiles share one human, see private content, or substitute for legal process. Treat every hit as a hypothesis until an independent second signal agrees — this rule is in every guide we publish, because it's the one readers most want to skip.
Sources we rely on
- Each platform's own public behavior — profile URL patterns, search features and privacy defaults, tested directly.
- The App Store and Google Play listings for current app capabilities, pricing and privacy details.
- Our own scan outputs, re-run before publication on the handles discussed.
- The platform directory and /find/ guides, re-verified as platforms change their rules.
Corrections
Platforms change rules constantly; a guide that was exact in March may drift by autumn. Pages carry their last-updated date, and material corrections update both the page and the date. Facts on this site were last verified in full in October 2026.
Ready to look someone up?
See what a username reveals
TraceScan searches 3,000+ platforms in 20–30 seconds and surfaces publicly accessible profiles matching a handle. Free first scan — no account, no card.
⬇︎ Download for iOS ⬇︎ Get it on Android
Works on iPhone & Android · 20–30 second scan · 3,000+ platforms