DDoS attack
What Is a DDoS Attack?
A DDoS attack, or distributed denial-of-service attack, overwhelms a website, application, server, API, or network with traffic from many sources. It blocks legitimate users by exhausting bandwidth, connections, or computing capacity. Unlike a data exfiltration attack, DDoS targets availability. Legitimate traffic surges can look similar, so teams compare activity with normal patterns.
How DDoS Attacks Work
A DDoS attack does not need to break into a system. It makes the service too busy to respond.
- An attacker uses compromised devices, rented servers, or traffic-reflection services.
- These sources send coordinated requests or packets to one target.
- The traffic consumes bandwidth, connection slots, processor time, or database capacity.
- Users experience slow pages, errors, timeouts, or an outage.
The Three Main Types of DDoS Attacks
Categories describe the resource being exhausted, not only traffic volume.
| Type | Target resource | Example and symptom |
|---|---|---|
| Volumetric | Internet bandwidth | A traffic flood fills network capacity and causes slowness. |
| Protocol | Network devices or connections | Connection requests overwhelm firewalls or servers, causing timeouts. |
| Application-layer | Web application resources | Requests imitate page visits but overload expensive endpoints or APIs. |
DDoS vs. DoS and Normal Traffic Spikes
Source count is a clue, not proof. Baselines, request behavior, and infrastructure telemetry provide stronger evidence.
| Event | Source pattern | Key distinction |
|---|---|---|
| DoS | Often one source | One system attempts to exhaust a service. |
| DDoS | Many distributed sources | Filtering is harder because traffic comes from many locations. |
| Normal spike | Many real users | Demand follows expected campaigns, releases, or audience behavior. |
How to Detect and Respond to a DDoS Attack
Fast, measured action reduces disruption and preserves evidence.
- Confirm unusual latency, errors, timeouts, connection exhaustion, or request patterns.
- Preserve logs and record the start time, affected endpoints, and infrastructure signals.
- Contact the hosting, CDN, or DDoS protection provider and enable mitigation controls.
- Communicate status through an independent status page or fallback channel.
- Review the event and update thresholds, rules, and runbooks.
How to Protect a Website or Application From DDoS Attacks
No single control stops every attack. Layered defenses improve resilience.
- Use a CDN and managed DDoS protection to filter traffic before it reaches the origin server.
- Apply rate limits and web application firewall rules to sensitive pages and APIs.
- Cache common responses and allow origin traffic only from trusted proxy services.
- Use autoscaling with spending and capacity safeguards, since scaling can be costly.
- Monitor normal behavior, maintain incident runbooks, and test fallback pages.
Practical Limits of DDoS Protection
Protection is continuous engineering work, not a one-time switch.
- Aggressive blocking can reject genuine customers during legitimate demand spikes.
- Application-layer attacks often need endpoint-specific rules because they resemble normal web traffic.
- Incident plans work only when teams test alerts, provider escalation paths, and recovery steps.
- Secure, observable design should be part of building and deploying an app. Teams using an AI web app builder can include monitoring, access controls, and resilient architecture requirements from the start.
on Emergent today

