HTTP DDoS protection
Help protect your origin from HTTP request floods using edge request limits.
This covers application-layer requests that reach the edge. It is not a volumetric DDoS scrubbing service or a bandwidth guarantee.
Choose what runs on each domain, then use observed traffic to see how your rules behave.
Help protect your origin from HTTP request floods using edge request limits.
This covers application-layer requests that reach the edge. It is not a volumetric DDoS scrubbing service or a bandwidth guarantee.
Use the background antibot to match unwanted networks. Add browser challenges when visitors need extra verification.
Choose Cloudflare Turnstile, Google reCAPTCHA v2 or hCaptcha where configured. Combining challenges means visitors must pass each selected check.
Block common sensitive-file requests, path traversal attempts and recognized exploit URL probes before they reach your site.
The exploit guard examines request paths. It does not inspect every payload or replace updates and application security at your origin.
Watch individual requests as they reach the serving node. The live feed shows time, visitor IP, HTTP method and the decision for each request.
The feed shows FortEdge decisions. Requests that reach the origin directly never appear here. An allowed request does not guarantee a successful response from your site.
Apply country rules, set trusted IP exceptions or pause web traffic while keeping the domain connected.
Whitelist entries bypass domain filters, including the paused page, so reserve them for trusted addresses.
Planned: serve eligible content closer to visitors using edge caching.
CDN is not live or included as an active feature in any plan today.
One domain. Thirty days. No card required.