What is a DDoS attack?
A distributed denial-of-service (DDoS) attack uses many compromised devices, often a botnet, to send a target more traffic or requests than it can handle, so real users cannot reach it. It differs from a plain DoS attack because the traffic comes from many sources at once, which makes it harder to trace and to block.
How a DDoS attack works
The attacker takes control of thousands of devices, then tells them all to hit the same target at the same moment. Attacks usually fall into three groups:
- Volumetric: saturate the bandwidth in front of the target. A DNS amplification attack is a classic example.
- Protocol: exhaust connection tables or load balancers with malformed or half-open connections.
- Application layer: send requests that look legitimate and are expensive to serve, as in an application layer DDoS attack or an HTTP flood.
Signs you may be under attack
- The site or one service is suddenly slow or unreachable.
- Traffic jumps without a campaign, launch or news item to explain it.
- Many requests hit the same URL, or come from the same few networks or identical clients.
- Error rates and timeouts rise while real orders or logins fall.
These signs also fit an ordinary traffic surge or a bug, so they do not prove an attack. CISA notes that watching network traffic through a firewall or intrusion detection system is the best way to confirm one.
Impact on a business
The direct cost is downtime: no sales, no sign-ups, no support. Indirect costs follow, such as lost trust, support load and emergency spend. An attack can also serve as a distraction while something else happens elsewhere, so check the rest of your systems too.
How to prepare and respond
- Put a DDoS protection service or CDN in front of the origin. See DoS protection and how to stop DDoS attacks.
- Rate-limit expensive endpoints and cache what you can.
- Write a response plan: who decides, who talks to your provider, how you communicate.
- Keep origin addresses private and restrict direct access to your provider's ranges.
- Know your normal traffic so an anomaly stands out.
Where load testing and monitoring fit
Load testing does not simulate a DDoS attack, and LoadFocus does not offer attack simulation. What it does show is your capacity limit under normal traffic: where response times climb and errors start. That tells you how much headroom you have before a surge, hostile or not, takes you down. Run a cloud load test to find that limit, and read about spike testing and load testing vs stress testing to plan the scenarios. Only test systems you own or have permission to test.
FAQ: DDoS attacks
What is the difference between DoS and DDoS?
A DoS attack comes from one source. A DDoS attack comes from many sources at once, usually a botnet, so blocking a single address does not stop it.
Can load testing protect me from a DDoS attack?
No. Load testing does not defend against attacks. It tells you how much normal traffic your system handles before it slows or fails, which helps you size capacity and set alerts. Protection comes from a DDoS mitigation service, rate limiting and a response plan.
How do I know if a traffic spike is an attack?
Look at the pattern. A legitimate spike usually matches a campaign or event and spreads across pages and regions. An attack often hits one URL, comes from a narrow set of networks or clients, and brings errors without more orders.
Does a CDN stop DDoS attacks?
A CDN absorbs and filters a large share of volumetric and request floods, but it is not complete. Keep your origin private, add rate limits, and check what your provider includes.
Related terms
- How to Stop DDoS Attacks: A Practical Guide
- What is a DNS Amplification Attack? Defence Guide
- What Is a DNS DDoS Attack?
- What Is a Memcached DDoS Attack?
- What Is a UDP Flood DDoS Attack?
- What is an Application-Layer DDoS Attack?
- What is an HTTP Flood DDoS Attack?
- What Is Denial-of-Service (DoS) Protection?
Related LoadFocus Tools
Put this concept into practice with LoadFocus, the same platform that powers everything you just read about.