Wildcard Domain Access

In addition to individual custom domains, the CloudBase HTTP Gateway supports access via wildcard domains (e.g., *.example.com). Once a wildcard domain is connected, all its subdomains (such as api.example.com and web.example.com) can be used directly without being added one by one, which is ideal for businesses with many or dynamically growing subdomains.

Access Modes

Wildcard domain access is available in two modes: Platform and Single Environment.

Mode	Plan Requirement	Quantity Limit	Scope	Entry
Platform	Platform plan	Up to 10 per platform	All environments under the platform	Platform Settings → Custom Domain
Single Environment	Enterprise Advanced plan	Subject to plan quota	Current environment only	HTTP Gateway → Custom Domain

Note

• Platform-level wildcard domains are connected and managed at the platform dimension; once connected, they are shared by all environments under the platform. For more about CloudBase platforms, see CloudBase Platform Integration Overview.
• Single-environment wildcard domains only take effect within the environment they belong to, and different environments can connect their own wildcard domains.
• For plan quotas and capabilities, see Plan Quotas and Capabilities.

Priority

If a subdomain is covered by both a platform-level wildcard domain and a single-environment exact subdomain (e.g., both *.example.com and api.example.com are connected), requests will first match the single-environment exact subdomain. Only traffic not covered by the exact subdomain falls back to the wildcard domain.

Prerequisites

1. ICP filing for the wildcard domain: The wildcard domain (e.g., *.example.com) must complete ICP filing. Filing entry: ICP Filing.
2. Wildcard SSL certificate: Prepare a wildcard certificate covering the wildcard domain (e.g., *.example.com). You can upload or apply for one in the SSL Certificate Console.

Tip

A wildcard certificate only matches first-level subdomains. For example, *.example.com protects api.example.com, but not a.b.example.com.

Configuration Steps (Platform)

1. Go to CloudBase Console - Platform Settings - Custom Domain, and click "Wildcard Certificate Association" in the "Custom Domain Access" area.

2. Enter the wildcard domain and associate the wildcard SSL certificate, then complete domain ownership verification as instructed (add a DNS TXT record).
3. Once the domain access status is normal, copy the CNAME value provided on the page, then add a CNAME record for the wildcard domain in the DNS Console.
4. Return to the console and confirm the access status is "Normal" to complete the access.

Note

Configuring the edge acceleration platform takes time to propagate. The access status update takes about 10-20 minutes. Please wait patiently.

Quickly Inherit a Platform Wildcard Domain in a Single Environment

If a platform-level wildcard domain is already configured, a single environment does not need to go through the full domain access flow again (ownership verification, certificate configuration, CNAME configuration, etc.). Instead, you can quickly inherit the platform wildcard domain's access method and add an exact subdomain by calling the Create Access Route API (CreateHTTPServiceRoute):

• Set the domain in the request to the exact subdomain (e.g., api.example.com)
• Pass NONE as AccessType; the access configuration (certificate, CNAME, etc.) will be automatically inherited from the platform-level wildcard domain, with no separate configuration needed

Once added, the exact subdomain takes effect in the current environment and, as noted in the priority warning above, takes precedence over the wildcard domain.

Configuration Steps (Single Environment)

1. Go to the CloudBase Console → HTTP Gateway → Custom Domain, and click "Add Domain".
2. Enter the wildcard domain (e.g., *.example.com) and configure the wildcard SSL certificate.
3. Subsequent steps such as domain ownership verification and CNAME configuration are the same as those for a regular custom domain. See Custom Domain - Get Started.

Managing Wildcard Domains

After access is completed, you can manage wildcard domains in the domain list:

Column/Action	Description
Domain	The wildcard domain address, e.g., *.example.com
Enable	Enable or disable access for the wildcard domain via a toggle
Certificate Status	Status of the associated certificate (e.g., "Normal")
Status	Domain access status (e.g., "Normal")
Access Mode	The access mode currently used by the domain
CNAME	The CNAME value to be configured at your DNS provider
Protocol	e.g., HTTP & HTTPS
Actions	Edit, Hosters settings, Delete

Limitations

• Only wildcard domains are supported; up to 10 per platform (Platform mode)
• The wildcard domain must have completed ICP filing
• A wildcard certificate only protects first-level subdomains, not multi-level subdomains