What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
To protect a WordPress site from a distributed denial-of-service (DDoS) attack, filter traffic before it reaches your hosting server. Use protection from your host or a managed reverse proxy/CDN with suitable DDoS and web application firewall (WAF) controls, then restrict direct access to the origin server. WordPress plugins can help with specific abusive endpoints, but they cannot absorb an attack that has already overwhelmed your network or server.
First, identify what kind of attack you are facing
DDoS describes an attempt to make a service unavailable by overwhelming it with traffic from multiple sources. The traffic may target network or transport capacity, or it may consist of HTTP requests aimed at consuming application or server resources. The right defenses depend on where the attack is happening; protection for one layer does not necessarily cover another. Cloudflare’s DDoS documentation describes protection across different layers.
A sudden increase in failed logins is not, by itself, proof of a DDoS. Credential stuffing and brute-force attacks target account access, while a DDoS targets availability. They can occur together, and some controls overlap, but blocking login attempts does not stop a flood that is saturating a network connection. WordPress’s brute-force guidance addresses account protection rather than upstream traffic capacity.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Put filtering in front of your WordPress origin
Your origin is the server or hosting environment where WordPress runs. A reverse proxy sits between visitors and that origin: it receives requests, filters them according to its protections, and forwards permitted traffic to the site. Because this filtering happens before requests reach the origin, it is the central resilience measure when the hosting server is at risk of being overwhelmed. WordPress’s optimization guidance describes using an intermediary to filter malicious requests before they reach the server.
#1 Best Overall
- Compact and Efficient Design: The FortiGate 40F is designed for small to mid-sized businesses and enterprise branch offices, featuring a compact, fanless desktop form factor that ensures quiet operation and minimizes space usage.
- Robust Connectivity Options: Equipped with 5 GE RJ45 ports, including 1 WAN port and 4 internal ports, this model provides essential connectivity and flexibility for various network configurations in a small-scale environment.
- High-Performance Security: Offers up to 1 Gbps IPS throughput and 600 Mbps threat protection throughput, using Fortinet’s purpose-built security processor technology to deliver industry-leading performance and protection for SSL encrypted traffic.
- Advanced Threat Protection: Integrated with Fortinet’s AI-powered FortiGuard Labs, the FortiGate 40F offers comprehensive cybersecurity, identifying and mitigating both known and unknown threats to maintain robust security across your network.
- Simplified Management and Deployment: Features a user-friendly management console that provides comprehensive network automation and visibility, coupled with Zero Touch Integration with Fortinet’s Security Fabric for easy deployment.
You can obtain this protection through your hosting provider or an independent managed CDN/WAF service. Cloudflare and Sucuri are examples referenced in official guidance, not universal recommendations. Compare options against the specific attack layers they cover, whether they filter before origin capacity is consumed, how they support origin access restrictions, what WAF and rate-limit controls they provide, compatibility with your DNS and WordPress integrations, incident support, and total cost for your traffic pattern. Ask providers directly about coverage and escalation; there is no established universal threshold or guarantee that a service will keep every site available during every attack.
Make sure attackers cannot bypass the proxy
A proxy cannot protect your origin as intended if an attacker can discover and contact the server directly. If you use Cloudflare, its proactive-defense guidance says: “Make sure your origin is not exposed to the public Internet, meaning that access is only possible from Cloudflare IP addresses.” Apply the equivalent restriction for whichever provider you deploy; do not copy Cloudflare’s address list for another service.
Rank #2
- HARDWARE PLUS SECURITY SERVICES: FortiGate-60F Firewall Appliance bundled with 1 year of FortiCare Premium and FortiGuard Unified Threat Protection.
- UNIFIED THREAT PROTECTION (UTP): Secures against advanced online threats with comprehensive web filtering and anti-botnet technologies.
- OPTIMIZED FOR MEDIUM-SIZED BUSINESSES: Tailored for businesses needing robust security without the infrastructure of larger enterprises.
- RELIABLE CUSTOMER SUPPORT: FortiCare Premium ensures high-quality support and service continuity.
- EFFECTIVE PROTECTION: Employs advanced filtering technologies to safeguard against sophisticated threats.
- Ask your host how to allow traffic to the origin only from your proxy or provider’s published network addresses.
- Review DNS records and other services that might reveal or expose the origin. Work with the host to check the full setup rather than assuming that adding a CDN hides every route to the server.
- If the origin IP has already been targeted directly, ask the host whether it can rotate the address, then secure the replacement so it is not reachable around the proxy.
Scope WAF rules and rate limits to real traffic
Begin with the managed DDoS protections provided by your service. Cloudflare recommends leaving its DDoS managed rules at their defaults, then using custom WAF and rate-limit rules that reflect known traffic patterns. These are Cloudflare-specific recommendations; rule names, capabilities, and setup vary by provider. See Cloudflare’s DDoS protection guidance.
Free tools Windows power users keep installed
One-click scans. No signup required.
For WordPress, sensitive routes such as /wp-login.php and /xmlrpc.php may warrant additional controls. Set limits at the edge when possible and tune them to preserve legitimate use. Overly strict rules can block real users, administrators, publishing workflows, or applications. A rate limit is not automatically a DDoS solution: if it runs inside WordPress, the request may already have consumed resources before the limit is applied. WordPress’s intermediary-filtering guidance supports filtering before requests reach the server.
Rank #3
- 【Up to 1100 Mbps VPN Speed 】 Hardware-accelerated WireGuard and OpenVPN-DCO deliver up to 1100 Mbps VPN throughput, over 3× faster than Brume 2 for smooth remote access and file transfers.
- 【Three 2.5G Ports & Multi-WAN】Tri-port 2.5GbE design with flexible WAN LAN configuration supports multi-gigabit wired setups, dual-ISP Multi-WAN and failover to keep home and SOHO networks online.
- 【Stealth VPN Obfuscation】VPN obfuscation disguises VPN traffic as regular HTTPS, helping you evade blocking, bypass restrictive networks and maintain stable, private connections.
- 【DPI protection】Deep Packet Inspection with visual dashboards blocks adult/gambling/malicious sites, while SQM and QoS prioritize gaming, calls, and video when bandwidth is tight
- 【OpenWrt & USB 3.0 Expansion】OpenWrt with 1GB DDR4 and 8GB eMMC lets you install plugins and build VPN, ad-blocking or NAS, while USB 3.0 Type‑C connects high-speed storage or 4G/5G dongles
Use WordPress hardening as a supplement, not the front line
Security plugins and application settings can help reduce login abuse or requests to particular WordPress endpoints. They are useful as one layer, but they execute within or alongside the application and cannot replace upstream filtering when request volume threatens the origin’s network or server capacity.
Disable XML-RPC only if your site does not need it
If no feature depends on XML-RPC, disabling it removes one endpoint that can be abused. But Jetpack, mobile apps, and remote publishing may rely on it. If those integrations need XML-RPC, keep the required functionality and apply suitable edge restrictions or rate limits instead. After changing access, check that the site’s integrations and publishing workflows still work. Disabling XML-RPC reduces one possible abuse path; it does not stop all DDoS attacks. WordPress’s Disable XML-RPC plugin listing is one reference for the option, not evidence that disabling it is appropriate for every site.
Rank #4
- Runs UniFi Network for full-stack network management
- Manages 30+ UniFi Network devices and 300+ clients
- 1 Gbps routing with IDS/IPS
- Multi-WAN load balancing
- 0.96" LCM status display
What to do during an active attack
- Contact your host and edge provider. Tell them the site is unavailable or degraded and ask what traffic they see. Confirm whether the event targets network capacity, HTTP requests, or a particular WordPress route.
- Check for a direct-origin path. Ask whether requests are reaching the hosting server outside the proxy. If so, work with the host to restrict access and, if the origin has been targeted, discuss rotating its IP.
- Apply mitigation at the edge. With your provider, challenge or rate-limit suspicious traffic and adjust WAF rules to the affected routes. Preserve access for known legitimate users and services.
- Watch the site and revise carefully. Check whether availability improves and whether legitimate login, publishing, or integrations are being blocked. Coordinate changes with the host or provider rather than relying on a plugin to absorb a high-volume flood.
There is no universal response threshold or assurance of uninterrupted service established by the cited guidance. The provider can assess its own network and controls; ask for incident-specific information and next steps.
Recommended Free Tools
Choose protection based on your hosting setup
| Decision point | Protection from your host | Independent managed CDN/WAF |
|---|---|---|
| Attack layers covered | Ask which network, transport, and HTTP/application attacks are covered for your hosting service; coverage varies. | Ask which layers and attack types the service covers; do not assume all plans or configurations are equivalent. |
| Filtering before origin capacity is used | Confirm where mitigation occurs in the provider’s network and whether it protects your hosting connection. | A reverse proxy can filter requests before forwarding them to the origin, if traffic is routed through it. |
| Origin access controls | Ask whether the host can restrict access to the origin and help rotate a targeted IP. | Configure the host firewall to accept only the deployed provider’s published addresses; check other services and DNS records for bypasses. |
| WAF and rate limits | Ask what rules and route-specific limits are available and how they can be tuned. | Compare managed protections and custom controls, including how to preserve legitimate WordPress and integration traffic. |
| Compatibility | Check your existing DNS, proxy settings, and WordPress integrations with the host. | Check DNS and proxy changes, origin configuration, and integrations such as remote publishing or mobile apps. |
| Incident escalation and cost | Confirm support availability, escalation process, and total cost for your actual traffic pattern. | Confirm support availability, escalation process, and total cost for your actual traffic pattern. |
The cited sources do not establish current plan prices, a provider ranking, or a guarantee that one option is best for every WordPress site. Choose based on the attack layers you need covered and whether the provider can filter traffic before it consumes your origin’s capacity.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
