{{form.name}} {% if form.errors.name %} {{form.errors.name}} {% endif %}

Does this tool gathers subdomains?
If you have chosen this tool as subdomain gathering tool, you'll be able to use it in scan engine configuration and provide this tool name inside uses_tools. If not, you will still be able to use this tool in our custom scripting engine.

{{form.github_url}} {% if form.errors.github_url %} {{form.errors.github_url}} {% endif %}
{{form.logo_url}}
{{form.license_url}}
{{form.description}}
Tool Installation Process

Please note that any commands here will directly execute in shell, so please be careful of the commands you are using.

  • If the tool has to be installed using github clone, then your installation command would be
    git clone https://github.com/user/tool
  • If the tool has to be installed using go, the your installation command would be
    go install -v github.com/tool@latest
    Please note that, go get command is no longer supported by go. Instead you should use go install. Learn why!

{{form.install_command}}

If update command is not provided, you will not be able to update the tools.

{{form.update_command}} {% if form.errors.update_command %} {{form.errors.update_command}} {% endif %}

reNgine will use this command to check the version of the tool and let you know if there is any update available. Most tools will display the version either of these ways

You can provide these commands depending on your tool, and reNgine will identify the version number.

(We have auto generated this for you based on your installation steps) {{form.version_lookup_command}} {% if form.errors.version_lookup_command %} {{form.errors.version_lookup_command}} {% endif %}

reNgine needs version match regex to find out if there is any update available or not. You can check how the tool displays the version number and we can generate the regex for you, or you can do that manually as well.
If version regex is not given, reNgine will not be able to check the updates automatically. However, you can still force update the tools.
Additionally, we can also generate the version regext for you. You can select how this tool displays the version number.
See, how the tool names the release version. https://github.com/user/tool/releases



{{form.version_match_regex}} {% if form.errors.version_match_regex %} {{form.errors.version_match_regex}} {% endif %}
Subdomain Gathering Tool Additional Information
Please note that this subdomain gathering tool must support subdomain output in the form of txt file.

Since you have chosen this tool as subdomain gathering tool, we require additional information on how this tool runs.

reNgine needs to know how this tool accepts target and output the subdomain results.
Use the below syntax wherever required, but remember that {TARGET} and {OUTPUT} are mandatory placeholders.
  • {TARGET} (mandatory), Use this for the command-line arg that takes in domain as input target. Example. subfinder -d {TARGET}
  • {OUTPUT} (mandatory), Use this for the command-line arg that takes the output arg. Example. subfinder -d {TARGET} -o {OUTPUT}
  • {PATH}, Use this if your tool is github cloned. Example. python3 {PATH}/subdomain.py
  • {PROXY}, Use this if your tool supports proxy. Example. tool_name -p {PROXY}
You can use the combinations of the above syntax and also you can use any other command-line argument that your tool supports.
{{form.subdomain_gathering_command}}