VergeCloud defends your infrastructure by:
Targets advanced bots and application-layer attacks that attempt to mimic legitimate user behavior. VergeCloud offers three challenge modes:
TTL (Time-To-Live) determines how long a successfully validated challenge remains trusted.
Long TTL results in fewer repeated challenges and a better user experience
Short TTL provides stronger security but may introduce more frequent prompts
For example, if TTL is set to 30 minutes, a user who passes a challenge will not be prompted again for the next 30 minutes.
You should avoid challenging every user and instead focus on suspicious or abusive traffic. A progressive strategy helps balance security and usability.
If example.com loads JavaScript that makes requests to sub.example.com, credential-included requests may be required when challenges are active.
Fetch example: fetch("https://sub.example.com", { credentials: 'include' });
XHR example: let xhttp = new XMLHttpRequest(); xhttp.open("GET", "https://sub.example.com", true); xhttp.withCredentials = true; xhttp.send();
Ajax example: $.ajax("https://sub.example.com", { xhrFields: { withCredentials: true }});
If the subdomain does not need to return a response:
fetch("https://sub.example.com", { mode: 'no-cors', credentials: 'include' });
Note on images: Any images included in this article should use clear, descriptive alt text to ensure accessibility and improve clarity for all users.
VergeCloud’s DDoS protection offers multi-layer filtering across L3/4 and L7, configurable challenge modes, firewall-based bot mitigation using IPs, user agents, JA3 fingerprints, and rate limits, along with flexible TTL controls and exclusion rules. Built into a secure CDN, this approach allows you to stop attackers effectively while preserving a smooth experience for legitimate users. By combining traffic analytics, adaptive challenges, and precise firewall controls, you can maintain availability even under sustained attack conditions.