Why I built a breach lookup tool that shows where every result came from

OSINT Pro — Fri, 16 Oct 2026 07:50:41 GMT

Most breach search sites give you a pile of rows and leave you guessing where they came from. That's fine until you need to act on it. If you're scoping an incident or deciding which passwords to rotate, you want to know if a hit came from a 2016 forum dump or last month's stealer log.

So I built OSINT Pro (https://www.osintpro.dev).

You paste an identifier and it checks a bunch of sources at once. It covers 14 types: email, username, phone, full name, domain, IP, crypto address, Discord ID, Steam ID, MAC address, machine UUID, company, password (reverse lookup) and file hash.

Results get merged into one format, duplicates are dropped, and they're sorted newest first. Every row keeps the name of the source it came from. You can export to TXT, CSV or JSON, and the file header records the query and lookup type so you can trace a finding later.

Sources include breach aggregators like Snusbase, IntelX and LeakCheck, plus stealer log and dump collections. Public sources include crt.sh, RDAP, Team Cymru, Spamhaus DROP, the IEEE OUI registry, Sherlock, Maigret and others. Not every source is hit on every search.

Some honest limits. There's no API or monitoring yet. An empty result doesn't mean you're safe, it just means the sources checked didn't have it. Names aren't unique, so confirm a match with a second identifier.

It's meant for defensive and investigative work: checking your own or your company's exposure, scoping an incident, or confirming an identifier during an investigation. The acceptable use policy is at https://www.osintpro.dev/legal/acceptable-use and anyone can request removal at https://www.osintpro.dev/legal/removal.

You get one free full lookup. After that it's credits or a monthly plan.

If you try it, I'd like to hear what sources or lookup types you'd want added.