What a DDoS attack is, in plain words
Imagine a shop with one door. A denial-of-service attack is a crowd of people who block the door without buying anything, so real customers cannot get in. A distributed denial-of-service (DDoS) attack uses thousands of machines at once — usually hacked computers, routers, cameras and cloud servers rented with stolen cards, controlled together as a 'botnet' — so the traffic cannot be stopped by blocking one address.
DDoS attacks are not rare and not only aimed at banks. Cloudflare reported mitigating 20.5 million DDoS attacks in the first quarter of 2025 alone, and in 2025 it described blocking an attack that peaked at 7.3 terabits per second, among the largest ever recorded. Most attacks are much smaller and short, but even a modest one can take down an unprotected small-business server for hours — during a sale, a launch or a results day.
The main types of DDoS attack on websites
Attacks are usually grouped by the layer of the network they target:
| Type | How it works | What it targets | Main defence |
|---|---|---|---|
| Volumetric flood (UDP, amplification) | Huge volumes of junk traffic, often reflected off open servers | The network link itself | Upstream scrubbing / CDN such as Cloudflare |
| Protocol attack (SYN flood) | Half-open connections that exhaust the server's connection tables | Firewall and operating system | SYN cookies, connection limits per IP |
| Application (layer 7) flood | Many real-looking HTTP requests to heavy pages, search or login | The web server, PHP and database | Per-visitor rate limits, caching, bot rules |
| Slow attacks (Slowloris) | Connections opened and kept alive by sending data very slowly | Web server connection slots | Short header and body timeouts, connection caps |
| Brute force and credential stuffing | Thousands of login attempts on wp-login.php or xmlrpc.php | Logins and CPU | Blocking xmlrpc, login rate limits, automatic bans |
| Scanners and exploit bots | Automated probes for .env, .git, backups and known bugs | Leaked files and weak plugins | Blocking sensitive paths, automatic bans |
For small and medium websites, the application-layer attacks and bot traffic are by far the most common. A WordPress site does not need a terabit attack to fall over: a few hundred requests a second to uncached pages, or a brute-force run on xmlrpc.php, can push the server's load high enough that every site on it slows down. That is exactly what we saw on our own servers in November 2026 — and why we built the protection described below.
Signs your website is under attack
Not every slowdown is an attack, but these patterns point to one:
- The site suddenly becomes very slow or shows 502, 503 or 504 errors, while nothing was changed.
- Analytics or server logs show a sudden spike in requests, often to one page such as /wp-login.php, /xmlrpc.php or a search URL.
- Thousands of requests come from many unrelated IP addresses with similar browser strings.
- Server load climbs far above normal while real visitor numbers stay the same.
- Your host or CDN emails you about unusual traffic or rate limiting.
Fix 502, 500, 503 and 504 errors →
How DDoS-protected hosting works, layer by layer
No single setting stops every attack. Good protection stacks several defences so that what gets past one is caught by the next. This is how it is done on Cloud Ninza servers:
1. Network and operating system
SYN cookies and larger connection backlogs keep the server answering during SYN floods; reverse-path filtering drops spoofed packets; packets with impossible TCP flags are discarded. A dedicated firewall table limits new connections per IP address for web, mail, DNS and SSH traffic and caps how many connections one address may hold open.
2. Web server
Every visitor is limited to a steady rate of requests per second with a burst allowance for normal page loads, and to a maximum number of simultaneous connections. Short header and body timeouts close slow connections, which defeats Slowloris-style attacks. Visitors over the limit get a 429 'too many requests' answer instead of tying up PHP.
3. Bot and brute-force rules
xmlrpc.php — the WordPress file most abused for brute-force and amplification — is blocked. Automatic jails ban an address for 24 hours after repeated failed WordPress logins, after probing for files such as .env, .git or phpunit, and for an hour after repeated rate-limit hits; repeat offenders are banned for longer. Bans apply at both the web server and the firewall, and work correctly behind Cloudflare by reading the real visitor IP.
4. Caching
Every WordPress site has a page cache, so most page views are answered from memory in milliseconds without starting PHP or touching the database. An attack on cached pages costs the server very little.
5. Edge network (CDN)
A volumetric attack larger than the server's own internet link can only be absorbed upstream. Putting a domain behind Cloudflare's free plan (proxied, SSL mode Full (strict)) adds Cloudflare's unmetered DDoS protection in front of the server. We recommend it for every customer domain, and our own sites run behind it.
We are open about that last point because it matters: no single server, at any host, can survive an attack bigger than its network link on its own. Hosting that claims 'unlimited DDoS protection' either means an upstream scrubbing service or is overpromising. The honest answer is layered protection on the server plus a CDN in front.
How to protect a WordPress site from DDoS and bots
WordPress is the most attacked platform simply because it is the most used. These steps cut most risk:
- Keep WordPress core, themes and plugins updated; delete what you do not use.
- Turn on page caching (on Cloud Ninza it is on by default; Ninza Speed manages it from wp-admin).
- Block or limit xmlrpc.php unless a specific app needs it.
- Use strong, unique admin passwords and two-step login; rename the default 'admin' user.
- Put the domain behind Cloudflare (proxied) and set SSL to Full (strict).
- Avoid heavy uncached pages that anyone can trigger — unlimited search, filters and AJAX calls — or limit them.
- Keep backups you can restore yourself, so an attack that coincides with a hack is never final.
Make WordPress fast: PageSpeed guide →Ninza Speed cache plugin →Restore from a backup →
What to do during an attack
If your site is being flooded right now:
- 1. Contact your host's support with the time it started and what you see; they can see the traffic and apply bans.
- 2. If the domain is on Cloudflare, turn on 'I'm Under Attack' mode for a few hours; it challenges every visitor before they reach your server.
- 3. Add a Cloudflare rate-limiting or WAF rule for the page being hit (login, search, xmlrpc).
- 4. If the domain is not on Cloudflare yet, move its DNS there — it takes minutes, and the proxy protects you as soon as DNS updates.
- 5. Do not pay anyone who demands money to stop an attack; report extortion to the police cyber cell (cybercrime.gov.in in India).
- 6. Afterwards, review logs, keep the protections on and check that nothing was changed on the site.
Questions to ask a host about DDoS protection
Before you buy hosting for a business site, ask:
- Which layers are protected — network, web server, application, logins?
- Are there per-visitor rate limits and automatic bans for bots and brute force?
- What happens to my site if another customer on the server is attacked?
- Is there a page cache for WordPress by default?
- Can I use Cloudflare in front, with SSL Full (strict), without problems?
- Will support act on an attack, and how fast?
DDoS protection included with Cloud Ninza hosting
Every Cloud Ninza plan — WordPress, PHP, static, Node.js, Python and Java — runs behind the protections described above at no extra cost, on servers in India. Because one site's attack must never take down its neighbours, limits apply per visitor and per account, and each account's memory and CPU are capped to its plan. WordPress plans add a page cache on every site, Ninza Speed, free SSL, backups twice a day and free email accounts; Growth, Business and Pro add Search Master and competitor analysis.
WordPress hosting →Node.js hosting →Compare plans →
Common myths about DDoS protection
A few beliefs lead businesses to under- or over-spend on protection:
- 'We are too small to be attacked.' Most attacks on small sites are automated bots that do not care who you are; they attack whatever answers.
- 'An SSL certificate protects us from DDoS.' SSL encrypts traffic; it does nothing to stop floods. Encrypted floods are actually more expensive for a server to handle.
- 'A security plugin is enough.' A WordPress plugin runs inside PHP — by the time it sees a request, the server has already spent the resources an attack wants to exhaust. Protection must start at the network and web server.
- 'Blocking a country stops attacks.' Botnets use machines everywhere, including India, so geo-blocking mostly blocks real customers abroad.
- 'Unlimited bandwidth means we cannot be taken down.' Bandwidth limits are rarely what fails first; CPU, PHP workers and connection slots run out long before.
Key takeaways
The short version, for anyone skimming:
- A DDoS attack floods a site with traffic from many machines so real visitors cannot get in.
- Small and medium websites are hit mostly by application-layer floods, bots and brute force, not terabit attacks.
- Real protection is layered: network limits, web-server rate limits, bot bans, caching and a CDN in front.
- No server alone survives an attack bigger than its link — use Cloudflare's free proxy for that layer.
- Cloud Ninza includes server-level DDoS and bot protection on every plan, with WordPress hosting from ₹1,788 a year.
WordPress Hosting from ₹1,788/year
WordPress on India-hosted cloud servers, installed for you — the latest release or the version your site needs. Latest WordPress or your chosen version · PHP 8.3, 8.4 or 8.5 · Free SSL certificate.
Hosting from ₹149 a month on servers in India
WordPress, static HTML, PHP, Node.js, Python and Java plans with free SSL and your choice of version. Create your account, pick a plan and pay by UPI, card or netbanking; your hosting is created automatically and you get your login by email, usually within minutes.