Signup → DNS verify → Launch → Read metrics
Sign up, prove the target is yours with a DNS TXT record, choose a method, launch the task, and read the result on your own metrics. About 60 seconds from account creation to first test.
Three steps. Each one ends with a clear state, so you always know whether the test is queued, running, or done.
Create an account in seconds and add a DNS TXT record to the domain you want to test. No credit card needed to start.
Step ends when: the target shows as verified in the panel.
Choose Starter, Pro or Business if you need more slots and longer runtimes — or stay on the free stresser tier while you get a feel for the panel. Crypto payments accepted, cancel anytime.
Step ends when: the plan is active and the slot shows in the Hub.
Open the Hub panel, pick your target, choose layer 4 or layer 7, set duration and rate, and hit Launch. The task starts right away with live metrics.
Step ends when: the task finishes and your graphs settle.
The DNS check is what separates a load test from a booter. Nobody can run a test on a host they do not control.
Put a unique token in the domain's DNS as a TXT record. Only someone with DNS control can do this, which is the point.
The panel checks the TXT record before the test starts, and re-checks it right before each run. Not just once at signup.
Once the DNS record is reverted to someone else, the token stops working. No reuse, no spoofing, no third-party abuse.
The TXT record is the whole authorisation. If you can write it, you own the DNS. If you cannot, the test does not run. That is why the free tier and the paid tiers use the same check — the plan does not change the rule, it changes the ceiling.
Re-verifying before each run closes a gap that other tools leave open. A token that was valid when the account was created is not proof of ownership next month. Re-checking means a transferred domain cannot be tested by its old owner.
Both run from the same Hub panel. What differs is the layer, the metric you watch, and what a "success" looks like.
Layer 4
These measure raw network throughput, connection-table saturation and firewall capacity. This is the layer where you find out if your pipe and your edge rules can take the hit.
What you read: half-open connection counts, kernel drop rate, NIC buffer depth, upstream scrub capacity.
Layer 7
These test WAF rules, rate limits and CDN behaviour under realistic user traffic. Cookies, headers and per-step delays make the traffic look like real users, not a blunt hammer.
What you read: request rate, worker pool saturation, DB connection count, error rate by route.
A live task table, per-server breakdown, slot saturation, throughput and uptime metrics. Watch the target react as the load goes up, instead of guessing from a graph after the fact.
Status
running
Elapsed
03:24
Remaining
06:36
Throughput
6.84M req/s
Latency
49 ms
Success
99.97 %
The panel shows what was sent. Only your own CPU, memory, connection counts and error rates show what your stack did with it. Read both.
Three cases where the panel should stay closed. These are the mistakes that cause incidents, not the tests themselves.
If the hostname resolves to a CDN edge, the traffic hits the CDN, not your origin. You measure the CDN's scrubbing capacity and learn nothing about your own stack. Test the origin directly, from a known IP, with the CDN bypassed on purpose.
A load test on a live system at 3 p.m. is an outage with extra steps. Run it on staging, or run it on production at the quietest hour you have, with a rollback plan and an on-call engineer watching the same graphs you are.
If the target belongs to a client, a host or an employer, get the permission in writing first. Most acceptable-use policies allow stress testing, but only when the provider has been told in advance and the traffic stays inside a declared window.
About 60 seconds. Sign up, pick a plan or stay on the free stresser tier, verify your target via DNS TXT, then launch your first task from the Hub panel. Most people run their first test within five minutes of signing up.
You add a unique TXT record to the domain you want to test, proving you control its DNS. We check it before the test starts and again right before each run. Once DNS is reverted to someone else, the token stops working.
Layer 4 tests run at the transport layer (TCP, UDP, SYN, ACK floods) and measure raw network throughput, connection-table saturation and firewall capacity. Layer 7 tests run at the application layer (HTTP/HTTPS with browser emulation, cookies, headers, form input and per-step delays) and measure how your web stack handles realistic user traffic at scale.
Yes. The free stresser tier is free forever — no credit card, no trial period, no hidden fees. You get 1 concurrent test, 120-second max duration, 250K req/s and 10 tests per day.
The panel shows what was sent — throughput, latency and success rate. Your own CPU, memory, connection counts and error rates show what happened on the target. Read your metrics, not the panel's.
Sign up, add the DNS TXT record, pick a method and launch. Start on the free tier, move to Starter, Pro or Business from the billing panel whenever the free ceiling gets too tight.