DDoS resilience testing
Valistra.
Controlled, staged load against systems you own, inside a window you agree. We measure what your DDoS protection, rate limits, alerts and services do at each step, and how fast your services recover.
How a run works
One run, step by step.
Every run follows the same shape, agreed before it starts.
Agreed ceiling
Requests per second (illustrative)
- 01
Baseline
We record normal behavior first, so every change has a reference point.
- 02
Agreed steps
Load rises in steps agreed in advance, each planned below the ceiling in your contract.
- 03
Watch the response
At each step we record what your protection, rate limits, alerts and services do.
- 04
Stop, any time
Your team holds the stop control. When it is used, the run stops.
- 05
Recovery
We measure how long your services take to return to normal.
- 06
Report and retest
Findings and fixes in plain language, then a shorter retest against the same scope.
Safety controls
What you sign before a run.
Valistra is built for systems that matter, so the controls come first. We test only systems you own, with your written authorization.
- Systems in scope
- Only systems you own
- Test window
- Dates and times fixed in the contract
- Agreed ceiling
- Every step is planned below it
- Stop control
- Agreed in advance and held by your team
- Declared sources
- So your team and providers can tell test traffic apart
- Providers notified
- Hosting, CDN and protection, where their terms ask for it
- Staging first
- If you want it
- Authorized by
- The owner of the systems, in writing
- Retest
- Same scope, shorter run
Questions
Before you write to us.
Will a test take our site down?
Services can slow down; finding where that starts is the point. That is why runs start low, rise in agreed steps under a ceiling, can begin in staging, and can be stopped by your team at any moment.
Do we need to tell our hosting or protection provider?
Often, yes. Many providers ask to be told before any load testing. We help you prepare that notice.
Can you test a system we do not own?
No. We test only systems you own, with your written authorization.
Who can authorize a test?
The owner of the systems in scope, in writing, as part of the contract.
How long does an engagement take?
It depends on the scope. The run itself is short and scheduled; preparation and reporting take longer. We agree the timeline in the contract.
Plans
Four ways to subscribe.
Monthly plans for regular clients, and a custom route for enterprise. Plans open when the service goes live; no payment is taken yet.
-
Opening soon
Starter
/ monthMonthly price to be announced
For individuals and small sites.
Payment opens at launch.
-
Opening soon
Professional
/ monthMonthly price to be announced
For small businesses.
Payment opens at launch.
-
Opening soon
Business
/ monthMonthly price to be announced
For larger teams and public bodies.
Payment opens at launch.
-
Custom
Enterprise
Custom
We run the tests for you, under written authorization.