About
An OSINT platform built with its community
OsintX.IO started in 2025 as a side project between two friends who wanted better tools and faster updates. This page explains how it came together and what we care about.
How it started
2025
The idea
A friend and I were using the existing OSINT tools every day. They were slow to change, support rarely answered, and feature requests went nowhere. So we talked about building our own, one that listens to the people who use it and ships updates often.
2025
The name
We wanted something short that says what it is. OSINT, plus an X for the pivots between sources. OsintX was free, and so was osintx.io, so we took both.
Today
Still small, still shipping
OsintX now covers breach data, stealer logs, Discord, Roblox, FiveM and more, with an AI Assistant, an MCP server and an API. New sources and fixes go out regularly, and most of them start as a message from a user.
What we care about
Community first
Roadmap items come from support tickets, Telegram and Discord. If many people ask for it, it moves up.
Regular updates
We prefer small releases every week over one big release every few months. The news channel lists every change.
Responsible use
OsintX is built for investigations, security work and support for authorities. Read our ethics policy before you search.
Honest data
Results show where they come from, passwords stay masked in the interface, and we remove personal data when a valid request reaches us.
What OsintX covers
Breach data
Search emails, usernames, domains and IPs across indexed breach sources, with source name and leak date on every row.
Stealer logs
Credential rows from infostealer corpora, plus a file explorer for the victim package when the upstream allows it.
Gaming and Discord
Roblox, FiveM and Discord lookups that connect a snowflake, a username or a Steam ID to profiles and history.
Social and geolocation
Username checks across platforms, TikTok profiles, and image based location and social matching.
IntelX exports
Stealer log exports parsed into counts and domain groups, so you can read them without opening raw files.
AI and automation
An AI Assistant, an AI Analyzer for exports, an MCP server for your editor, and API v1 for your own tools.
How we work
- 1
Ask
Users send requests through support tickets and Telegram. We read all of them.
- 2
Decide
Requests that many people repeat, or that fix a broken source, go first.
- 3
Ship
Small releases go out often. The news channel and the blog explain what changed.
- 4
Check
The status page shows source health, and results mark a miss as a miss.
Who uses it
- Trust and safety teams that handle gaming and Discord abuse
- Server admins who check ban evasion and alt accounts
- Security analysts who triage leaked credentials
- Researchers who need exports they can pin to a case
- Verified police and government staff, through the free access forms
Results are leads from indexed data. Verify them before you rely on them.
Questions or ideas
Talk to us on support, read the ethics policy, or browse the guides.