DDoS attacks explained: what a small website can and cannot do about them
A DDoS attack floods a site from many machines at once, and attacks come in different shapes. How to tell one from an ordinary outage, when mitigation has to happen upstream, and what to prepare before it happens.
Your site slows to a crawl, then stops loading entirely. Is it a spike of real visitors, a hosting problem, or an attack? A distributed denial-of-service (DDoS) attack is one possibility, and knowing what it is changes what you do next. This guide covers what DDoS attacks are, how to tell one from an ordinary outage, and what a small website can realistically do - grounded in CISA's guidance and Cloudflare's learning materials.
What a DDoS attack is
A denial-of-service attack, as CISA defines it, makes a system unavailable to legitimate users by flooding the target host or network with traffic until it cannot respond or crashes. The "distributed" version runs the same play from many machines at once: attackers use botnets, groups of hijacked internet-connected devices, often including IoT devices left with default passwords or weak security. Cloudflare's explainer offers a useful analogy: an unexpected traffic jam clogging the highway so regular traffic cannot arrive. Attacks also come in different shapes: Cloudflare groups them into volumetric attacks that consume the available bandwidth, protocol attacks that exhaust server or network-equipment resources, and application-layer attacks that overwhelm the server with requests that are expensive to answer. Two details matter for small site owners. Botnets are often rented out through attack-for-hire services, so launching an attack does not require skill or a grudge. And your site can be affected without being the target at all - if your hosting or cloud provider is attacked, you feel the outage too.
Attack or ordinary outage?
The symptoms overlap with non-malicious problems: CISA lists unusually slow performance, a particular website becoming unavailable, or an inability to access any website, and notes these can also come from technical issues or maintenance. Detection is ultimately about traffic, not vibes: network traffic monitoring and analysis, with alerts on anomalous load, is how an attack is confirmed. This is one more reason to have basic uptime monitoring in place, as our monitoring guide covers - an alert that fires at the same moment your traffic graph goes vertical is different evidence than a quiet timeout.
What helps, and where
Where mitigation has to happen depends on the attack's shape. A volumetric flood works by consuming the available bandwidth itself, and once the link is full, nothing on your server can filter a way out of that - the traffic has to be absorbed or screened upstream. CISA's recommendation for reducing the effects of an attack is a protection service that detects abnormal traffic flows, filters out the attack traffic and passes clean traffic on. Other shapes leave more room to act locally: protocol and application-layer attacks exhaust resources rather than bandwidth alone, and while capacity permits, measures like rate limiting and rule-based filtering can absorb part of the pressure - Cloudflare lists both rate limiting and web application firewalls among its mitigation strategies, alongside anycast distribution. Local measures complement upstream protection; they do not replace it for the volumetric case. For small sites, this kind of protection may already be part of a CDN, hosting plan or security service rather than a separate purchase; our CDN and WAF guides cover those layers. The practical homework is checking what your current provider includes and how to reach them quickly, before you need it. CISA also recommends a disaster recovery plan so that communication, mitigation and recovery are decided in advance rather than improvised mid-incident.
If it happens to you
CISA's advice is to contact the appropriate technical professionals rather than fight a flood alone: your host or network administrator can investigate traffic data for evidence of an attack, an internal issue or maintenance - evidence, not a guarantee that every cause can be identified - and apply filtering rules or reroute traffic through a protection service. Note when the problem started and what changed - a launch, a news mention, a new campaign - because genuine traffic spikes are also real, and the response differs. There is no way to completely avoid becoming a target, as CISA puts it; the goal is reducing the effects, not achieving immunity.
Not being part of the problem
Botnets are made of other people's compromised devices, and any internet-connected equipment you own - including cameras, routers and other IoT hardware - can be drafted the same way. CISA's hygiene advice applies here: install and maintain antivirus software, use a firewall, change default passwords, and follow good security practices on anything you connect. A DDoS arms race is fought partly with other people's neglected gadgets; yours should not be among them.
FAQ
My site is down. Is it a DDoS attack?
Probably not, but possibly. CISA notes that attack symptoms can resemble technical problems or maintenance. The way to know is traffic analysis, not guesswork: check your provider's status page, then ask them to look at traffic patterns if the outage is unexplained. Basic uptime monitoring helps you know the moment availability changes.
Why would anyone attack a small website?
Attack-for-hire services make launching an attack cheap and skill-free, so motives range from competition to boredom, and some attacks are essentially random. Your site can also be caught in the blast radius of an attack on your hosting or cloud provider, with no one targeting you at all.
Can my own server or firewall stop a DDoS attack?
It depends on the attack's shape. A volumetric flood saturates the connection itself - by the time requests reach your server, the pipe can already be full, which is why CISA points to protection services that filter traffic upstream. Protocol and application-layer attacks exhaust resources instead, and there local measures can help while capacity holds: rate limiting and rule-based filtering are among the mitigation strategies Cloudflare lists. Local filtering complements upstream protection rather than replacing it.
Does DDoS protection make attacks impossible?
No. CISA is explicit that there is no way to completely avoid becoming a target of a DoS or DDoS attack. Protection services and a recovery plan reduce the effects - shorter outages, cleaner traffic, faster response - rather than preventing attacks from being attempted.