Search the Community

Scant3r Scans all URLs with multiple HTTP Methods and content-types also, it tries to look for bugs with basic exploits from Headers and URL Parameters By chaining waybackurls or gau with Scant3r you will have more time to look into functions and get Easy bugs on the way and scant3r will help you write your own python script faster, you don’t need to configure http/threads/errors/options/etc…, just by writing the main function in your script (also you can import scant3r function for write an awesome script), you can run it in your terminal or access your script from api [hide][Hidden Content]]

An incredibly fast proxy checker & IP rotator with ease.proxy checker Feature Proxy IP rotator: Rotates your IP address for every specific request. Proxy checker: Check your proxy IP which is still alive. All HTTP/S methods are supported. HTTP & SOCKSv5 proxy protocols apply. All parameters & URIs are passed. Easy to use: You can just run it against your proxy file, and choose the action you want! Cross-platform: whether you are Windows, Linux, Mac, or even Raspberry Pi, you can run it very well. Changelog v0.9.3 6f9ad0e fix: Add err check for http.ResponseWriter.Write ef8f050 Bump docker/login-action from 1.12.0 to 1.13.0 [hide][Hidden Content]]

Reko (Swedish: “decent, obliging”) is a C# project containing a decompiler for machine code binaries. This project is freely available under the GNU General Public License. The project consists of front ends, the core decompiler engine, and back ends to help it achieve its goals. A command-line, a Windows GUI, and an ASP.NET front end exist at the time of writing. The decompiler engine receives inputs from the front ends in the form of either individual executable files or decompiler project files. Reko project files contain additional information about a binary file, helpful to the decompilation process or for formatting the output. The decompiler engine then proceeds to analyze the input binary. Reko has the ambition of supporting decompilation of various processor architectures and executable file formats with minimal user intervention. Reko consists of a central .NET assembly Reko.Decompiler.dll which contains the central core logic. Leaving aside the user interface for a moment, the Reko can at a glance be considered a pipeline. The first stage of the pipeline loads the executable we wish to decompile. Later stages perform different kinds of analyses, extracting information from the machine language where they can and aggregating it into structured information (such as Procedures and data types). The final stage is the output stage, where the source code is emitted into files. A central tenet is that Reko is extensible: wherever possible, we strive to avoid hard-coding knowledge about specific platforms, processors, or file formats in the core decompiler. Instead, such special knowledge is farmed out in separate assemblies. Examples: Reko.Arch.X86.dll – provides support for disassembling Intel X86 binaries. Reko.ImageLoaders.MzExe.dll – understands how to load MS-DOS executable files and all related formats Reko.ImageLoaders.Elf.dll – understands the ELF executable file format. Changelog v0.9.3 This is the last time Reko is released for .NET Framework and Mono. Future releases will be based on .NET Core and .NET 5 The release consists of minor feature enhancements and bug fixes. Initial support for IA-64 and v850 support Support for the MIL-STD-1750, XCore-200, CompactRisc, MCore and Hexagon architectures Rewrite Reko’s MemoryArea abstraction to support non-byte-oriented archictectures (like Cray YMP and MIL-STD-1750) As usual, more x86 rewriters (with thanks to @smx-smx) Improved Sparc, zSeries, and Risc-V disassemblers Fuse adjacent memory accesses x86 and GUI support for specifying separate architecture models. Unpacker script for Exepack 3.60 et al. Loader for preprocessed C headers, making it possible to use such headers as metafiles in Reko projects (with thanks to @ptomin) User-supplied labels (#987) Register Values dialog (#950) Support for the TekHex and LDM text file formats Support for Unicos binary executables. Support for PharLap DOS Extender executables (with thanks to @gbody) [hide][Hidden Content]]

What Findomain can do? It table gives you a idea why you should use findomain and what it can do for you. The domain used for the test was aol.com in the following BlackArch virtual machine: Host: KVM/QEMU (Standard PC (i440FX + PIIX, 1996) pc-i440fx-3.1) Kernel: 5.2.6-arch1-1-ARCH CPU: Intel (Skylake, IBRS) (4) @ 2.904GHz Memory: 139MiB / 3943MiB The tool used to calculate the time, is the time command in Linux. Enumeration Tool Search Time Total Subdomains Found CPU Usage RAM Usage Findomain real 0m5.515s 84110 Very Low Very Low Summary: 84110 subdomains in 5.5 seconds. Features Subdomains monitoring: put data to Discord, Slack or Telegram webhooks. See Subdomains Monitoring for more information. Multi-thread support for API querying, it makes that the maximun time that Findomain will take to search subdomains for any target is 20 seconds. Parallel support for subdomains resolution, in good network conditions can resolv about 2000 subdomains per minute. DNS over TLS support. Specific IPv4 or IPv6 query support. Discover subdomains without brute-force, it tool uses Certificate Transparency Logs and APIs. Discover only resolved subdomains. Discover subdomains IP for data analisis. Read target from user argument (-t) or file (-f). Write to one unique output file specified by the user all or only resolved subdomains. Write results to automatically named TXT output file(s). Hability to query directly the Findomain database created with Subdomains Monitoring for previous discovered subdomains. Hability to import and work data discovered by other tools. Quiet mode to run it silently. Cross platform support: Any platform, it's written in Rust and Rust is multiplatform. See the documentation for instructions. Multiple API support. How it works? It tool doesn't use the common methods for sub(domains) discover, the tool uses Certificate Transparency logs and specific well tested APIs to find subdomains. It method make it tool the most faster and reliable. The tool make use of multiple public available APIs to perform the search. APIs that we are using at the moment: Certspotter Crt.sh Virustotal Sublist3r Facebook ** Spyse (CertDB) * Bufferover Threadcrow Virustotal with apikey ** Notes APIs marked with **, require an access token to work. Search in the Findomain documentation how to configure and use it. APIs marked with * can optionally be used with an access token, create one if you start experiencing problems with that APIs. Search in the Findomain documentation how to configure and use it. Download: [HIDE][Hidden Content]]