DDoS Attack Types

Learn the main DDoS attack types, including volumetric, protocol, application-layer, and multi-vector attacks. Understand how they work, how to detect them, and which mitigation strategies help protect infrastructure and applications.

DDoS (Distributed Denial of Service) attacks flood target systems with malicious traffic to exhaust resources and deny service to legitimate users. Attack types range from volumetric floods that consume bandwidth to application-layer attacks that target specific services, each requiring different detection and mitigation strategies.

Last updated: 2026-06-03

How DDoS Attacks Work

DDoS attacks leverage distributed sources—typically botnets of compromised devices—to generate overwhelming traffic volumes. The goal is to exhaust bandwidth, compute resources, or connection capacity, rendering the target unavailable.

┌─────────────────────────────────────────────────────────────────┐
│ DDoS Attack Architecture │
│ │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ Bot 1 │ │ Bot 2 │ │ Bot 3 │ │ Bot ... │ │ Bot N │ │
│ │ (IoT) │ │ (Server)│ │ (PC) │ │ │ │ (Mobile)│ │
│ └────┬────┘ └────┬────┘ └────┬────┘ └────┬────┘ └────┬────┘ │
│ │ │ │ │ │ │
│ └───────────┴───────────┼───────────┴───────────┘ │
│ │ │
│ ┌──────▼──────┐ │
│ │ C&C │ │
│ │ Server │ │
│ └──────┬──────┘ │
│ │ Attack command │
│ ▼ │
│ ┌──────────────┐ │
│ │ Target │ │
│ │ Server │◀─── Overwhelming traffic│
│ │ (Victim) │ │
│ └──────────────┘ │
└─────────────────────────────────────────────────────────────────┘

DDoS Attack Classification

DDoS attacks target different layers of the OSI model, each with distinct characteristics and mitigation approaches.

LayerAttack TypeTargetPrimary Impact
3-4VolumetricBandwidthNetwork saturation
3-4ProtocolState tablesResource exhaustion
7ApplicationApplication logicService unavailability

1. Volumetric Attacks (Layer 3-4)

Overwhelm network bandwidth with massive traffic volumes.

Attack TypeMechanismTypical VolumeDetection
UDP FloodRandom UDP packets to random ports10-1000+ GbpsTraffic volume spike
ICMP FloodPing requests overwhelm target1-100 GbpsICMP rate
AmplificationReflected traffic from third parties10-700 GbpsSource port/protocol
DNS AmplificationDNS responses amplified 70x10-500 GbpsDNS response ratio
NTP AmplificationNTP monlist responses 100x10-400 GbpsNTP traffic pattern
SSDP AmplificationUPnP discovery responses 30x5-200 GbpsSSDP source ports

UDP Flood Example:

Source: Random IPs (spoofed)
Destination: Target server
Port: Random ports
Packet size: Large UDP datagrams
Volume: 50-500 Gbps typical
Impact: Bandwidth saturation, packet loss

Amplification Attack Flow:

Attacker ──(small request)──▶ Public Server ──(large response)──▶ Victim
Example DNS Amplification:
Attacker sends: 60-byte DNS query (spoofed source = victim IP)
Server responds: 4000-byte DNS response to victim
Amplification factor: ~70x

2. Protocol Attacks (Layer 3-4)

Exploit weaknesses in network protocols to exhaust server resources.

Attack TypeMechanismResource TargetDetection
SYN FloodIncomplete TCP handshakesConnection tableSYN/ACK ratio
ACK FloodACK packets to non-existent connectionsFirewall CPUInvalid ACKs
SYN-ACK FloodSpoofed SYN-ACK responsesConnection trackingUnexpected SYN-ACKs
FIN/RST FloodAbnormal connection terminationState tablesFIN/RST rate
Smurf AttackICMP to broadcast addressesNetwork bandwidthBroadcast traffic
Ping of DeathOversized ICMP packetsLegacy systemsLarge ICMP

SYN Flood Example:

Normal TCP Handshake:
Client ──SYN──▶ Server
Client ◀─SYN-ACK─ Server
Client ──ACK──▶ Server (Connection established)
SYN Flood Attack:
Attacker ──SYN──▶ Server (spoofed IP)
Server ◀─SYN-ACK─ (goes nowhere)
Attacker ──SYN──▶ Server (spoofed IP)
Server ◀─SYN-ACK─ (goes nowhere)
... (thousands more)
Result: Server's connection table fills with half-open connections
Memory exhausted, legitimate connections fail

SYN Flood Metrics:

MetricNormalUnder Attack
SYN packets/sec100-100010,000-1,000,000+
SYN/ACK ratio~1:110:1 to 1000:1
Half-open connections<10010,000-1,000,000
Connection failures<1%50-100%

3. Application Layer Attacks (Layer 7)

Target specific application functions with seemingly legitimate requests.

