Methods · API · Monitoring · Verification

Every LittleAndKing capability, in one place.

Layer 4 and layer 7 methods, DNS-verified targets, a REST API with scoped keys, real-time monitoring and a free stresser tier. Below is what each one does and where it fits.

Layer 4 methods

Transport layer floods 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.

Method What it stresses When to use it
TCP floodConnection table and socket exhaustionYou want to test edge connection limits
UDP floodBandwidth and UDP buffer depthYou run DNS, game or media services and want to size the pipe
SYN floodHalf-open connection queueYou want to test SYN cookies and rate limits
ACK floodPacket processing rate and firewall rule costYou want to test edge ACLs and rate-limit rules

Layer 7 methods

HTTP and HTTPS flood with browser emulation tests 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.

Method What it stresses When to use it
HTTP floodRequest handling, cache hit ratio, worker poolYou want to test a CDN or a reverse proxy
HTTPS floodTLS handshake rate and cipher processingYou want to test TLS termination and renegotiation cost
HTTPS flood with browser emulationWAF rules, rate limits, backend logicYou want realistic user traffic, not a blunt hammer

A GET flood against a cached endpoint may do nothing; the same flood against an uncached search route may take the database down in seconds. Browser emulation with cookies, headers and per-step delays makes the traffic look like real users, which is what your WAF is tuned for.

Layer 4 and layer 7 answer different questions. Run both, read both, and write the numbers down. The next test should start where the last one ended, not at the same default concurrency you used last time.

DNS-verified targets

Every host you test has to be proven with a DNS TXT record. We re-verify before each run, so a token cannot be reused after DNS is reverted. No spoofing, no third-party abuse, every test stays authorized.

01

Add a TXT record

Put a unique token in the domain's DNS as a TXT record. Only someone with DNS control can do this.

02

Verified before launch

The panel checks the TXT record before the test starts, and re-checks it right before each run.

03

Revert = token dies

Once the DNS record is reverted to someone else, the token stops working. No reuse, no spoofing.

REST API stresser

Launch, stop and inspect IP stresser tasks with a single HTTP call. GET and POST supported, JSON over TLS. If you already have scripts or a CI pipeline, the API slots in without a fight.

Single-call verbs

Launch, stop, list and inspect — four core calls. Wire them into any script or pipeline. Full reference lives in the API docs.

Scoped API keys

Issue, rotate and revoke keys whenever you want. Per-key task-time and slot caps, plus atomic slot reservation, so a shared key cannot quietly blow through your limits.

JSON over TLS

Both GET and POST are supported. All traffic is JSON over TLS. No binary framing, no custom protocol — standard HTTP clients work as-is.

Real-time monitoring

A live task table, per-server breakdown, slot saturation, throughput and uptime metrics. You can watch how your target reacts 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 %

Nodes online

10

Privacy by default

Passwords are bcrypt-hashed, sessions are encrypted, audit logs are scoped and there are no third-party trackers. We do not sell or share user activity — your tests stay yours.

bcrypt passwords

Passwords are hashed with bcrypt, never stored in plain text, never logged.

Encrypted sessions

Sessions are encrypted end to end between the browser and the panel.

Scoped audit logs

Audit logs are scoped per account. You see your own activity, nobody else does.

No third-party trackers

No ad pixels, no analytics resellers, no cross-site tracking scripts.

Booter alternative

Most booters are anonymous and easy to abuse. LittleAndKing is a DNS-verified booter alternative for teams that need to test their own infrastructure, with audit trails, scoped keys and pricing you can actually read.

The difference is not cosmetic. A booter will fire at any IP you type. LittleAndKing will not start a test until the target proves ownership with a DNS TXT record, and it re-checks that record before every run. That single rule is what keeps the tool inside the authorized testing lane, where it belongs.

Capabilities FAQ

Layer 4 vs layer 7 stresser — what is the difference?+

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.

How does DNS TXT target verification work?+

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.

How are API keys scoped?+

Keys are scoped with per-key task-time and slot caps, plus atomic slot reservation. A shared key cannot quietly blow through the limits set for it. Keys can be issued, rotated and revoked whenever you want.

Does the IP stresser have an API?+

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.

What does real-time monitoring show?+

A live task table, per-server breakdown, slot saturation, throughput and uptime metrics. You can watch how your target reacts as the load goes up instead of guessing from a graph after the fact.

Run the first test on your own target.

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.