Review the requirements and restrictions for accelerated domain names before adding them to Alibaba Cloud CDN. This helps you avoid issues with content that violates our policies.
Security restrictions
|
Restriction |
Description |
|
Content policy |
All domain names added to CDN are subject to a content review. CDN does not support acceleration for domain names associated with content such as:
Note
|
|
Handling content violations and suspensions |
|
|
Throttling rules for traffic bursts |
As stipulated in the Product Terms of the Alibaba Cloud Service Agreement, if you anticipate a sudden bandwidth or QPS surge — including capacity tests, performance tests, promotions, or major releases — you must apply for a temporary traffic quota increase. Contact your account manager or apply through other channels at least three business days in advance. For major holidays (Spring Festival, Double 11), apply at least one month in advance.
|
|
Potential risks from attacks or resource abuse |
By default, Alibaba Cloud CDN does not provide access control or security protection. If your domain experiences a sudden bandwidth or traffic spike from malicious attacks or resource abuse, you may incur unexpectedly high charges. Charges incurred from malicious attacks or resource abuse cannot be waived or refunded. Mitigate this risk by following Warning about high bills. |
|
Domain name sandbox mode |
Sandbox: If your domain name is under attack, such as a DDoS or CC attack, or if you do not report a traffic surge to Alibaba Cloud in advance and the bandwidth or queries per second (QPS) significantly increases, the CDN system may add your domain name to a sandbox. This prevents other users' acceleration services from being affected. The system determines whether to add the domain name to the sandbox based on factors such as the service status and the severity of the attack. In the case of a severe attack, other domain names under the same account are also added to the sandbox, and you cannot add new domain names to the account. For more information, see Sandbox. |
Accelerated domain name restrictions
|
Restriction |
Description |
|
Domain name format |
|
|
Wildcard domain name requirements |
Note
Should I add an apex domain or a wildcard domain name? When adding an accelerated domain name to CDN, you can specify a wildcard domain name (for example, |
|
ICP filing requirements |
ICP filing: If the acceleration region is Global or Mainland China Only, you must apply for an ICP filing for the domain name, regardless of where the origin server is located. We recommend that you use the Alibaba Cloud Filing Service to apply for an ICP filing. Before you apply for an ICP filing, see Check the server for ICP filing to complete the required preparations and checks. After CDN acceleration is enabled, user requests route to the nearest CDN node. The accessed IP address changes based on node allocation — this is normal CDN behavior. CDN node IP changes do not affect your origin server IP or ICP filing status. ICP filing is tied to the origin server, not CDN node IPs, so you do not need to worry about your filing being revoked due to changing node IP addresses. |
|
Domain name quantity limit |
|
|
Domain name reclamation and suspension |
|
Origin server restrictions
|
Restriction |
Description |
|
Origin address length |
The maximum length is 67 characters. |
|
Number of origin servers |
Up to 20 origin servers per accelerated domain name. |
|
OSS Domain |
Note
|
|
IP |
|
|
Site Domain |
One or more domain names can be configured as origin servers. Note
|
|
Function Compute Domain |
Use a Function Compute domain name from the same account as an origin server. Select the Function Compute Region and Domain Name. Configure a Custom Domain Name. |
Back-to-origin restrictions
|
Restriction |
Description |
|
Maximum length of the back-to-origin request header |
Maximum: 300 bytes. |
|
Back-to-origin request timeout |
Default: 10 seconds (TCP layer), 30 seconds (HTTP layer). |
|
Back-to-origin |
If the origin server does not respond with |
|
HEAD requests converted to GET requests by default |
By default, when a client sends a HEAD request to an Alibaba Cloud CDN node, the node converts it to a GET request before forwarding it to the origin server. To preserve the HEAD request method, submit a ticket. |
|
Default case conversion for origin request headers |
When you use the Origin HTTP Header feature to add a request header, the header field name is automatically converted to title case when sent to the origin server. For example:
To disable this default conversion, use the Origin HTTP Header feature to add the following header:
|
Cache refresh and prefetch quotas
|
Item |
Quota |
|
Cache refresh |
If your account's daily peak bandwidth exceeds 200 Mbps, request a quota increase through Quota Management. Alibaba Cloud evaluates and configures quotas based on your business needs. |
|
Prefetch |
Only URL prefetch is supported. Quota: 1,000 URLs per day per account. If your account's daily peak bandwidth exceeds 200 Mbps, request a quota increase through Quota Management. Alibaba Cloud evaluates and configures quotas based on your business needs. |
Access restrictions
|
Restriction |
Description |
|
Restriction for the "Global (Excluding the Chinese mainland)" acceleration region |
If the acceleration region for an accelerated domain name is set to Global (Excluding the Chinese mainland), Alibaba Cloud CDN will block requests from accessing nodes in the Chinese mainland. In this case, user requests are routed to nearby nodes outside the Chinese mainland, such as those in Hong Kong (China), Japan, or Singapore. |
|
Difference between "Global" and "Global (Excluding the Chinese mainland)" |
|
|
Total size limit for origin server HTTP response headers |
The total size of the HTTP response headers returned from the origin server to a CDN node cannot exceed 32 KB. Otherwise, a 502 error is returned. |
|
Limits on URL length, HTTP request header length, and total length of URL and all headers |
For HTTP/2.0:
For HTTP/1.1: The |
|
Request method |
Of the common HTTP request methods, CDN and support Note
|
|
IoT card access restriction |
In accordance with regulations from the Ministry of Industry and Information Technology (MIIT) of China, Alibaba Cloud CDN in the Chinese mainland does not support acceleration for IoT card terminals. Devices using IoT cards to access Alibaba Cloud CDN nodes may fail to connect. |
|
HTTPS access restriction |
If a client does not send Server Name Indication (SNI) information during the SSL handshake with a CDN node, the CDN node cannot guarantee a successful handshake. |
API limits
|
Limit |
Description |
|
API call frequency limit per user |
The API call limit for all API operations of Alibaba Cloud CDN is 1,000 calls per second per user. If this threshold is exceeded, the following error message is returned:
|
Other restrictions
|
Restriction |
Description |
|
CNAME record |
The CNAME records for Alibaba Cloud CDN, DCDN, ApsaraVideo Live, and ApsaraVideo for VOD products are intended solely for the scheduling and resolution purposes of Alibaba Cloud CDN. Alibaba Cloud reserves the right to suspend any domain names and accounts that misuse these CNAME records. |
|
File |
|
|
Number of EdgeScript rules |
By default, you can configure a maximum of two EdgeScript rules for each domain name. If you need to configure more rules, use the Modify Outgoing Request Header feature. |
|
Number of feature configurations |
You can add up to 50 configuration rules. This limit applies to features such as: Modify Outgoing Request Header, Modify Incoming Response Header, Origin Path Rewrite, Parameter Rewrite, and Cache Expiration. |
|
Gzip and Brotli compression |
Gzip or Brotli compression applies only to origin files between 1 KB and 10 MB. Files outside this range are not compressed. |