Skip to content
SECURITY & DISCLOSURE / DDoSly

Trust is a process, not a badge.

Read the principles guiding safe operations and the boundaries for reporting issues with DDoSly.

SPECIFIC CAPABILITIES DEPEND ON THE VERIFIED PRODUCT RELEASE
DISCLOSURE WORKFLOW

Security reports need a responsible route.

01 / 01 / RECORD

Describe the issue

Capture affected component, version, impact and reproducible steps without including credentials.

02 / 02 / MINIMIZE

Limit sensitive material

Avoid collecting third-party data or testing production systems without permission.

03 / 03 / COORDINATE

Prepare responsible disclosure

Use an agreed secure reporting channel when one becomes available; the public website is not an incident-response system.

A verified vulnerability intake address or encrypted submission endpoint has not yet been published. Do not send exploitable details through the public inquiry preview.

EXPLORE NEXT

Review the trust boundaries.