DeepIntel breach hits with source labels.
Breach database OSINT on OsintX answers a simple question with depth: has this email, username, IP, or domain appeared in public or semi-public leak corpora, and from which named sources? You are not guessing from a single combo file; hits arrive as labeled rows you can sort, export, and chain into stealer or game modules.
Each result ties the identifier to a breach or forum dump name, optional leak date, and exposure type (email only, password hash, plaintext password field when upstream allows). That lets you prioritize fresh 2024–2026 corpora over stale reposts before you spend time on manual verification.
What you can search
- Email addresses (primary breach pivot)
- Usernames and handles from gaming or corporate accounts
- IPv4 addresses seen in combo or forum leaks
- Domains for credential stuffing or customer record exposure
Typical hit cards
Password fields may appear hashed or plaintext depending on the upstream corpus; the UI still treats secrets carefully and masks where policy requires. After breach, run stealer on the same email to see live infostealer captures, or Roblox/FiveM if the username matches a gaming handle.
Volume investigators expect
Popular emails can return dozens of rows across sources. Filter by source name, export JSON for your case system, and use AI Analyzer on the export if you need a one-page brief for stakeholders.
- Dashboard: DeepIntel → Breach mode or unified Breaches category
- API v1: POST /api/v1/search with type breach and query set to email, username, IP, or domain
