Do you keep what I search?
No. Revealer keeps no search history. Your account holds a counter of how many searches you have used this period, and nothing else about them. The terms you typed and the results you saw are not stored.
Reveal where you're exposed.Type a handle. 700+ modules answer.
Enter a username or email. Revealer checks it live against 700+ social, gaming, forum and developer modules and 186 email modules, then against known breach and stealer-log datasets. Hits land as each source replies.
- 700+
- username modules, checked live
- 186
- email modules, on email search
- Live
- results arrive as sources respond
Loading the search console
Same handle, four sites, not the same person every time.
Four of 700+ modules answered for the invented handle nightjar_dev. Each source returns its own display name, bio and outbound links. Revealer lays them out in one ledger so you can see which rows agree and which one only shares the handle.
Here three rows carry the same bio, and two of them link to the same site. The fourth has the handle stem, a different display name and nothing else. That is the row to check before you write anything down.
Search a handle you know| Source | Public handle | Display name | Bio | Link | Status |
|---|---|---|---|---|---|
| github.com | @nightjar-dev | Nightjar | Firmware, radios, the occasional teardown. | nightjar.example | confirmed |
| instagram.com | @nightjar.dev | Nightjar | Firmware, radios, the occasional teardown. | nightjar.example | confirmed |
| reddit.com | u/nightjar_dev | Nightjar | Firmware, radios, the occasional teardown. | none | lead |
| x.com | @nightjardev | N. Jar | none | none | name mismatch |
Where the email has already leaked, and what was in the record.
Breach Reveal reads partner breach datasets and stealer-log datasets and returns the source type, the date and the field types each record exposed. For [email protected] that is three records: which login, which site, which browser. Revealer never displays a password value, on any plan. The record says a password was present, and stops there.
Check an address you know| Source type | Dated | Login as seen | Exposed field types | Secret |
|---|---|---|---|---|
| Forum database | [email protected] | emailusernameip | none in record | |
| Infostealer log | ni••••••v | loginwebsitebrowser | none in record | |
| Combolist | [email protected] | emailpassword in record | •••••••• redacted |
Deep Search writes the finding and shows its work.
On Basic and up, Deep Search reads every row the sweep returned and writes a short report. Each claim carries a citation back to a row and a confidence value, so you can see what it leaned on and how hard.
It will tell you when it is not sure. The X account below is the kind of row it refuses to merge.
See plans from $12.99Report nightjar_dev4 rows in
Finding
The handle nightjar_dev most likely belongs to one person across GitHub, Instagram and Reddit. All three return the same bio sentence, and GitHub and Instagram both link out to nightjar.example, which is a stronger tie than the handle alone.
The X account @nightjardev shares the handle stem but returns the display name N. Jar, no bio and no link. There is not enough in the record to attach it to the other three. Treat it as a lead and verify by another route before you rely on it.
No email was searched in this run, so no breach or stealer-log rows contributed to this finding.
References
- [1]0.71confidence
github.com/nightjar-devinstagram.com/nightjar.dev
Same bio text and the same outbound domain on two independent sources.
- [2]0.44confidence
x.com/nightjardev
Handle stem only. Display name differs, no bio, no link. Not confirmed.
Before you sign up
Will I ever see a password?
No, on any plan. Breach and stealer-log records show the source, the date and which field types were exposed. Secret values are redacted before they reach the page. If a password was in a record, the record says so, and stops there.
Check a handle now.
Free on this page. No account. Nothing kept.
Free on this pageStarter $12.99/moBasic $29.99/mo adds AI Deep Search