This section explains every thing that was not a major module, eg atk, or certian newer commands

---

A breif intro as to how the red rabbit terminal works

I did not want to go over this or bother making this a section in other command like sections so why not do it here. Red rabbit works alot like metasploit in terms of running options, it has a module, each module has its own utility, say the module search right. The search module stays static but its subroutines dont `search mx` changes at mx `search head` changes at head. Take the following tree as an example of how modules work so do note, all options that you input whatever the first thing you type to run that module is going to be the module name, a way to shorten the giant ass command list is to type `help module_name` example as `help inject` will output all information and commands under the module inject in a organized and fit manner

---

> Section API, this section will talk about all API commands

- api layerus config

as I have mentioned here before every command ending in config, conf, setting, or custom is a customized command, where data is read from a file, a yaml file, a json file, or some other file. the API layerus config command uses a file in the directory `API/configuration` named api_keys.json, this json file is structured like the following for the api layerus config command you will need to input your API layer API key in the APILA_KEY section of the json file. once done then you can run the command this command traces and gets all information on a US phone number, this is not just API layer being used but also red rabbits custom offline databases for matches take the following example as a number19644520897

- api layerbe config

this is the same as above but just uses red rabbits belgium database for finding extra information such as country codes, country name, city name etc

- api layerus

this is the same thing as the api layerus config but you manually input your API key

- api layerbe

same command as api layerbe config but the key is manually inputted by the user

- api whoisx config

whois xml is a pretty big whois api, and with red rabbits intensly generated types and responses it is able to get a good amount of information from it using the api, this command works as any other config command above, the api key will be stored in the file `api_keys.json` in the filepath `API/configuration`, your api key will be put in the JSON field labled `WHOIS_KEY` however you will also need your username and password which go in the fields `WHOIS_PAS` and `WHOIS_USR` where `WHOIS_USR` is your whoisxml username and `WHOIS_PAS` is the field for your whoisxml password. when thats all set run the command and you input a website or domain name you will get the following output

- api whoisxml

same thing as above but without the api key being in a config file, rather just manually inputting the key yourself each time

- api grab config

this config will simply locate and pull all API keys from all configuration files used for api's or other settings in red rabbit.

---

Engine

> This section will talk about all commands in the engine module. The engnine module utilizes google to scrape for certian information from a given search query. the engine module can be set with flags such as using the --SQ option to set a search query, the --RPP option to set the reuslts per page, and the --PTC to name the amount of pages to crawl of google for your information. an example using the flags would be sudo go run main.go --SQ="inurl:index.php?id=1" --RPP=10 --PTC=1 example usage of the enguine would be if you search for user1234 as a search query you will get the following output.

- engine ogoogle

this command will search for just google related results. if it has any other information or link that is not google related then it will skip it and not append it. Sometimes it will grab information from other sources but its a small amount mainly the engine will generalize all targets around a google link. say you search for a website like the following inurl:"index.php?id=1" you will get something like the following output

- engine otwitter

This command does the same thing as the other one but will specify links ONLY to twitter links or links found from the third or second position away from a twitter searched query, so if you search for something like a username you will get mostly twitter links with just that username or people who have a account tied to that username

- engine ofacebook

This command does the same thing as the one above but will specify links ONLY to facebook links or links found from the third or second position away from a facebook searched query, so if you search for something like a username you will get mostly facebook links with just that username or people who have a account tied to that username

- engine olinkedin

This command does the same thing as the one above but will specify links ONLY to linkedin links or links found from the third or second position away from a linkedin searched query, so if you search for something like a username you will get mostly linkedin links with just that username or people who have a account tied to that username

- engine shodanh

This command will search shodan using a API key to search for information on a host, say you have a host of 1.1.1.1 to search you would use this engine option to show information on that hostname or of all results that engine pulled in search for that query or hostname.

- engine cve

This command also uses the google engine but instead of searching google for information it will search a CVE database for information, such as a CVE's name, date, moded date, Description, information, articles, or other relevant data to teach you about certian CVE's. You can search by date or name of the CVE and example is `shop` there is another option and that is simple to use tor to reach the database thats holds the CVE information, this option is `engine tcve` simply just using a proxy to reach and pull data from the database.

Stalk

This is the section which will talk about two options in the stalk module

- stalk hosts and stalk hosts2

both are relative to each other, the only difference is the brute forcing method, so stalk hosts is a subset which will allow the user to set 3 or 2 octets or a network address. stalk hosts will allow the user to input 3 octets and example is (172.217.2) and you will brute force all possible ranges and network addresses that match anf youll get something like the following using that example the second one stalk hosts2 again does the same but you can instead of input (172.217.2) you can do (172.217) and it will brute force all possible combinations until it finds a server like the following output

---

Proxy downloading

> fetch proxy4, fetch proxy5 both of these commands do the same thing. what they do is download proxies and save them to a output file you specified wether it was from using the -o flag or by manually typing it when the program asks for it. however the difference is proxy4 will fetch all proxies it can for SOCKS4, proxy5 will fetch all proxies for SOCKS5 > fetch http/https/httpssl/httpsssl like the one above all of these are similar, specify an output file and it will download and save proxies to that given file. fetch http/https commands will fetch all proxies relating to a http/https like address, there are options to also use SSL for the proxy grabbing list. fetch htpssl and httpsssl will grab proxies of either http or https and make sure they are specified to just SSL, anything without SSL will not be added to the list.