Vet a report
Run the username, email or phone behind a report and see the public profiles and history tied to it.
For trust & safety
Context on a reported account, in minutes.
When an account is reported, check the public footprint behind its identifiers and whether they turn up in leaked data, then document the decision your team actually made.
How it comes together
Reported accountHandle · email
Breach & stealerLeaked-data signal
Linked identitiesThrowaway accounts
ReviewDocumented & auditable
What you can do
Leaked-data signal
See whether an identifier appears in breach data or stealer logs, a common thread behind throwaway abuse accounts.
Link throwaways
Correlation ties repeat registrations, shared devices and reused contacts into one picture.
Document the call
Export the sources behind a decision so a later appeal or audit sees exactly what you saw.
A typical workflow
Four steps from a single clue to something you can hand off.
- Open the report
Paste the identifier that came with the report: a handle, an email, a phone.
- Read the footprint
Public accounts, breach and stealer indicators, and linked identifiers come back in one view.
- Correlate
Map the account into a case to see the other identities that share its details.
- Record the decision
Keep the result and export it, so the review is reproducible later.
What Elyv checks for you
- Username, email & phonethe identifiers on a reported account
- Breach & stealer-log indicatorssignal behind abuse accounts
- Correlation graphties throwaway identities together
- History & exportan auditable record
Questions
Elyv reports what is already public or in the breach index. It does not de-anonymise people or decide policy; the call stays with your team.
Start from one clue.
Search a username, an email, a phone or a domain and see what public sources hold.
