footprint / history / diff between runs
Reverse username lookup
A reverse username lookup starts from a handle and lists every public profile that uses it. UsernameLookup checks 300+ public sites, saves the footprint, and on the next run shows what is new, what is gone and what stayed the same.
Why start from the handle
Most people search tools work forward: you know who you are looking for and try to find their accounts. A reverse lookup works the other way. The only thing you hold is a handle, seen in a review, a chargeback note, a scam message or a list of signups, and you want to understand where that handle lives in public.
That footprint answers practical questions. Is this a long established handle with profiles across code, video and forums, or a fresh name that appears on one marketplace only? Does it cluster around one niche, such as gaming or crypto? Are the profiles linked to each other, which suggests one operator?
A footprint is a snapshot, though. The second half of the story is change over time, which is why every run is kept and compared.
- social 4
- video 2
- dev 3
- gaming 1
- forums 3
- marketplaces 1
Example footprint by category. A real run lists each profile with its link.
The diff between two runs
Run the same handle next week and the result is compared with the previous run site by site. You do not have to read two long lists and spot the difference yourself. The changes are marked for you.
A new profile can mean a fresh account, a moved community or an impersonator. A profile that is gone may have been deleted, renamed or suspended. Unchanged rows confirm what is stable.
+ new kick.com/quietharbor found
+ new bsky.app/profile/quietharbor found
- gone twitter.com/quietharbor was found, now free
= unchanged github.com/quietharbor found
= unchanged reddit.com/user/quietharbor found
? unknown snapchat.com/add/quietharbor no clear answerWhat each run keeps for every site
A footprint is only useful later if it records enough detail to compare. These are the fields saved with every lookup and included in the CSV export.
| Field | Example | Why you need it |
|---|---|---|
| site and category | GitHub, dev | Group the footprint and filter it by type |
| state | found, free, unknown | The basis of every diff between runs |
| profile link | github.com/quietharbor | Open the public page in one click |
| response time | 342 ms | Spot slow or blocked sites that may need a recheck |
| first seen | date of the first run that found it | Tell an old profile from a newly created one |
Deleting a saved lookup removes it from history, it does not give back any monthly quota.
A simple reverse lookup routine
Run the handle once
Get the baseline footprint. Read the found profiles and note which categories the handle lives in.
Run it again later
After a week or after an incident, search the same handle. The diff shows new, gone and unchanged sites at a glance.
Hand it over
Export the CSV for your team, or let monitoring run the handle for you on a schedule and alert you when something new appears.
If you mainly need the list of profiles with a likely same person score, see find social media accounts by username. For many handles at once with case notes, read about OSINT username search. To check footprints from your own software, the username lookup API returns the same fields as JSON.
Public footprint only
A reverse lookup reads the same public profile pages anyone can open without logging in. It does not reach private accounts, messages or anything behind a login, and it does not claim to know who runs a profile. People who want a public profile excluded can request it on the opt-out page.
Your first search is a one-time demo with the first 8 found sites visible. History, diff and CSV export come with every paid plan, from $24 a month billed yearly. See pricing.
- Pro
- 300
- Investigator
- 2,000
- Brand Monitoring
- 10,000
- Brand Enterprise
- 50,000
Questions about reverse username lookup
What is a reverse username lookup?
It is a search that starts from a username instead of a name or an email address. You enter the handle and get back every public site where a profile with that handle answers, which together form the public footprint of the handle.
How does the history between runs work?
Every lookup is saved in your account. When you search the same handle again, the new result is compared with the previous one and each site is marked as new, gone or unchanged, so you see what moved since the last run.
Can I export the footprint?
Yes. Pro and higher plans export any result as CSV with the site, category, state, profile link, response time and first seen date. Investigator adds a PDF report with evidence snapshots.
Does a reverse username lookup reveal who owns an account?
No. It lists public profiles that use the handle and how strongly they connect to each other. It does not identify the person behind them, and it never reads private data.
Map the public footprint of a handle
Start from one username. See every public profile across 300+ sites, then compare runs to see what changed.