Attack TypeMechanismTarget ResourceDetection
HTTP FloodMassive GET/POST requestsWeb serverRequest rate/pattern
SlowlorisSlow HTTP header transmissionConnection poolsSlow header rate
Slow POSTSlow request body transmissionServer threadsLong request duration
HTTP RegexExpensive regex in requestsCPUCPU spike pattern
Hash CollisionSpecially crafted inputsCPU/memoryResource spike
DNS Water TortureRandom subdomain queriesDNS serverNXDOMAIN rate
SSL RenegotiationRepeated SSL handshakesCPUSSL handshake rate

HTTP Flood Example:

GET / HTTP/1.1
Host: target.com
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64)...
Accept: text/html,application/xhtml+xml...
[Repeated thousands of times from distributed sources]

Slowloris Attack Flow:

Attacker opens 100+ connections to server
Sends partial HTTP headers slowly:
Connection 1: "GET / HTTP/1.1\r\nHost: target.com\r\nX-Header1: a"
Connection 2: "GET / HTTP/1.1\r\nHost: target.com\r\nX-Header1: b"
...
Every 10-15 seconds, sends additional header data to keep connection alive
Server keeps connections open waiting for complete headers
Connection pool exhausted, legitimate users cannot connect

4. Multi-Vector Attacks

Combine multiple attack types simultaneously to overwhelm defenses.

CombinationStrategyComplexity
Volumetric + ApplicationSaturate bandwidth while targeting appMedium
SYN Flood + HTTP FloodExhaust connections and app resourcesMedium
Amplification + ProtocolNetwork saturation + state exhaustionHigh
All three typesMaximum disruptionVery High

Attack Duration and Scale Statistics

MetricTypical RangeNotable Extremes
Duration10 min - 2 hours24+ hours (sustained)
Bandwidth1-100 Gbps3.47 Tbps (AWS, 2020)
Packets/sec1-50 Mpps809 Mpps (2024)
Requests/sec1K-1M RPS71M RPS (HTTP/2, 2023)
Concurrent attacks1-3 types12+ types simultaneously

Attack Frequency (2025):

  • 15+ million DDoS attacks per year globally
  • Average of 41,000 attacks per day
  • 25% of attacks exceed 100 Gbps
  • Average duration: 30 minutes
  • 60% target web applications (Layer 7)

When Each Attack Type Occurs

Volumetric Attacks:

  • Often used for extortion (pay to stop)
  • Launched by large botnets (100K+ devices)
  • Peak during business hours for maximum impact
  • Common against gaming, gambling, e-commerce

Protocol Attacks:

  • Target infrastructure (firewalls, load balancers)
  • Exploit stateful devices with connection tracking
  • Effective against unprepared network gear
  • Common against enterprise infrastructure

Application Attacks:

  • Target specific applications or APIs
  • Lower volume but higher precision
  • Harder to detect (looks like legitimate traffic)
  • Common against financial services, SaaS, healthcare

Detection Methods

Volume-Based Detection

MethodHow It WorksDetection Time
Traffic thresholdAlert when >X GbpsSeconds
Baseline deviationCompare to historical baselineMinutes
Flow analysisNetFlow/sFlow monitoringSeconds

Behavioral Detection

MethodHow It WorksDetection Time
Request pattern analysisDetect unusual patternsSeconds-minutes
Source IP correlationIdentify coordinated sourcesMinutes
User agent analysisDetect bot signaturesReal-time
Connection ratio analysisSYN/ACK imbalancesReal-time

Machine Learning Detection

MethodAccuracyDetection Time
Anomaly detection90-95%Seconds
Classification models95-99%Real-time
Deep learning97-99%Real-time

Mitigation Strategies

Volumetric Attack Mitigation

TechniqueHow It WorksLatency Impact
Traffic scrubbingFilter attack traffic at scrubbing center10-50ms
BGP routingRoute traffic through mitigation providerVariable
AnycastDistribute traffic across global networkReduces congestion
Rate limitingLimit traffic per source IP<1ms

Protocol Attack Mitigation

TechniqueHow It WorksEffectiveness
SYN cookiesStateless SYN handlingHigh for SYN floods
Connection limitingLimit connections per sourceMedium-High
TCP interceptProxy TCP connectionsHigh
Firewall rulesDrop known attack patternsMedium

Application Attack Mitigation

TechniqueHow It WorksEffectiveness
WAF rulesBlock malicious request patternsHigh
Rate limiting per URILimit requests to specific endpointsHigh
CAPTCHA challengesVerify human usersMedium-High
Bot detectionIdentify and block bot trafficHigh
Connection timeoutClose slow connectionsHigh for Slowloris

Common Mistakes and Fixes

Mistake: Relying only on on-premises mitigation Fix: Use cloud-based DDoS protection for volumetric attacks that exceed your bandwidth

