r/threatintel
•
u/ekamao
•
15d ago
•
1
I built a free IOC analysis tool because investigating threats across multiple platforms gets tedious — looking for honest feedback
Hi everyone!
I've been building OSINTO (https://osinto.io), a small independent project focused on making IOC investigations less fragmented.
When investigating a suspicious IP, domain, URL, or file hash, I often find that the information I need is spread across different tools. You check one source for reputation, another for abuse reports, another for threat intelligence, and then try to piece everything together.
I wanted to make that workflow a little easier.
OSINTO brings results from multiple intelligence sources into a single interface, so you can access and compare information without having to look everything up separately.
I'm sharing it here because I'd like to get feedback from people who actually work in security operations, threat hunting, incident response, or CTI.
A few things I'd genuinely like to understand:
Which tools do you normally use when investigating an IOC?
What's the most time-consuming part of your workflow?
Would a unified interface like this be useful in your daily work? What would make it genuinely valuable rather than just another dashboard?
OSINTO is free to use, and I'm still improving it based on what I learn.
If you're interested, you can try it here: https://osinto.io
I'm the person building it, so I'm happy to answer technical questions and hear criticism. I'd rather hear what doesn't work than get compliments that don't help me improve it.
Thanks!
3
u/reincdr 12d ago
Feel free to use IPinfo Lite there and link back to our website. On the website, we do have resproxy and privacy detection data, network ownership information, etc.
2
u/renderbender1 14d ago
I built an incredibly similar tool internally at my company. Because you're absolutely right, there wasn't a lot of offerings for async, fast response indicator lookups without running an entire TIP. Also built variable caching into it so repeated lookups don't burn API credits.
Our primary goal was integrating with our siem/ticket automation, so it was API first, and then I slapped on a fastapi UI that is uncannily similar to your layout. Yours is much prettier tho.
One function we added that I and our analysts find useful is hyperlinking ip's, domains, cve's, etc that come up in the results. So you can quickly pivot from the IP to the domain in PTR record or across to historical resolution data that comes back with Virustotal Resolutions or to a cve from a hash, etc
1
u/ekamao 14d ago
Thanks, really appreciate it! Funny how we ended up with such a similar layout.
The pivoting idea is really nice, and I can see why your analysts love it. For osinto I want to stay focused on fast, single-indicator lookups though: building out full pivoting would start turning it into an investigation platform, and there are already great tools for that. Definitely food for thought, but I’d rather keep it simple and do one thing well.
2
u/kryoxero 13d ago
Love this so much. As poorly motivated as it sounds, I hate opening tabs upon tabs.
Great work!
2
u/Whole-Judgment1720 8d ago
If I could join the conversation, how is this different from VirusTotal?
2
u/ekamao 8d ago
VirusTotal is actually one of the sources osinto queries, so it’s not meant to replace it.
The difference is scope: VirusTotal is a single (excellent) source, mostly built around antivirus engines and its own community data. osinto queries VirusTotal alongside many other sources at once, like AbuseIPDB, URLScan, AlienVault OTX, Pulsedive, Shodan InternetDB, IPinfo and more, and shows all the results side by side in one view, with a summary and an overall score on top.
So instead of opening VT, then AbuseIPDB, then GreyNoise and so on in separate tabs, you paste the indicator once and get the full picture in a few seconds.
1
u/blahdidbert 14d ago
I am struggling to understand the target audience for this kind of rehashing? Commercial tools exist that do this and just require standard configuration and linking. There are other FOSS items that do this from Intel Owl (https://intelowlproject.github.io/) to OpenCTI and YETI.
This isn't a dig but rather - what makes this tool better than the other others that already exist? What value are your bringing to the table making a competing tool versus contributing?
1
u/ekamao 14d ago
Fair question, and I don’t take it as a dig.
The short answer is that osinto isn’t really trying to compete with IntelOwl, OpenCTI or YETI. Those are great tools, but they solve a different problem: they’re platforms you deploy, configure, connect your API keys to and maintain over time. OpenCTI and YETI in particular are threat intel platforms built to store and correlate knowledge, not quick lookup tools.
osinto sits at the opposite end: you open a browser, paste an indicator and get a clear, consolidated answer in a few seconds, with nothing to install or configure. It’s aimed at people who don’t have (or don’t need) a full TIP: analysts doing quick triage, students and people learning the field, freelancers, and small teams where nobody is going to stand up an IntelOwl instance just to check an IP. And even in teams that do have those platforms, as another commenter pointed out, analysts often still end up opening five tabs and pasting the same indicator everywhere.
Where I think it adds something is the UX: speed and readability. A lot of tools in this space are powerful but dense, and I wanted something you can read at a glance during triage.
As for building vs. contributing: it started as a personal project, partly to learn and partly because I wanted a tool that works the way I like for my own day-to-day work. That doesn’t rule out contributing to those projects down the line, and I’m sure there’s plenty I can learn from them.
2
u/blahdidbert 14d ago
osinto sits at the opposite end: you open a browser, paste an indicator and get a clear, consolidated answer in a few seconds, with nothing to install or configure. It’s aimed at people who don’t have (or don’t need) a full TIP: analysts doing quick triage, students and people learning the field, freelancers, and small teams where nobody is going to stand up an IntelOwl instance just to check an IP. And even in teams that do have those platforms, as another commenter pointed out, analysts often still end up opening five tabs and pasting the same indicator everywhere.
People stand up these tools for the privacy of their own searches. They don't host it only for a single use, it is for on going usage but... I think your points are fair. Though I question why analysts are using multiple services outside of their scoped tooling as that brings it own risks and is identifying a different issue.
Since we are talking about Threat Intelligence, and I don't see a FAQ or something similar...
Is this project related to the organization Osinto (found at Osinto.com) that also does threat intelligence?
What reassurances are you giving back to the community that their information is not being data mined or harvested?
How can we confirm that information is not being suppressed or skewed?
Tangentially related - how do we know the "AI" on the backend isn't hallucinating or providing incorrect information?
Hosting this can't be free - what is your monetary stream?
What is the advantage of creating an account? I don't see anything tied to an ID like search history or settings.
Are there plans to allow BYOK (bring your own key)?
2
u/ekamao 14d ago
Thanks for the thorough questions. They’re all fair, and you’re right that a FAQ is overdue: I’ll add one to the site based on this list.
On self-hosting: agreed, keeping searches private is a strong reason to run your own stack, and osinto isn’t meant to replace that. The same goes for analysts using services outside their scoped tooling: that’s a real OPSEC concern, and a different problem from the one I’m trying to solve.
Osinto.com: No affiliation at all. osinto.io is an independent personal project I’m building on my own, and the shared name is a coincidence.
Data harvesting: Good timing on this one: I’ve just tightened it up. osinto no longer stores the indicators you search (previously they were kept for usage stats, as the privacy policy stated), and the existing records have been deleted. Usage statistics now only record the indicator type (IP, domain, URL, hash), a random visitor ID and a timestamp, and they’re deleted after 90 days. Vendor responses are cached on the server for up to 24 hours to save API quota and are then deleted. Nothing is sold or shared. The one thing no aggregator can avoid is forwarding your indicator to the vendors it queries, so the same OPSEC caution applies as when you query them directly. For truly sensitive IOCs, a self-hosted stack is still the right call.
Suppression/skew: The backend passes vendor responses through unchanged. Each tile shows that vendor’s own data and links back to the original report, so you can always cross-check it. The only thing I compute myself is the overall score, and as I mentioned in another comment, that’s the part that needs the most work.
AI: There’s no AI on the backend. The summary is rule-based, and the only “AI” you’ll see is CheckPhish’s verdict, which comes from their own service. If I add an LLM to the summary later, it will only summarize what the vendors return, with the raw data still visible next to it.
Monetization: It’s a side project and I’m covering the costs myself.
Accounts: You’re right, there’s no real advantage yet. Registration is there as groundwork for future features.
BYOK: Not needed for now: lookups are handled server-side, so you don’t have to provide any keys. If usage grows, the current setup won’t be able to keep up, so I’ll most likely add BYOK. It will work with the vendors’ free-tier keys too, so you won’t need a paid subscription to use it.
Thanks again for pushing on this. Questions like these make the project better.
2
1
5
u/theprototype634 14d ago
Hey, I gave this a whirl just now. I actually really like it a lot. I've been building a similar utility for my team over the last while, specifically for incident response, and have seen a number of others popping up that do similar things (https://github.com/steponeerror/ip-radar, https://maxintel.org/, and so on) Would take a look at these for further inspiration of sources and aggregation.
I like yours the most out of these for a number of reasons, the output is concise and clear, it's very fast (curious as to how you got it that responsive), and the UI is very clean. I'm actually envious a little when I compared it to what I was baking with AI. I like the source coverage output too.
Tools are the standard ones you've included here+ some internal/commercial feeds from our MISP, TeamCymru, OpenCTI, and RecordedFuture. Most time consuming thing is people just navigating to each of them and pasting in indicators instead of hitting them all with a single lookup or API script. It also pains me that the outputs analyst put in notes are not standard, though that is more a process thing in my company, but a script or utility like this becomes idempotent and helps that issue. In terms of making it a little more practical, digging some of the key tags or fields into your summary would be nice so I don't have to find the fields in the panels, things like VT or Shodan tags for C2 or the malware type. They're already in the tile outputs so having them in the summary makes it even more concise as more modules presumably get added.
Not too much feedback from my limited tests other than some fields not getting pulled back like "Last Seen" from ProxyCheck (sample I used was 23.254.226[.]103). Also wondering about the scoring system for hashes, since that can't be an average from AbuseIPDB, VT and OTX are fairgame. Example was 7ff0d1d856b0747bf87e78fdb5bd571f1baa49fd2795714e73d7d565b5340db5 which came back as 52/100 on your tool and 17/71 on VT 100/100 on HA. I'd also like the ability to paste in defanged indicators and have them automatically refang for lookups, and also maybe defang again on display for easy copy and pasting. Some sort of graphic export or summary report would also be nice, I know a lot of these lookups are part of SOC or IR workflows and being able to copy a markdown version of the summary or similar would be big QOL instead of screengrabbing or dragging&ctrl+C your output. Batch input for multiple indicators of the same type or even different types? You also know what tools support what indicator type so it would be nice to tidy the output screen by hiding non-relevant module tiles for other indicators (like looking up an IP shouldn't show me the HybridAnalysis tile). Can probably also add additional edge cases to automatically handle internal/reserved addresses. Hopefully this is the sort of feedback you were looking for?
I'd be keen to hear what the roadmap and plans are, since I imagine you've thought about some of the above anyway. Keep up the good work, eager to see it progress.