Protocol Agnostic – Currently supporting HTTP, HTTPS, HTTP/2. Other protocols are on the way.Scenario-Based – Create your flow in a JSON file. Without a line of code!Different Load Types – Test your system’s limits across different load types.
docker run -it --rm ddosify/ddosify
Homebrew Tap (macOS and Linux)
brew install ddosify/tap/ddosify
apk, deb, rpm packages
# For Redhat based (Fedora, CentOS, RHEL, etc.)
rpm -i https://github.com/ddosify/ddosify/releases/download/v0.1.1/ddosify_amd64.rpm
# For Debian based (Ubuntu, Linux Mint, etc.)
dpkg -i ddosify_amd64.deb
# For Alpine
apk add --allow-untrusted ddosify_amd64.apk
Using the convenience script (macOS and Linux)
- The script requires root or sudo privileges to move ddosify binary to
- The script attempts to detect your operating system (macOS or Linux) and architecture (arm64, x86, amd64) to download the appropriate binary from the releases page.
- By default, the script installs the latest version of
- If you have problems, check common issues
- Required packages:
curl -sSfL https://raw.githubusercontent.com/ddosify/ddosify/master/scripts/install.sh | sh
Go install from source (macOS, Linux, Windows)
go install -v go.ddosify.com/ddosify@latest
This section aims to show you how to use Ddosify without deep dive into its details easily.
Simple load test
ddosify -t target_site.comThe above command runs a load test with the default value that is 100 requests in 10 seconds.
Using some of the features
ddosify -t target_site.com -n 1000 -d 20 -p HTTPS -m PUT -T 7 -P http://proxy_server.com:80Ddosify sends a total of 1000 PUT requests to https://target_site.com over proxy http://proxy_server.com:80 in 20 seconds with a timeout of 7 seconds per request.
Scenario based load test
ddosify -config config_examples/config.jsonDdosify first sends HTTP/2 POST request to https://test_site1.com/endpoint_1 using basic auth credentials test_user:12345 over proxy http://proxy_host.com:proxy_port and with a timeout of 3 seconds. Once the response is received, HTTPS GET request will be sent to https://test_site1.com/endpoint_2 along with the payload included in config_examples/payload.txt file with a timeout of 2 seconds. This flow will be repeated 20 times in 5 seconds and response will be written to stdout.
You can configure your load test by the CLI options or a config file. Config file supports more features than the CLI. For example, you can’t create a scenario-based load test with CLI options.
|Target website URL. Example: https://ddosify.com||–||Yes|
|Total request count||No|
|Test duration in seconds.||No|
|Protocol of the request. Supported protocols are HTTP, HTTPS. HTTP/2 support is only available by using a config file as described. More protocols will be added.||No|
|Request method. Available methods for HTTP(s) are GET, POST, PUT, DELETE, UPDATE, PATCH||No|
|The payload of the network packet. AKA body for the HTTP.||–||No|
|Basic authentication. Usage: ||–||No|
|Headers of the request. You can provide multiple headers with multiple ||–||No|
|Timeout of the request in seconds.||No|
|Proxy address as host:port. ||–||No|
|Test result output destination. Other output types will be added.||No|
|Type of the load test. Ddosify supports 3 load types.||No|
|Config File of the load test.||–||No|
|Prints version, git commit, built date (utc), go information and quit||–||–||No|
ddosify -t target_site.com -l linear
Note: If the request count is too low for the given duration, the test might be finished earlier than you expect.
ddosify -t target_site.com -l incremental
ddosify -t target_site.com -l waved
Config file lets you use all capabilities of Ddosify.
The features you can use by config file;
- Scenario creation
- Payload from a file
- Extra connection configuration, like keep-alive enable/disable logic
- HTTP2 support
ddosify -config <json_config_path>
There is an example config file at config_examples/config.json. This file contains all of the parameters you can use. Details of each parameter;
request_countoptionalThis is the equivalent of the
-nflag. The difference is that if you have multiple steps in your scenario, this value represents the iteration count of the steps.
load_typeoptionalThis is the equivalent of the
durationoptionalThis is the equivalent of the
proxyoptionalThis is the equivalent of the
outputoptionalThis is the equivalent of the
stepsmandatoryThis parameter lets you create your scenario. Ddosify runs the provided steps, respectively. For the given example file step id: 2 will be executed immediately after the response of step id: 1 is received. The order of the execution is the same as the order of the steps in the config file.Details of each parameter for a step;
idmandatoryEach step must have a unique integer id.
urlmandatoryThis is the equivalent of the
protocoloptionalThis is the equivalent of the
methodoptionalThis is the equivalent of the
headersoptionalList of headers with key:value format.
payloadoptionalThis is the equivalent of the
payload_fileoptionalIf you need a long payload, we suggest using this parameter instead of
othersoptionalThis parameter accepts dynamic key: value pairs to configure connection details of the protocol in use.
"keep-alive": true, // Default false
"disable-compression": false, // Default true
"h2": true, // Enables HTTP/2. Default false.
"disable-redirect": true // Default false
macOS Security Issue
"ddosify" canâ€™t be opened because Apple cannot check it for malicious software.
- Right click
ddosifyand select Open
- Select Open
- Close the opened terminal
You can join our Discord Server for issues, feature requests, feedbacks or anything else.
This repository includes the single-node version of the Ddosify Loader. Ddosify Cloud will be available soon. It will support multi-location based distributed load testing and more features.
Join the waitlist: https://ddosify.com
Licensed under the AGPLv3: https://www.gnu.org/licenses/agpl-3.0.html