Is a DDoS stresser legal?

Against infrastructure you own or are authorised to test, yes. Against anything else it is a computer misuse offence. The difference is authorisation for that host, not the brand on the panel.

How much load can one run generate?

The ceiling comes from your plan: Starter reaches 5 Gbps L4 or 20k RPS L7, Team 20 Gbps or 100k, Scale 50 Gbps or 250k. The form warns you before a run if a rate is above your ceiling.

Why do you verify the target?

Because the DNS TXT check is what keeps a stresser from becoming a weapon. A target that fails verification is refused and does not consume a run credit.

DDoS stresser with verified targets and bounded windows

Run the same traffic a DDoS stresser produces, aimed only at infrastructure you can prove you control, and finish with a report instead of an incident.

Start a free test See plans

Updated November 8, 2026, 14:54 (GMT+3) · reviewed for accuracy

DDoS stresser with verified targets and bounded windows: How target verification works

A DDoS stresser is only useful with a verified target, so the panel checks DNS or a confirmation before any traffic moves. That check is what separates this DDoS stresser from a flood tool, and it applies to the free DDoS stresser run as well.

That check is the difference between a test and a flood tool. It applies on every plan, including the free stresser trial.

DDoS stresser with verified targets and bounded windows: Bounded runs, on purpose

Every DDoS stresser run has a method, a rate and a window, and the window has a ceiling. Short windows confirm a fix, longer windows map a limit, and the pricing page shows which plan reaches which window.

Keep the window short when confirming a fix and longer when mapping a limit. The free DDoS stresser page covers the short form.

Reading DDoS stresser results

Read the DDoS stresser report by finding the rate where delivery drops, then compare it with the capacity you expected. Keep both runs in the stresser panel so the comparison survives the next deploy.

Keep both runs in the stresser panel so the comparison survives the next deploy.

Before your first stresser run

Own the target. Verify it through DNS or the panel before any traffic moves.
Pick one question. Does the endpoint fail, and at what rate? One method per run answers it.
Keep the report. The run lives in the panel so a later test can confirm the change.