Special Offers: Up to 75% OFF on Hostinger & High-RAM Contabo Cloud VPS available this month.Compare Plans

How to Protect WordPress from Layer 7 DDoS Attacks on Hostinger & Contabo

Alex Vance
Alex VanceCloud Infrastructure Architect
October 19, 2026
•
15 min read
•
4.9 / 5.0
Transparency Notice: This article contains affiliate links to hosting providers like Hostinger and Contabo. If you purchase through our links, we may earn a commission at zero extra cost to you. We only recommend products we personally benchmark and test. Read full disclosure.
How to Protect WordPress from Layer 7 DDoS Attacks on Hostinger & Contabo

Hostinger vs. Contabo: Full Specifications Breakdown

Data verified from our lab benchmarks • Updated for 2026

Feature / Metric
HostingerEditor's Choice UI
ContaboMax RAM Value
Starting Price$2.99 / month (Web) | $4.99 / mo (VPS)$5.50 / month (Cloud VPS S)
vCPU Cores1 to 8 vCPU (Dedicated resources)4 to 12 vCPU (High Core Count)
RAM Memory4 GB to 32 GB6 GB to 64 GB (Gigantic RAM)
Storage Technology50 GB – 400 GB NVMe SSD50 GB NVMe or 300 GB SSD
Traffic / Bandwidth4 TB to 32 TB32 TB Outgoing + Unlimited In
Control Panel & UIhPanel (Ultra Modern & Easy)cPanel, Plesk, Webmin, or CLI
Customer Support24/7 Live Chat & AI Support (Multi-lingual)Email Ticket Support (German Business Hours)
Best ForBloggers, WordPress Sites & Devs wanting easy UIHeavy Database, Docker, Game Servers & SysAdmins
Money-Back Guarantee30-Day Money-Back Guarantee14-Day EU Statutory Cancellation
Official LinksVisit HostingerVisit Contabo

The Threat of Layer 7 Application DDoS Attacks

Unlike traditional volumetric Layer 3/4 attacks that saturate network bandwidth, Layer 7 (Application Layer) DDoS attacks simulate legitimate browser traffic by sending thousands of simultaneous HTTP GET and POST requests directly to expensive endpoints like /wp-login.php, /?s=search_query, or /xmlrpc.php. These attacks exhaust PHP worker threads and database connection pools, bringing even powerful servers to their knees.

Defense Layer 1: Cloudflare Custom WAF Rules

In your Cloudflare dashboard, navigate to Security -> WAF -> Custom rules. Create the following rules:

  • Block XML-RPC: (http.request.uri.path eq "/xmlrpc.php") -> Action: Block.
  • Protect WP-Login with Managed Challenge: (http.request.uri.path contains "/wp-login.php") and not (ip.src in {YOUR_HOME_IP}) -> Action: Managed Challenge.
  • Rate Limit Site Search: (http.request.uri.query contains "s=") -> Action: Rate Limit (10 requests per minute).

Defense Layer 2: Nginx Connection and Request Rate Limiting

In /etc/nginx/nginx.conf, add rate-limiting memory zones:

limit_req_zone $binary_remote_addr zone=one:10m rate=5r/s;
limit_conn_zone $binary_remote_addr zone=addr:10m;

Apply to your virtual host:

location / {
    limit_req zone=one burst=15 nodelay;
    limit_conn addr 10;
    try_files $uri $uri/ /index.php?$args;
}

Editorial Verdict: Pros & Cons

What We Love (Pros)

  • Stops malicious botnets before they reach your origin server and exhaust CPU resources
  • Combines Cloudflare edge filtering with local Nginx IP connection limits
  • Protects WooCommerce checkouts and contact forms from automated spam bursts

Drawbacks (Cons)

  • Overly aggressive rate limiting can temporarily challenge legitimate high-speed visitors
#DDoS Protection#WordPress Security#Cloudflare WAF#Nginx Security#Server Hardening
Alex Vance

Written by Alex Vance

Cloud Infrastructure Architect

Alex and the ServerCraft engineering lab run routine benchmarks on over 25 web hosting providers, maintaining strict objectivity and reproducibility.

Recommended Next Reads