tencent cloud

Tencent Cloud EdgeOne

Release Notes and Announcements
Release Notes
Security Announcement
Announcements
Product Introduction
Overview
Strengths
Use Cases
Comparison Between EdgeOne and CDN Products
Use Limits
Purchase Guide
Description of Trial Plan Experience Benefits
Free Plan Guide
Billing Overview
Billing Items
Subscriptions
Renewals
Instructions for overdue and refunds
Comparison of EdgeOne Plans
About "clean traffic" billing instructions
DDoS Protection Capacity Description
Getting Started
Choose business scenario
Quick access to website security acceleration
Quick deploying a website with Pages
Domain Service&Origin Configuration
Domain Service
HTTPS Certificate
Origin Configuration
Site Acceleration
Overview
Access Control
Smart Acceleration
Cache Configuration
File Optimization
Network Optimization
URL Rewrite
Modifying Header
Modify the response content
Rule Engine
Image&Video Processing
Speed limit for single connection download
DDoS & Web Protection
Overview
DDoS Protection
Web Protection
Bot Management
API Discovery(Beta)
Edge Functions
Overview
Getting Started
Operation Guide
Runtime APIs
Sample Functions
Best Practices
Pages
L4 Proxy
Overview
Creating an L4 Proxy Instance
Modifying an L4 Proxy Instance
Disabling or Deleting an L4 Proxy Instance
Batch Configuring Forwarding Rules
Obtaining Real Client IPs
Data Analysis&Log Service
Log Service
Data Analysis
Alarm Service
Site and Billing Management
Billing Management
Site Management
Version Management
General Policy
General Reference
Configuration Syntax
Request and Response Actions
Country/region and Corresponding Codes
Terraform
Overview
Installing and Configuring Terraform
Practical Tutorial
EdgeOne Skill User Guide
Automatic Warm-up/Cache Purge
Resource Abuse/hotlinking Protection Practical
HTTPS Related Practices
Acceleration Optimization
Scheduling Traffic
Data Analysis and Alerting
Log Platform Integration Practices
Configuring Origin Servers for Cloud Object Storage (Such As COS)
CORS Response Configuration
API Documentation
History
Introduction
API Category
Making API Requests
Site APIs
Acceleration Domain Management APIs
Site Acceleration Configuration APIs
Edge Function APIs
Alias Domain APIs
Security Configuration APIs
Layer 4 Application Proxy APIs
Content Management APIs
Data Analysis APIs
Log Service APIs
Billing APIs
Certificate APIs
Origin Protection APIs
Load Balancing APIs
Diagnostic Tool APIs
Custom Response Page APIs
API Security APIs
DNS Record APIs
Content Identifier APIs
Legacy APIs
Ownership APIs
Image and Video Processing APIs
Multi-Channel Security Gateway APIs
Version Management APIs
Data Types
Error Codes
FAQs
Product Features FAQs
DNS Record FAQs
Domain Configuration FAQs
Site Acceleration FAQs
Data and Log FAQs
Security Protection-related Queries
Origin Configuration FAQs
Troubleshooting
Reference for Abnormal Status Codes
Troubleshooting Guide for EdgeOne 4XX/5XX Status Codes
520/524 Status Code Troubleshooting Guide
521/522 Status Code Troubleshooting Guide
Tool Guide
Agreements
Service Level Agreement
Origin Protection Enablement Conditions of Use
TEO Policy
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

IP Groups

PDF
Focus Mode
Font Size
Last updated: 2025-09-01 15:30:54
An IP group contains a list of IPs or CIDR IP ranges. You can reference the IP group in DDoS protection and Web protection rules to simplify configuration and maintenance.
Note:
1. IP groups support cross-site usage. After creating an IP group, you can directly reference it in other sites to ensure consistent policies across different sites.
2. Up to 100 groups can be configured under the same account, and each IP group can include up to 2,000 IPs or CIDR IP ranges. To configure IP group matching in Web protection rules, see Match Condition for related limits.

Scenario 1: Group Management of IP Information with Business Threats

Example Scenario

A large game customer has connected sites example.com and site.com. Currently, through the security intelligence library and their own business security, a blocklist of IPs with business threats has been identified. These IP addresses will change dynamically, so they need to be updated in real-time and applied to all site domain names, instantly blocking these IPs.

Directions

1. Log in to the Tencent Cloud EdgeOne console, enter Service Overview in the left menu bar, and click the site to be configured under Website Security Acceleration.
2. On the site detail page, click Security > General Settings.
3. In the IP groups tab, click Edit.
4. Click Create to create a group. Enter the group name and the IP address or IP range contained in the group, such as 1.1.1.1/23 and 1.2.2.2. Separate multiple IP addresses with carriage returns.
5. Click Save to complete the IP group creation.



6. After creating the IP group, as an example for this scenario, you need to disable access for all IPs within the group. You can add basic access control rules on the example.com and site.com's Web Security page. When adding rules, choose Client IP equals the group name to perform Block. This will intercept all IP access within the group and dynamically update based on included IPs. For detailed configuration steps, refer to Custom Rules.



7. (Optional) After configuring the rules, if you identify new risky IPs that need to be added to the group and applied to all sites, you can follow steps 1-3 to re-enter the site where the template was created, click Edit, enter the new IP addresses, and click Save to apply the new IPs to all protection policies that use this group.




Scenario 2: Adding Automatically Expiring IPs in Batch to an Existing IP Group

Example Scenario

An e-commerce customer has configured a long-term valid custom interception rule on the site example.com, referencing the IP group named block_ip to manage blocklist IPs in a unified way. During promotional events, a batch of IPs exhibiting risk behaviors such as malicious crawling and abnormal order placement were identified through monitoring. Since these risks only exist during the activity period, the customer wants to temporarily add these IPs to block_ip and set a unified expiry date, automatically removing them at the end of activity to avoid long-term blocking of legitimate users, while keeping the existing interception rules in effect without additional maintenance of new protection policies.

Directions

1. Log in to the EdgeOne console, enter Service Overview in the left menu bar, and click the site that needs to be configured under Website Security Acceleration.
2. Click Security Protection > General Settings to enter the configuration options details page.
3. In the IP group card, locate the target IP group (such as block_ip), then click Edit.
4. In the editing page, click Add.



5. In the pop-up window for adding IP or ranges, input the IP address or ranges that need temporary control (bulk entry is supported, multiple addresses are separated by pressing enter). Check Expiration time and set the expiration time.



6. Click Confirm. Once saved, the temporary control IP will take effect immediately and be automatically removed from block_ip upon expiration.

Scenario 3: Adjusting the Expiry Time of IPs with Scheduled Expiration

Example Scenario

For site example.com, the block_ip IP group has set a 7-day expiry for a batch of abnormal request source IPs. Subsequent analysis detected ongoing attack behavior, requiring these IPs' expiry dates to be extended by 14 days.

Directions

1. Log in to the EdgeOne console, enter Service Overview in the left menu bar, and click the site that needs to be configured under Website Security Acceleration.
2. Click Security Protection > General Settings to enter the configuration options details page.
3. In the IP group card, locate the target IP group (such as block_ip), then click Edit.
4. On the editing page, select the IP address or ranges that need expiry time adjustment, then click Modify.



5. In the pop-up window for modifying scheduled expiration time, set a new expiry date.



6. Click Confirm. Once saved, these IPs will be automatically removed based on the latest expiry time.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback