Can the code of your .exe be recovered?
Drop the executable (.exe, .dll), the Access database or the .jar of your application here. In a few seconds we tell you which technology it is built with and how likely it is that its business logic can be recovered.
The analysis runs in your browser. The file is not uploaded to any server and never leaves your computer.
What it detects
.NET Framework and modern .NET
Framework version, whether it is WinForms, WPF, ASP.NET or WCF, which database it uses and whether it is obfuscated.
Visual Basic 5 and 6
Applications that depend on the VB runtime, whose development environment has been unsupported for years.
Delphi and C++Builder
Desktop applications compiled with Borland or Embarcadero tools.
Visual FoxPro and PowerBuilder
Classic business applications and their data tables (.dbf).
Access, SQLite and Java
.mdb and .accdb databases, SQLite files and .jar applications.
Native, packed and protected
C/C++, Go, compressed executables (UPX) or ones protected against analysis.
How it works
1. Pick the file
The main .exe or .dll of the application, or its database.
2. Header reading
We read the internal structure of the file, the libraries it uses and its compiler markers. Nothing is executed.
3. Estimate
We show the detected technology and a recovery estimate: high, medium or low.
4. Next step
If you want, we help you confirm it in a free first consultation.
This is an automatic estimate based on the file structure. It can be wrong with uncommon applications and does not replace an assessment. Use it only on software you own or have the right to analyse.
Frequently asked questions
Is my file uploaded anywhere?
No. The analysis runs entirely in your browser with JavaScript. The file is not sent to any server, so you can use it even with internal applications.
What does "high recovery" mean?
That, given the detected technology, most of the business logic can probably be recovered from the executable, as with most unobfuscated .NET or Java applications. It is not the identical original code (comments and some names are lost), but it is its behaviour.
What if it says "low recovery"?
It does not mean there is no solution. For native or protected applications, the usual approach is to reconstruct the logic from analysing the program, its behaviour and its database, and migrate it to current technology.
Which file should I analyse?
The main executable of the application (usually in the Program Files folder) or the DLL holding the logic. If it is an installer, install it first and analyse the program it leaves installed.
Is it legal to analyse an executable?
Analysing the structure of a file you own changes nothing. Recovering or modifying the code depends on who owns the software and on its licence; we review it with you before any work. This does not replace legal advice.
Contact
Email: jmoreno@stellariscode.com · Phone: +34 654 51 63 65