content="2026-06-10T09:00:00+00:00">

Types of DDoS Attacks Explained: L3, L4, L7, Amplification & More

806 views · likes · 14 shares
Share on
18 min read
Types of DDoS Attacks Explained: L3, L4, L7, Amplification & More

Key Takeaways

  • DDoS attacks are categorised into three layers: Volumetric (L3), Protocol (L4), and Application (L7) - each targeting different infrastructure.
  • Amplification attacks exploit public servers to multiply traffic by 28x to 51,000x, turning small bandwidth into devastating floods.
  • Application-layer (L7) attacks are the hardest to stop because each request looks legitimate, they require bot detection and behavioural analysis.
  • Modern attacks are multi-vector: they combine volumetric flooding with protocol exhaustion and L7 attacks simultaneously.
  • Each attack type requires different mitigation: anycast networks absorb volume, stateful firewalls block protocol attacks, and bot management + WAF handle L7.

Understanding the different types of DDoS attacks is essential for building effective defences. Each attack type exploits different vulnerabilities, targets different infrastructure layers, and requires different mitigation strategies. An attack that overwhelms your bandwidth requires a completely different response than one that exhausts your web server's connection pool.

This guide breaks down every major DDoS attack category, explains how each works, and maps the specific defences needed to stop them.

DDoS Attack Categories Overview

CategoryOSI LayerTargetExamplesSize
VolumetricLayer 3Network bandwidthUDP flood, ICMP flood100 Gbps to 5+ Tbps
AmplificationLayer 3/4Bandwidth via reflectionDNS, NTP, Memcached amp50 Gbps to 3+ Tbps
ProtocolLayer 4Server/firewall resourcesSYN flood, ACK floodMillions of packets/sec
ApplicationLayer 7Web server/applicationHTTP flood, SlowlorisThousands of requests/sec

Volumetric Attacks (Layer 3)

Volumetric attacks aim to consume all available bandwidth between the target and the internet. They generate massive traffic volumes measured in Gbps (gigabits per second) or Tbps (terabits per second).

UDP Flood

Sends a massive number of UDP packets to random ports on the target. The server must check for listening applications on each port and reply with ICMP "destination unreachable" - consuming bandwidth and processing resources. UDP is connectionless, making it easy to spoof source IPs and difficult to filter.

Defence: Rate limiting UDP traffic, blackholing non-essential UDP ports, anycast network distribution to absorb volume across multiple data centres.

ICMP (Ping) Flood

Sends overwhelming numbers of ICMP echo request (ping) packets. The target must process each request and send echo replies, consuming both bandwidth and CPU. Also known as a "Ping of Death" when using oversized packets.

IP Fragmentation Flood

Sends fragmented IP packets that the target must reassemble. The reassembly process consumes memory and CPU. Overlapping fragments can crash vulnerable systems. Particularly effective against firewalls that must reassemble packets for inspection.

Amplification Attacks

