Register with a nickname, an email and a password. Free access arrives as the Basic plan at $0 a month or as trial credit from live support, and neither route asks for payment details. Once credit lands, the Layer4 and Layer7 tabs open, with adding a target and starting a test on the same screen.
What the free tier allows
One concurrent test, short windows and the core metrics: packet or request rate, error rate, latency. VIP stays off, so the dedicated servers behind 50-60 Gbit/s never enter the free tier. The method count does not change: 30+ Layer4 and 20+ Layer7 methods are visible on a free account, and expiry of credit stops the test rather than spilling over.
Choosing a first target
Your own site or server, tested off-peak if it serves production. A staging box is a fine start: the numbers differ, but the shape of the curve does not. Firing repeated tests at the same target measures warm-up rather than behaviour, so leave ten minutes between runs and keep the window short enough that the load stays reversible.
Reading a single run
First whether the host answered at the rate you tried. If loss appears, step the rate down until it disappears and treat that value as today's number. On an application test, add the 5xx rate and p95 to that reading. One run is a data point, not a threshold; a decision needs a second run at a different time.
The record you keep
The stresser panel keeps target, method, window and rate with the run, and exports the metrics when the test ends. That record is what turns two tests into a comparison instead of two anecdotes. The free stresser tier writes the same record, one layer up.
Who this tier is for
Single-server projects, personal sites and fresh staging environments. It is not enough for a checkout that queues under traffic, where the application and database need their own look. Choosing a layer without knowing which one is the bottleneck sets the measurement wrong from the start, and the layer 7 stresser tab is the application half of that choice.
The ownership check
Only systems you own or have written permission to test. A free account is no exception: traffic at an unconfirmed target closes the account, and the remaining credit is not refunded. The confirmation runs when the target is saved and again when the test starts, which is why IP booter is a different product rather than a different price.
Three mistakes to avoid
Testing during peak hours, which blends production traffic into the result. Choosing the wrong layer, which sends a packet test after an application bottleneck. Deciding on one run. All three are avoided with a quiet hour, the right tab and a second test, and DDoS stresser translates those packet numbers into a verdict.