MyRecon OSINT
Founder

Aryan Walia

Penetration tester · Founder, BugSnaps & MyRecon · @4ryanwalia

I build tools that refuse to guess. MyRecon started as a side effect of offensive security work — the same discipline that stops you writing an unverified finding into a penetration test report is what this platform is built around.

BugSnaps

I founded BugSnaps, a penetration testing and offensive security practice that helps growing businesses find and eliminate vulnerabilities before attackers do. The work covers application and infrastructure testing against the OWASP methodology, with remediation guidance that a development team can actually act on rather than a PDF of raw scanner output.

Most security reports fail in the same place: they list findings without evidence, or list possibilities as though they were confirmed. A client cannot prioritise a report like that, and after the second false alarm they stop reading it. Everything I build is shaped by that problem.

Credentials

Why MyRecon exists

Mapping an organisation's attack surface and mapping a person's public footprint are the same exercise with a different subject. You enumerate what is reachable, verify what is real, and discard what only looks like a finding. The third step is the one almost every OSINT tool skips.

Run a username through most tools in this category and you get a wall of green ticks. Click a few and you find pages saying the account is not there. That is not a small annoyance — it makes the entire output unusable, because if you cannot tell which results are real you have to check all of them by hand, and at that point the tool has saved you nothing.

So MyRecon is built the other way round. It reports what it can support, at the confidence it can support it, and says plainly when it does not know. It shows you the platforms it checked and could not confirm, with the reason each one gave — because "we checked 112 sites and none of them were yours" is a stronger statement than silence, and it is the only way you can tell a thorough scan from a lazy one.

How the work gets done

Measurement, not assumption. When we test whether a platform can be checked reliably, we request a handle we know is real and a string of nonsense nobody could have registered, and compare the responses byte for byte. Several well-known platforms return literally identical pages for both. Those get labelled honestly or excluded — never counted, because a bigger platform number that is partly fictional is worth less than a smaller one that is true.

That research is published rather than kept as a competitive advantage, because the failure mode it describes affects every tool in this category including ours:

What I've built here

MyRecon on the web — username, email, domain, DNS and IP investigation from documented public sources, with breach exposure and password checking that hashes in your browser so the password itself never leaves your device.

MyRecon for Android — the username sweep running on your own handset across 280+ platforms, which produces better results than a server can: platforms block datacentre address ranges far more aggressively than phones. It also watches for newly published breaches by downloading the public catalogue and comparing it locally, so no address is sent anywhere.

Footprint removal — where the tools stop being enough and someone has to do the tedious part: finding everything, verifying it, and working through the removal requests.

Reach me

I use the handle 4ryanwalia on most platforms. Email is the reliable route:

aryan@bugsnaps.in GitHub HackerOne BugSnaps

Happy to hear about a result you think is wrong — those are the useful messages. If a platform reports something MyRecon missed, or reports one that isn't real, tell me and I will measure it.

← About MyRecon