Ddosify – High-performance Load Testing Tool

Features

Note: If the request count is too low for the given duration, the test might be finished earlier than you expect.

Incremental

ddosify -t target_site.com -l incremental

Result:

Waved

ddosify -t target_site.com -l waved

Result:

Config File

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

Usage;

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_count optional

  This is the equivalent of the -n flag. The difference is that if you have multiple steps in your scenario, this value represents the iteration count of the steps.

• load_type optional

  This is the equivalent of the -l flag.

• duration optional

  This is the equivalent of the -d flag.

• proxy optional

  This is the equivalent of the -P flag.

• output optional

  This is the equivalent of the -o flag.

• steps mandatory

  This 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;

  • id mandatory

    Each step must have a unique integer id.

  • url mandatory

    This is the equivalent of the -t flag.

  • protocol optional

    This is the equivalent of the -p flag.

  • method optional

    This is the equivalent of the -m flag.

  • headers optional

    List of headers with key:value format.

  • payload optional

    This is the equivalent of the -b flag.

  • payload_file optional

    If you need a long payload, we suggest using this parameter instead of payload.

  • auth optional

    Basic authentication.

    "auth": {
        "username": "test_user",
        "password": "12345"
    }

  • others optional

    This parameter accepts dynamic key: value pairs to configure connection details of the protocol in use.

    "others": {
        "keep-alive": true,              // Default false
        "disable-compression": false,    // Default true
        "h2": true,                      // Enables HTTP/2. Default false.
        "disable-redirect": true         // Default false
    }

Common Issues

macOS Security Issue

"ddosify" can’t be opened because Apple cannot check it for malicious software.

• Open /usr/local/bin
• Right click ddosify and select Open
• Select Open
• Close the opened terminal

Communication

You can join our Discord Server for issues, feature requests, feedbacks or anything else.

More

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

License

Licensed under the AGPLv3: https://www.gnu.org/licenses/agpl-3.0.html