Last reviewed 16.11.2026, 09:00

Acceptable Use — IP Stresser Legal & Authorization Rules

What the IP stresser and free stresser will run, what it will not run, and the authorization gate that sits before every launch.

Authorization is required, every run

Every IP stress test on this platform requires proof that the target IP is yours or that you have written permission from the party that owns it. The proof is checked before the run launches, not after, and a run without proof does not launch. There is no "quick test to verify ownership," no partial run, and no bypass. A failed authorization is a hard stop.

The accepted proof is one of two: a DNS TXT record on the target domain that matches a token the platform issues to your account, or a control panel screenshot from your hosting provider showing the target IP assigned to your account. The DNS record is checked automatically. The screenshot is reviewed manually the first time and then cached for that IP.

The proof is re-checked whenever the target IP changes. If you prove ownership of 203.0.113.10 on Monday and try to run against 203.0.113.11 on Tuesday, the Tuesday run goes through the same authorization gate as the first. This is not a formality; it is the difference between a load testing platform and a weapon, and the platform is the first and not the second.

What the platform will run

The platform will run an IP stress test, a free stresser run, or an IP booter run against a target IP that has cleared the authorization gate. It will run it with any Layer 7 or Layer 4 method on the method list, at any duration the tier allows, from the platform's own distributed infrastructure. It will return the full report, the time series and the history entry, the same on free and paid, with the only difference being the duration cap and the daily quota.

The platform will run against a VPS, a home lab, a game server, a staging environment, a small hosting setup with several IPs, or any other infrastructure you own or have written permission to test. It does not require you to be an enterprise customer, it does not require you to own a domain, and it does not require a credit card on the free tier. It does require the proof.

The platform will run a Layer 7 stresser method against a web application, a Layer 4 stresser method against a game server, a TCP SYN flood against an edge firewall, a UDP flood against a DNS resolver, and every other combination on the method list, as long as the target is authorized. The method list is a menu, not a restriction; the restriction is the authorization gate, not the method.

What the platform will not run

The platform will not run against a target that has not cleared the authorization gate. This is the whole list, and everything else on this page is a consequence of it. A target you do not own and cannot prove permission for is a target the platform will not touch, regardless of the method, the duration, or the tier.

The platform will not run against a shared hosting provider's shared IP, a CDN's edge IP that serves multiple customers, a cloud provider's shared load balancer IP, or any other address where the party who receives the traffic is not the party who authorized it. If your service sits behind a CDN, target the origin IP you control, not the CDN edge, unless you can prove the CDN edge is dedicated to you.

The platform will not run against a government, military, financial institution, healthcare provider, or critical infrastructure target, even if you claim authorization. The platform's operator makes the final call on this, and the call is conservative: if the target category is on the list, the run does not launch, regardless of the proof. This is a platform policy, not a legal position, and it is not negotiable through the support inbox.

Hard wall. Sexual content involving minors is not a category this platform will discuss, host, or route traffic for, in any context, on any page. It is the one wall, and it is not negotiable. Any request touching it gets one line: absolute no ollie. try me again with something that isn't that. Everything else on the agenda stays on the agenda.

Data handling

The platform stores four things about each run: the target IP, the method, the duration and the report. The report includes the time series, which is per-second data for the run. The target IP is stored because the authorization proof is tied to it and because the history needs it to show you the previous run against the same target. The method and duration are stored because the history needs them to make the report readable. The report is stored because the report is the product.

The platform does not store the authorization proof itself beyond the cached confirmation. A DNS TXT record is checked against the token and the confirmation is stored; the record itself is not retained. A control panel screenshot is reviewed and the confirmation is stored; the screenshot is deleted after review. The platform does not store your hosting account credentials, does not have access to your control panel, and does not ask for either.

The platform logs access to the panel for security purposes: login events, run launches, and authorization checks. These logs are retained for 90 days and are not shared with third parties. The platform does not sell run data, does not aggregate run data into a public dataset, and does not use run data to train a model. If you want your run history deleted, email [email protected] and the history is deleted within five business days; the target IP is retained only as a hash so the authorization cache does not have to be rebuilt if you return.

Jurisdiction and legal basis

The platform operates under the laws of the jurisdiction where its operator is established. Running an IP stress test against infrastructure you own or have written permission to test is lawful in most jurisdictions, including the United States, the United Kingdom and the European Union, provided the authorization is genuine and the target is the authorizing party's own infrastructure. Running one against a target you do not own is a computer misuse offence in all three jurisdictions, and the platform's authorization gate exists precisely to keep that line bright.

The legal basis for the platform's processing of your data is the performance of the contract between you and the platform (the load testing service), plus the legitimate interest of the platform in preventing abuse (the authorization gate and the access logs). The platform does not rely on consent for any processing that is necessary to provide the service, because a service that stops working when consent is withdrawn is not a service; it is a consent banner with a product attached.

If you are a law enforcement agency or a regulator and you need to contact the platform about a specific run, email [email protected] with the request. The platform responds to lawful requests and does not respond to requests that are not lawful, and the response will name which category the request falls into. The platform does not have a "compliance" page that lists the requests it has received, because the platform has not received any, and a page that lists zero requests is a page that exists to look transparent rather than to be transparent.

Changes to this policy

This policy changes when the platform's behavior changes, not on a schedule. The review date at the top of this page is the date of the last change, and it is the same date as the page's `dateModified` in the structured data. A change that narrows what the platform will run is announced on the home page for 30 days before it takes effect. A change that widens what the platform will run is not announced, because a widening is not a risk to the reader; it is a feature.

If a change to this policy makes a run you have already scheduled unauthorized, the run does not launch, and the platform emails you the reason. The platform does not retroactively delete your run history because the policy changed; the history is a record of what happened under the policy in force at the time, and rewriting the record is not something a load testing platform should do any more than a stress test should edit its own report.

Contact

Legal and policy questions go to [email protected]. The reply window is five business days. If you are writing about a specific run, include the run ID from your history; that is the fastest way to get a useful reply. If you are writing about the authorization gate in the abstract, the reply will point you at this page, because this page is the answer.