Acceptable Use — authorized IP stresser rules that keep testing legal.

Acceptable use

You may use Slammed.st solely to generate controlled Layer 4 and Layer 7 traffic against systems that you own or that you are explicitly authorized to assess. Acceptable use means the test has a legitimate capacity, resilience, or performance purpose; the target is verified; intensity and duration stay within your plan and the permission you hold; and you can stop the session when the objective is met.

“Authorized IP stresser” and “authorized load testing” describe the same boundary: traffic is intentional, documented, and limited to infrastructure under your control or written mandate. Using the platform as a booter, anonymous attack service, or tool to disrupt third parties is never acceptable use.

Permission must cover, at minimum: the specific target (hostname, IP, URL, or application endpoint), the type of traffic you will generate, the maximum intensity you intend to apply, and the time window in which testing is allowed. If any of those elements is missing, do not run the test.

Authorization requirements

Before you configure a meaningful load session, you must be able to demonstrate authorization. Typical evidence includes ownership of the domain or network, a hosting or cloud account in your organization’s name, a written engagement letter or change ticket approving the test, or documented approval from the system owner that names the target and window.

• Authorization must be current for the testing window you schedule.
• Authorization must belong to you or to the organization on whose behalf you act.
• Shared hosting, multi-tenant platforms, and upstream providers may require additional notice — obtain it before testing.
• You remain responsible for keeping proof of permission and for configuring tests that respect it.

Slammed.st may require target verification steps inside the product. Completing those steps does not replace your obligation to hold real-world permission; verification is a platform control, not a legal shield for unauthorized activity.

Verified targets

Verified targets are endpoints that have passed the platform’s ownership or authorization checks. Only verified targets may receive substantive test traffic. Attempting to point sessions at unverified third-party systems, spoof ownership, reuse another customer’s verification, or otherwise evade checks violates this AUP.

If a target’s ownership changes, authorization expires, or you lose permission, stop testing that target and remove or update it. Continuing to stress infrastructure without ongoing authority is prohibited even if the target was previously verified.

For product context on how authorized testing is designed, see authorized load testing and the company overview at company.

Allowed use cases

The following use cases are examples of acceptable, authorized activity when targets are verified and permission is in place:

• Capacity planning before a launch, marketing campaign, or seasonal peak.
• Rehearsing autoscaling, failover, CDN behavior, and origin limits on systems you operate.
• API and website performance validation under controlled L7 traffic patterns.
• Game or platform operations rehearsals on environments owned or contracted by your organization.
• Comparing regional behavior using the platform’s testing regions for infrastructure you control.
• Regression checks after architecture changes, using repeatable sessions and stop controls.

Educational or research use is allowed only when the researcher has explicit authority over the target environment. Curiosity about someone else’s public IP is not authorization.

Zero-tolerance activity

Slammed.st maintains a zero-tolerance policy for activity that weaponizes the platform. The following are strictly prohibited:

• Unauthorized denial-of-service activity or any attempt to disrupt services you do not own or lack permission to test.
• Using Slammed.st as a booter, stresser-for-hire against third parties, or anonymous attack relay.
• Evading, falsifying, or circumventing target verification, plan limits, or account controls.
• Credential stuffing, account sharing that defeats security controls, or unauthorized access to another user’s account.
• Distributing malware, phishing content, or illegal material through or alongside the service.
• Testing targets where law, contract, or upstream policy forbids the traffic you intend to generate.
• Harassment, extortion, or any use intended to coerce or harm a third party.

Violations may result in immediate session stops, account suspension or termination, preservation of relevant records, and cooperation with valid legal process. Fees already incurred are handled under the Terms of Service; prohibition of misuse does not create a right to continued access.

Abuse response

When activity appears unsafe, unauthorized, or inconsistent with this AUP, we may take one or more of the following steps without prior notice where necessary to protect networks and third parties:

1. Pause or terminate active tests.
2. Restrict methods, concurrency, regions, or account privileges.
3. Require additional verification or written proof of authorization.
4. Suspend or terminate the account.
5. Preserve logs and related records for security, abuse, and legal purposes.
6. Respond to valid law-enforcement or court requests according to applicable law.

We aim to act proportionally. Clear unauthorized disruption is treated urgently. Ambiguous cases may involve requests for clarification — but we are not obligated to continue service while risk remains unresolved.

Platform availability during investigations is described in operational terms on status; AUP enforcement can affect individual accounts independently of global status.

Reporting

If you believe Slammed.st traffic is reaching a system without authorization, or you observe other AUP violations, report them promptly.

Abuse reports: send details to abuse@slammed.st. Include the affected target (IP, hostname, or URL), approximate timestamps (with timezone), any source information you have, and supporting evidence such as logs or packet captures. The more precise the report, the faster we can investigate.

Security vulnerabilities in the Slammed.st product or infrastructure: report to security@slammed.st. Describe the issue, affected component, and steps to reproduce at a high level. Do not include exploit payloads aimed at third parties; responsible disclosure about our own systems is welcome.

Write email addresses manually in your mail client. We do not publish mailto links that create Cloudflare email-protection URLs.

Relationship to Terms and Privacy

This Acceptable Use Policy is part of the rules governing Slammed.st. It works together with the Terms of Service, which form the contractual agreement for accounts, billing, liability, and termination, and the Privacy Policy, which explains how we handle personal and operational data, including logs used for abuse prevention.

If there is a conflict between marketing copy and this AUP on the question of unauthorized testing, this AUP and the Terms control: authorized, verified-target testing only.

For company background and trust signals, see company. For plan and product context, see pricing and features.

Related resources

Further reading for teams evaluating authorized IP stresser use, acceptable use, and legal framing:

• Authorized load testing — how the product model works.
• Is using an IP stresser legal? — plain-language guide emphasizing permission and verified targets.
• Best IP stresser 2026 — buyer criteria that prioritize authorization and process.
• Glossary — definitions for L4/L7 testing and verification terms.
• Terms of Service · Privacy Policy · AML Policy · Status · Company

Questions about this AUP that are not abuse reports can be directed through support channels listed on the company page. Abuse and security reports should use the addresses above so they reach the right queue quickly.