DDoS Attacks Explained:What Small Sites Can Realistically Do
What a DDoS attack is, which kinds actually affect small websites, and the realistic protections available: CDNs and proxies, rate limits, caching, your host's network defences and a response plan.

Table of Contents
A DDoS (distributed denial of service) attack tries to make a website or service unavailable by overwhelming it with traffic or requests from many sources at once. Small websites are most often affected by application-layer floods (many requests to pages that are expensive to generate) and occasionally by large network floods aimed at the hosting provider. Realistic protection combines a CDN or reverse proxy in front of the site, caching, rate limits, and your hosting provider's network defences, plus a plan for what to do when it happens.
Types of DDoS attacks
| Layer | What it targets | Examples | Who can stop it |
|---|---|---|---|
| Network/volumetric | Bandwidth and network equipment | UDP floods, amplification attacks | Hosting provider, network or DDoS mitigation service |
| Protocol | Server and network state tables | SYN floods | Provider, firewalls, mitigation services |
| Application (Layer 7) | The website itself | Floods of page, search or login requests | CDN/WAF, rate limits, caching, application tuning |
Volumetric attacks can reach far more traffic than any single server's connection can carry, so they must be stopped upstream. Application-layer attacks can be small in bandwidth but very effective against uncached, expensive pages.
Why small sites get hit
- Extortion attempts or competitors.
- Grudges against a business or a news story.
- Being on the same network as a target.
- Abusive bots and scrapers that behave like a low-grade DDoS, even without intent.
Realistic protections
1. Put a CDN or reverse proxy in front
Services that proxy your traffic (often combined with a CDN) absorb large volumes across their global network, hide your origin server's IP address, and filter malicious traffic before it reaches you. Many offer basic DDoS protection in free or low-cost plans. See how to set up Cloudflare DNS as one example.
Important: once proxied, keep your origin IP private and restrict the origin to accept web traffic only from the proxy, or attackers can bypass it.
2. Cache aggressively
Pages served from cache cost almost nothing to deliver. A flood of requests to cached pages is far less damaging than one hitting PHP and the database. See website caching explained.
3. Rate-limit expensive endpoints
Limit requests per IP to logins, search, carts, APIs and other uncached URLs. Use a web application firewall or server rules; see what is a web application firewall.
4. Know your host's protections
Ask your hosting provider what network-level DDoS mitigation it provides, what happens to your site during a large attack (some providers temporarily null-route targeted IPs to protect other customers), and how to contact them during an incident.
5. Reduce the attack surface
- Close unused ports and services; see Linux firewall basics.
- Remove or protect endpoints that are expensive and unnecessary.
- Keep software updated so that small floods do not trigger crashes.
Example: an application-layer flood on a search page
A local news site slows to a crawl on Sunday afternoon. Traffic graphs show requests ten times higher than normal, but mostly to URLs like /?s=random-words-123 from thousands of different IP addresses. Every search result page is generated fresh, querying the database, so the server's PHP workers and database are overwhelmed.
The response:
- Enable the CDN/proxy's challenge mode for the site temporarily, which stops most automated clients.
- Add a rate-limiting rule for requests containing
?s=: a few searches per minute per IP. - Make sure normal article pages are fully cached, so legitimate readers are served from the cache.
- Afterwards, consider a search service or tighter limits on expensive endpoints, and keep the origin IP private.
Total bandwidth was modest; the attack worked because each request was expensive. Caching and rate limits addressed exactly that.
Preparing before it happens
- Know how to switch on your proxy's "under attack" mode and who has the login.
- Keep the origin IP private and allow only the proxy to reach it.
- Make sure expensive endpoints have rate limits.
- Keep your host's emergency contact details at hand.
- Have an alternative way to reach customers if the site is unavailable.
Recognising an attack
- Sudden traffic spikes not explained by marketing or news.
- Many requests to the same URLs, often with unusual user agents or patterns.
- The site slowing down or returning 503/508 errors.
- Your host notifying you about abnormal traffic.
Check access logs and your CDN's analytics; see troubleshooting a slow or unresponsive server.
What to do during an attack
- Confirm it is an attack, not legitimate traffic or a broken process.
- Contact your hosting provider.
- If you use a proxy/CDN, enable its stronger "under attack" or challenge modes.
- Add temporary rate limits or blocks for the patterns you see.
- Keep customers informed through another channel if the site is down.
- Afterwards, review what worked and strengthen your setup.
Frequently Asked Questions
Can a firewall on my server stop DDoS attacks?
It can help against small floods and abusive clients, but not against attacks that fill the network connection before traffic reaches the server.
Is DDoS protection expensive?
Basic protection through CDNs and hosting providers is often included or inexpensive. Dedicated protection for very large attacks costs more.
Will a DDoS attack steal my data?
DDoS aims at availability, not data theft, though attackers sometimes use it as a distraction. Keep other security measures in place.
Related reading
DDoS defence is one layer of website security basics. For hosting built for resilience, see ServerNeed cloud hosting.
Sources
Last updated 7 October 2026



