Overview
VergeCloud’s DDoS protection ensures that your website remains secure from malicious or abusive traffic while maintaining a seamless, interruption-free experience for legitimate users. Using multi-layer filtering, intelligent traffic verification, customizable challenge modes, and firewall automation,
VergeCloud provides comprehensive protection with minimal friction.
VergeCloud defends your infrastructure by:
- Filtering malicious traffic across Layer 3/4 (network) and Layer 7 (application)
- Offering configurable challenge modes (Cookie, JS Challenge, Captcha)
- Supporting TTL configuration for challenge validity
- Allowing exclusions for trusted IPs, URLs, or services
- Enabling traffic analysis to identify attack patterns
- Providing granular firewall rules to block or challenge abusive IPs, fingerprints, or user agents
Protection Level
Layer 3/4 Protection
Protects your website from volumetric and network-level attacks (SYN floods, UDP floods, amplifiation attacks).
Does not stop sophisticated Layer 7 bot traffic.
Layer 7 Protection
Targets advanced bots and application-layer attacks. VergeCloud offers 3 challenge modes:
Cookie Challenge
Ensures the browser can accept/return cookies.
Stops simple bots.
Lightweight and user-friendly.
JS Challenge
Browser runs a small JavaScript file to validate itself.
Stops bots that cannot execute JS.
Ideal for preventing automated scraping or credential stuffing.
Captcha Challenge
Displays a Captcha (image or puzzle).
Highest verification level.
Best for login pages, checkout flows, or sensitive user actions.
TTL (Time-To-Live)
TTL determines how long a validated challenge remains trusted.
- Long TTL → Fewer repeated challenges, better UX
- Short TTL → Stronger security but more prompts
Example: If TTL = 30 minutes, a user who passes a challenge won’t be prompted again for the next 30 minutes.
How to Implement an Effective DDoS Strategy
You don’t want to challenge every user only suspicious traffic.
Follow this progressive strategy:
A. Limit Abusive IP Addresses
VergeCloud maintains lists of known abusive IP ranges (e.g., abuseip90to100).
Steps:
- Go to Security → Firewall → New Rule
- Set Field = IP Source Address
- Set Operator = From IP List
Use values:
- abuseip90to100
- abuseip80to90
- abuseip70to80
Choose Challenge or Block at the bottom.
B. Limit or Block Most Visited IPs
- Go to Analytics & Logs → Visited IPs Statistics
- Identify IPs generating unusually high traffic
- Click the Add Firewall Rule button next to the IP
- Apply Challenge or Block action
- Check your logs for repeated suspicious user-agent strings
- Create a firewall rule to Challenge or Block those agents
- Useful for automated crawlers and bad scrapers
D. Rate-Limit the Most Visited URLs
- Go to Firewall → New Rule
- Select Field = URL and Operator = Equals/Matches
- Target URLs under heavy attack
- Apply Rate Limit, Challenge, or Block
E. Use JA3 Fingerprinting to Identify Bots
- Enable JA3 fingerprinting:
SSL/TLS → Edge Servers → Enable JA3 - Download malicious JA3 fingerprints from:
https://sslbl.abuse.ch/ja3-fingerprints/ - Add firewall rules based on JA3 fingerprint
Block/challenge fingerprints associated with bot frameworks
F. If Attacks Persist — Enable General DDoS Mitigation
Go to your CDN service → DDoS Protection and activate the global protection mode.
You may enable Captcha for all visitors during severe attacks.
Exclusions
Use exclusions to prevent unnecessary challenges:
Supported Exclusions:
- Specific URLs or paths (supports glob patterns)
- Subnets or IP ranges (CIDR)
- Internal services (health checks, monitoring endpoints.
Disabling DDoS Protection for a Specific URL
- Open DDoS → Custom Rules
- Click New Rule
- Enter the URL path
- Set action to No Challenge
JavaScript / Fetch / XHR Considerations
If example.com loads JS that requests sub.example.com, you may need credential-included requests when challenges are active.
Fetch
fetch("https://sub.example.com", { credentials: 'include' });
XHR
let xhttp = new XMLHttpRequest();
xhttp.open("GET", "https://sub.example.com", true);
xhttp.withCredentials = true;
xhttp.send();
Ajax
$.ajax("https: //sub.example.com", { xhrFields: { withCredentials: true }});
CORS / Preflight Notes
If the subdomain does not need to return a response:
fetch("https://sub.example.com", {
mode: 'no-cors',
credentials: 'include'
});
Summary
VergeCloud’s DDoS protection provides:
- Multi-layer filtering (L3/4 + L7)
- Configurable protection modes
- Firewall-based bot mitigation (IP, UA, JA3, rate limits)
- Flexible TTL and Captcha options
- URL and IP exclusions
- Developer-friendly support for cross-domain requests
- By combining traffic analytics, firewall rules, and adaptive challenges, you can build a layered defense strategy that stops attackers while keeping your user experience intact.