1. CC Attack Protection
Hackers typically launch CC attacks in two ways: 1) Using botnets, or 2) Utilizing proxies. In either case, these methods generate high-frequency access requests, causing server resource congestion (usually affecting CPU and bandwidth).
Therefore, we can effectively defend against CC attacks and scraping through protection mechanisms such as access frequency limiting and human-machine verification. It is recommended to enable this feature!
General Recommended Configuration:
Protection Mode: Relaxed
Protected Types: asp, aspx, php, htm, html
Protection Threshold: 60 requests/minute
Block Time: 60 minutes
Firewall Block: Disabled
Verification Method: Redirect Verification
Recommended Configuration During Large-Scale CC Attacks:
Protection Mode: Strict
Protected Types: asp, aspx, php, htm, html
Protection Threshold: 30 requests/minute
Block Time: 720 minutes
Firewall Block: Enabled
2. 404 Scan Protection
Hackers often use scanning tools to detect entry points before infiltrating a website. This module effectively identifies illegal scanning activities. It is recommended to enable this feature!
Recommended Configuration:
Scanning Frequency Threshold: 60 requests/minute
Block Time: 60 minutes
Firewall Block: Enabled
3. Overflow Attack Protection
Limits URL length and HTTP header length to prevent buffer overflow attacks.
It is recommended to set the URL length limit to 2048 bytes and the HTTP header length limit to 4096 bytes.
For detailed explanations of HTTP headers, click here >>>
4. Fake Spider Protection
Utilizes intelligent learning algorithms to accurately identify fake spiders. It is recommended to enable this feature during CC attacks!
Relaxed Mode: Employs intelligent learning algorithms for more precise identification of fake spiders, reducing the risk of false positives.
Strict Mode: Disables intelligent learning. Select this option during large-scale CC attacks to alleviate server pressure.
Blocking Scope: Choose the types of fake spiders to block. If the spider you need is not listed, please contact us to add it.
5. Proxy Request Protection
Prohibits access via proxies. It is recommended to enable this feature during large-scale CC attacks. However, websites using CDNs should never enable this feature.
This module cannot identify high-anonymity proxies. Due to the principles of high-anonymity technology, no company can currently identify high-anonymity proxies.