Amplification attacks exploit third-party servers to multiply attack traffic. The attacker sends small requests with a spoofed source IP (the victim's IP) to vulnerable servers. These servers respond with much larger replies directed at the victim.

VectorAmplification FactorProtocolHow It Works
Memcached10,000-51,000xUDP 11211Exploit misconfigured Memcached servers; "stats" command returns massive data
NTP556xUDP 123"monlist" command returns list of last 600 clients connected
DNS28-54xUDP 53"ANY" queries against domains with large DNS records
SSDP30xUDP 1900Exploit Universal Plug and Play (UPnP) devices on the internet
CLDAP56-70xUDP 389Exploit publicly accessible LDAP servers
CharGEN358xUDP 19Legacy character generation protocol, sends random characters
SNMP6.3xUDP 161Exploit publicly accessible SNMP agents
Why amplification is devastating: A Memcached amplification attack turns 1 Gbps of attacker bandwidth into 51 Tbps of attack traffic hitting the victim. The largest recorded DDoS attack (5.6 Tbps, 2024) used amplification vectors. Even modest attacker resources can generate catastrophic traffic volumes.

Protocol Attacks (Layer 4)

Protocol attacks exploit weaknesses in network protocol implementations to exhaust server resources, connection tables, firewalls, load balancers, and session state tracking.

SYN Flood

The most common protocol attack. Exploits the TCP three-way handshake: the attacker sends millions of SYN packets with spoofed source IPs. The server responds with SYN-ACK and waits for the final ACK that never comes. Each half-open connection consumes memory in the server's connection table until it's full, blocking legitimate connections.

Defence: SYN cookies (stateless SYN handling), increase backlog queue size, reduce SYN-RECEIVED timer, and deploy hardware-based SYN flood mitigation at the network edge.

ACK Flood

Sends massive volumes of TCP ACK packets. Whilst the server can quickly determine these ACK packets don't belong to any active connection, the processing still consumes CPU. Particularly effective against stateful firewalls that must track every packet against their connection tables.

RST Flood

Sends spoofed TCP RST (reset) packets to terminate active connections between the target and its legitimate users. If the attacker can guess active connection parameters, they can disconnect real users.

TCP Connection Flood

Completes full TCP handshakes, establishing thousands of connections that are never used. Unlike SYN floods, these are complete connections that survive SYN cookie defences. Each connection consumes server memory and file descriptors until limits are reached.

Application-Layer Attacks (Layer 7)

Application-layer attacks are the most sophisticated and hardest to mitigate because each request appears legitimate.

HTTP GET Flood

Sends massive numbers of HTTP GET requests to the target website. Each request is valid HTTP, making it difficult to distinguish from legitimate traffic. Attackers target resource-heavy pages: search pages, product listings, dynamic content that requires database queries.

HTTP POST Flood

Similar to GET floods but uses POST requests, typically targeting login forms, registration endpoints, contact forms, or APIs. POST processing is generally more resource-intensive than GET, making this more efficient per request.

Slowloris

Opens many connections to the target and sends partial HTTP requests very slowly, never completing them. Each connection holds a server thread open indefinitely. With enough slow connections, the server exhausts its connection pool and can't serve new requests. Devastatingly effective against Apache servers.

Slow POST (R.U.D.Y.)

"R U Dead Yet" sends HTTP POST requests with a legitimate Content-Length header but transmits the body data one byte at a time, very slowly. The server keeps the connection open waiting for the complete body, consuming a thread/worker for each slow request.

HTTP/2 Rapid Reset

A newer attack exploiting HTTP/2's stream multiplexing. The attacker opens and immediately resets streams at high speed, forcing the server to process each stream setup and teardown. Discovered in October 2023, it generated the then-largest DDoS attack at 398 million requests per second.

WordPress XML-RPC

Exploits WordPress's pingback feature to amplify L7 attacks. Attackers send pingback requests from thousands of WordPress sites to the victim, creating a distributed L7 flood that appears to come from legitimate WordPress installations.

Under DDoS Attack? Get Immediate Protection

Unled Network provides emergency DDoS mitigation with up to 10 Tbps capacity. L3/L4/L7 protection, bot management, and 24/7 incident response for businesses under attack.

Emergency Response ->

Multi-Vector Attacks

Modern DDoS attacks rarely use a single vector. Sophisticated attackers combine multiple attack types simultaneously:

Ransom DDoS (RDoS)

RDoS combines DDoS attacks with extortion. Attackers send a ransom demand (usually requesting cryptocurrency) and threaten a sustained DDoS attack if payment isn't made. Some groups demonstrate capability with a short initial attack before demanding payment.

Never pay ransom: Payment doesn't guarantee the attack will stop, and it marks your organisation as a willing payer for future attacks. Instead, deploy proper DDoS protection, it's cheaper than any ransom and provides permanent defence.

Mitigation by Attack Type

Attack TypePrimary DefenceSecondary Defence
Volumetric (UDP, ICMP)Anycast network / CDN with massive bandwidthBGP blackholing (last resort)
Amplification (DNS, NTP)Upstream filtering, scrubbing centresBlock spoofed traffic (BCP38)
SYN FloodSYN cookies, hardware mitigationIncrease backlog, tune kernel params
Connection FloodConnection limits per IP, timeoutsLoad balancers with connection mgmt
HTTP FloodBot management, JS challengesRate limiting, WAF rules
Slowloris/Slow POSTReverse proxy (nginx), connection timeoutsLimit concurrent connections per IP
HTTP/2 Rapid ResetPatched HTTP/2 implementationsRate limit stream creation

Real-World Attack Examples

DateTarget/SizeAttack TypeNotable Detail
Oct 20245.6 Tbps (Cloudflare)UDP amplificationLargest recorded DDoS attack
Oct 2023398M rps (Google/Cloudflare/AWS)HTTP/2 Rapid ResetNew L7 attack vector discovery
Jun 202226M rps (Cloudflare)HTTPS flood (botnet)5,067 devices generating 212M rps
Feb 20202.3 Tbps (AWS)CLDAP reflectionLargest recorded at the time
Mar 20181.7 Tbps (Arbor)Memcached amplificationFirst major Memcached DDoS
Oct 20161.2 Tbps (Dyn DNS)Mirai botnetIoT botnet took down DNS for major sites

Building Comprehensive Protection

No single solution handles all DDoS attack types. Build a layered defence:

  1. Network layer: DDoS-protected hosting with anycast network and scrubbing centres for volumetric/protocol attacks
  2. CDN/Proxy layer: Cloudflare, Akamai, or AWS Shield to absorb and filter traffic globally
  3. Application layer: WAF rules to detect and block L7 attack patterns
  4. Bot detection: Bot management with fingerprinting for sophisticated L7 attacks
  5. Rate limiting: Intelligent per-IP and per-endpoint throttling
  6. Monitoring: Real-time traffic analysis with automated alert escalation

Enterprise DDoS Protection for Every Attack Type

Our infrastructure handles volumetric, protocol, and application-layer attacks with up to 10 Tbps mitigation capacity. Always-on protection, 24/7 monitoring, and expert incident response.

Telegram: @unlednetwork →    WhatsApp Us →

Comments

Have a question or a first-hand experience with this? Join the conversation. Your email is never shown or shared.

    Maria S.

    We implemented this last month and already seeing positive signals.

    Author

    Thanks for the feedback. Based on our experience across hundreds of accounts, this approach shows results within 2-4 weeks.

Join the conversation

No HTML. Comments are moderated; they appear after review.

What You Get

High Trust Score

Pre-established account with positive activity history and cleared standing

Ready to Spend

Skip the warm-up phase - accounts are ready for immediate campaign launch

High Spend Ceiling

Elevated daily and monthly spend limits from day one

30-Day Replacement

Full replacement if account triggers suspension within 30 days

24h Delivery

Credentials delivered within 24 hours of payment confirmation

Dedicated Support

Direct Telegram/WhatsApp line to your account manager

WhatsApp Telegram