Slowloris Distributed Denial-of-Service (DDoS) Attack: Definition, damage & defense

Updated: November 20, 2026 Time to read: ~

TL;DR

A Slowloris attack is a low-bandwidth Distributed Denial-of-Service (DDoS) technique that exploits HTTP's connection model by sending partial, never-completing requests to a target server. Because the server must keep each thread open while waiting for the request to finish, a single attacker with minimal resources can exhaust a server's connection pool and take it offline. Mitigation strategies include proxy servers, connection limits per IP, slow-transfer restrictions, and timeout rules — but organizations should also work with experienced security partners to build proactive defenses.

What is a Slowloris attack and why is it so dangerous?

A Slowloris attack is remarkably dangerous. Hackers don't need an army of computers or significant bandwidth. With a little code and some spare time, they can take down a server and keep it there.

Count every item on this webpage, from the logo to the footer to the headline to the illustrations. Now, imagine asking for each element individually. Finally, put several seconds between each request you make.

You've just envisioned a Slowloris attack.

Rather than requesting every item on a page at once, hackers split up their commands. The server can't complete the request, and in time, it crashes.

Where did the Slowloris attack originate?

Any webpage you see renders through a series of Hypertext Transfer Protocol (HTTP) requests. During a Slowloris attack, hackers extend their requests and make them impossible to close. 

Anytime you visit a website, your web browser and a server start a conversation. You ask for elements on the page with a command, and the server delivers what you've requested. A server can neither initiate nor close a request. Your web browser does that work. 

In the mid-2000s, a hacker named RSnake realized this HTTP vulnerability could allow one hacker working on one machine to take down an entire web server. And that hacker wouldn't need a lot of bandwidth to make it work. Slowloris was born. 

The technique may seem simple, but it's remarkably powerful. In 2009, for example, hackers used Slowloris to take down multiple websites in Iran.  

The goal of the Slowloris is to bombard a server with multiple requests. In time, the server has too many open demands, and it crashes under the pressure. 

How does a Slowloris attack work step by step?

A typical attack follows this sequence:

  • Download code. A hacker needs help to make the Slowloris work, but the code is readily available online. 
  • Open the connection. The hacker sends many partial HTTP requests. The target opens a thread for each request. 
  • Pause the conversation. The attacker lengthens responses, sending back an update just frequently enough to keep the connection open. 
  • Open more connections. If the server continues to respond, the hacker sends more requests. 

Servers can't handle an indefinite amount of conversation. At some point, they will crash under the pressure of multiple, open requests. This Distributed Denial-of-Service (DDoS) attack lasts until the server terminates the conversation. 

Why is Slowloris so hard to detect?

Unless you catch it, a Slowloris attack can last indefinitely. And these problems are hard to spot. The traffic may seem slow, but it looks normal enough that it could slip past detection devices. The packets won't look malformed. They're just incomplete. 

Some web servers, including Apache and Microsoft Internet Information Services (IIS), are particularly vulnerable to the Slowloris.  

Can you prevent a Slowloris attack?

HTTP requests are foundation elements. You must accept them, or all of your web-based assets won't render for your employees or customers. Some vulnerability to Slowloris attacks is built into any system that runs online. 

But there are mitigation steps available, including:

Mitigation MethodHow It Helps
Proxy serversPlace a tool in front of your vulnerable servers to handle requests like this. A proxy could buy you time while you fight back.
EnhancementsDig into your setup and allow your server to take on more connections.
LimitationsRestrict how many connections you'll allow from one Internet Protocol (IP) address, and use a timer to cut off requests that take too long to complete.
RestrictionsDon't allow slow transfer connections to your server.

Applying one or more of these methods can significantly reduce your server's exposure to a Slowloris attack.

What should you do if a Slowloris attack occurs?

Despite your best work, you may experience at least one Slowloris attack. When you do, reset all of your connections and talk with your hosting provider immediately. You may need to reset preferences quickly so you can limit how long your site stays down.

Okta can help

We know that even thinking about a downed website makes you feel nervous, scared, and angry. A good offense is better than any well-planned defense. Work with a company that has years of experience in helping customers fend off threats. Contact Okta and see how we can help you.

Frequently asked questions

What makes a Slowloris attack different from a traditional DDoS attack?

Unlike traditional Distributed Denial-of-Service (DDoS) attacks that rely on massive volumes of traffic from many machines, a Slowloris attack requires only a single machine and minimal bandwidth. It works by holding many partial Hypertext Transfer Protocol (HTTP) connections open simultaneously, slowly exhausting the server's thread capacity rather than overwhelming it with raw traffic volume.

Which web servers are most vulnerable to a Slowloris attack?

Certain web servers are particularly susceptible, including Apache and Microsoft Internet Information Services (IIS). These servers are vulnerable because of how they manage open HTTP connections and threads while waiting for requests to complete.

How can you tell if your server is under a Slowloris attack?

Slowloris attacks are notoriously difficult to detect because the traffic appears slow but otherwise normal. The packets are not malformed — they are simply incomplete. This means the attack can slip past many standard detection tools, making proactive monitoring and connection-timeout rules especially important.

Can a Slowloris attack last indefinitely?

Yes — unless actively identified and stopped, a Slowloris attack can continue indefinitely. The attack persists as long as the attacker keeps sending just enough data to prevent the server from closing the open connections. The server will remain under pressure until it either crashes or the connections are forcibly terminated.

What are the most effective ways to mitigate a Slowloris attack?

Several mitigation strategies can reduce exposure: placing a proxy server in front of vulnerable servers to absorb requests, increasing the server's connection capacity, restricting the number of connections allowed from a single IP address, setting timeouts to cut off slow or incomplete requests, and blocking slow-transfer connections entirely.

What should you do immediately after experiencing a Slowloris attack?

Once an attack is identified, you should reset all open connections as quickly as possible and contact your hosting provider immediately. Acting fast to reconfigure connection limits and timeout settings is critical to minimizing downtime and preventing the attack from resuming.

References

An Overview of HTTP. (February 2021). Mozilla. 

Slowloris HTTP DoS. (April 2015). Ha.Ckers. 

Slowloris and Iranian DDoS Attacks. (June 2009). InfoSec. 

Performing a Genuine Slowloris Attack (SlowHTTP) of Indefinite Length in Kali Linux. (June 2019). Our Code World. 

Slowloris (Computer Security): Boring a Server to Death. (June 2019). Dev. 

Continue your Identity journey