Mistake: No baseline traffic analysis Fix: Establish traffic baselines to detect anomalies quickly; know your normal patterns

Mistake: Mitigating only at Layer 3-4 Fix: Layer 7 attacks require application-layer defenses (WAF, rate limiting, bot detection)

Mistake: No incident response plan Fix: Document DDoS response procedures, escalation paths, and communication templates

Mistake: Manual mitigation only Fix: Implement automated detection and mitigation to respond in seconds, not minutes

Mistake: Testing mitigation only during attacks Fix: Conduct regular DDoS simulation exercises to validate defenses

DDoS Attack Quick Reference

Attack TypeLayerVolumeDetectionMitigation
UDP Flood3-4HighTraffic spikeScrubbing, rate limit
DNS Amplification3-4Very HighDNS traffic ratioScrubbing, anycast
SYN Flood4Medium-HighSYN/ACK ratioSYN cookies
HTTP Flood7Low-MediumRequest patternWAF, rate limit
Slowloris7LowConnection durationTimeout, WAF
DNS Water Torture7Low-MediumNXDOMAIN rateDNS hardening

Frequently Asked Questions

What is the difference between DDoS and DoS? DoS (Denial of Service) originates from a single source. DDoS (Distributed Denial of Service) uses multiple sources—typically thousands of compromised devices—to generate attack traffic, making it harder to block.

What is a botnet? A botnet is a network of compromised computers, IoT devices, or servers controlled by an attacker. Botnets generate DDoS traffic, send spam, or perform other malicious activities without the device owners’ knowledge.

How do amplification attacks work? Amplification attacks send small requests to public servers with spoofed source IPs (the victim’s address). The servers send large responses to the victim, amplifying the traffic 10-700x. Common amplification protocols include DNS, NTP, and SSDP.

Why are Layer 7 attacks harder to detect? Layer 7 attacks use legitimate HTTP/HTTPS requests that appear normal to network devices. They don’t require massive bandwidth, making them harder to distinguish from legitimate traffic. They target specific application functions, requiring application-aware detection.

How long do DDoS attacks typically last? Most DDoS attacks last 10-60 minutes. However, sophisticated attacks can persist for hours or days, especially extortion-driven attacks. Extended attacks require sustained mitigation capability.

Can small websites be DDoS targets? Yes. DDoS-for-hire services make attacks affordable ($5-50), so even small sites are targeted. Common motivations include extortion, competition, and ideological attacks. No site is too small to need protection.

What is the cost of DDoS downtime? Average cost: $5,600-9,000 per minute of downtime (Gartner). Costs include lost revenue, productivity, remediation, and reputation damage. Extended attacks can cost millions.

How do I distinguish a traffic spike from a DDoS attack? Traffic spikes from legitimate events (product launches, viral content) show normal request patterns. DDoS attacks show anomalous patterns: unusual source distribution, repetitive requests, known attack signatures, or protocol violations.

Should I pay a DDoS extortion demand? Law enforcement and security experts recommend against paying. Payment encourages future attacks and doesn’t guarantee the attack will stop. Instead, implement DDoS protection and report to authorities.

What is DDoS mitigation as a service? DDoS mitigation services provide cloud-based traffic scrubbing. During attacks, traffic routes through the provider’s network where malicious traffic is filtered. Clean traffic reaches your servers. Providers include cloud platforms, CDNs, and specialized security companies.

How This Applies in Practice

DDoS protection requires a layered approach:

  1. Network edge: Volumetric attack detection and scrubbing
  2. Infrastructure: Protocol attack mitigation (SYN cookies, connection limits)
  3. Application: Layer 7 protection (WAF, rate limiting, bot detection)

Most organizations use a combination of on-premises equipment for immediate response and cloud-based services for large volumetric attacks. The key is automated detection and mitigation—attacks can overwhelm systems in seconds, leaving no time for manual intervention.

How to Implement on Azion

Azion provides integrated DDoS protection across all layers:

  1. Network Layer Protection: Automatic volumetric attack mitigation at edge locations
  2. Protocol Protection: SYN cookie support and connection limiting
  3. Application Protection: WAF with rate limiting and bot detection for Layer 7 attacks
  4. Global Distribution: Anycast network distributes attack traffic across multiple locations

Azion’s edge platform detects and mitigates DDoS attacks close to the source, protecting your origin infrastructure while maintaining availability for legitimate users.

Learn more in the Azion Documentation.


Sources:

  • Cloudflare. “DDoS Threat Report 2025.”
  • NETSCOUT. “Threat Intelligence Report.” 2025.
  • Radware. “Global Application & Network Security Report.” 2025.
  • Link11. “DDoS Statistics and Trends.” 2025.
  • NIST. “Guide to DDoS Attacks.” SP 800-83.
stay up to date

Subscribe to our Newsletter

Get the latest product updates, event highlights, and tech industry insights delivered to your inbox.