Layer 4 & Layer 7 · DNS-verified · API-first
LittleAndKing's IP stresser fires TCP, UDP, SYN, ACK and HTTP/HTTPS floods at a target you have proven you control. You get live metrics, a REST API and DNS-verified targets on every run.
Two layers, one panel. Layer 4 floods test the pipe and the kernel; layer 7 floods test the application and the WAF.
| Layer | Method | What it stresses | When to use it |
|---|---|---|---|
| L4 | TCP flood | Connection table and socket exhaustion | You want to test edge connection limits |
| L4 | UDP flood | Bandwidth and UDP buffer depth | You run DNS, game or media services |
| L4 | SYN flood | Half-open connection queue | You want to test SYN cookies and rate limits |
| L4 | ACK flood | Packet processing rate and firewall rule cost | You want to test edge ACLs |
| L7 | HTTP flood | Request handling, cache hit ratio, worker pool | You want to test a CDN or reverse proxy |
| L7 | HTTPS flood (browser emulation) | WAF rules, rate limits, backend logic | You want realistic user traffic, not a blunt hammer |
Layer 4 tests answer the pipe question. A SYN flood tells you how many half-open connections your kernel queues before it drops. A UDP flood tells you how deep the buffer is and how fast the NIC sheds. You run these to find the ceiling before you tune the app.
Layer 7 tests answer the app question. A GET flood against a cached route may do nothing; the same flood against an uncached search route may take the database down. Browser emulation with cookies, headers and per-step delays makes the traffic look like real users, which is what your WAF is tuned for.
No target runs without proof of ownership. The DNS TXT check is what separates a load test from a booter.
Put a unique token in the domain's DNS as a TXT record. Only someone with DNS control can do this.
The panel checks the TXT record before the test starts, and re-checks it right before each run.
Once the DNS record is reverted to someone else, the token stops working. No reuse, no spoofing.
Launch, stop and inspect IP stresser tasks with a single HTTP call. GET and POST supported, JSON over TLS. Scoped keys, per-key caps, atomic slot reservation.
Launch a task
POST /api/v1/task
Content-Type: application/json
Authorization: Bearer <key>
{
"target": "api.example.com",
"layer": "L7",
"method": "https-flood",
"duration": 300,
"rate": 250000
}
Inspect a task
GET /api/v1/task/LK-4102
Authorization: Bearer <key>
{
"id": "LK-4102",
"status": "running",
"elapsed": 204,
"remaining": 396,
"throughput": "6.84M req/s"
}
Scoped keys. Issue, rotate and revoke per-key. Per-key task-time and slot caps keep a shared key inside its lane.
Atomic slots. Slot reservation is atomic, so two tasks cannot claim the same slot at the same instant.
Full coverage. Every plan above Starter includes full API access. Starter itself does not.
Free tier to try, Starter to start, Pro for teams, Business for 10M+ req/s. Crypto accepted, no setup fees, cancel anytime.
| Plan | Concurrent | Max runtime | Peak rate | API |
|---|---|---|---|---|
| Free | 1 | 120 s | 250K req/s | No |
| Starter | 1 | 10 min | 1,000,000 rq/s | No |
| Pro | 5 | 2 h | 5,000,000 rq/s | Yes |
| Business | 100 | 24 h | 10,000,000+ rq/s | Yes |
An IP stresser is a service that generates controlled network load against a target host so you can measure how it holds up under heavy traffic. LittleAndKing supports layer 4 and layer 7 methods and requires DNS-verified targets.
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.
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.
Yes. Every plan above Starter includes full REST API access. Launch, stop, list and inspect tasks with single HTTP calls (GET and POST), all JSON over TLS. Keys are scoped, rotatable and revocable.
Testing infrastructure you own — or have written authorization to test — is legal in most places. Every target here has to pass a DNS TXT check before any test runs, and we re-check it on each launch, so every test stays inside the authorized testing envelope.
Starter is $30/month (1 concurrent slot, up to 1,000,000 requests/sec, 10-minute max task runtime). Pro is $150/month (5 slots, up to 5,000,000 rq/s, 2-hour max runtime, API access). Business is $3,000/month (100 slots, over 10,000,000 rq/s, 24-hour max runtime, full API). The free stresser tier is $0 forever.
Start on the free stresser tier, verify your domain with a DNS TXT record, and launch the first test from the Hub panel. Paid plans unlock longer runtimes, more slots and the REST API.