Inspect ESA configuration
01Review sites, DNS, origin pools, cache, compression, HTTPS, SaaS domains and origin rules. Retrieve all API pages and browse results in paginated tables.
Bring Namecheap domains, Baota websites and Alibaba Cloud ESA SaaS onboarding into a workflow with preflight checks and stage-by-stage progress. Designed for website teams repeatedly setting up customer domains.
Check existing resources for each domain and apply the required configuration in sequence.
Review sites, DNS, origin pools, cache, compression, HTTPS, SaaS domains and origin rules. Retrieve all API pages and browse results in paginated tables.
Filter unbound, unexpired domains using Namecheap DNS. Check DNS, matching resources and Baota websites, then review the proposed actions before execution.
Create or reuse compatible Baota sites, configure ESA service records, SaaS domains and origin Host rules, then update DNS. Wait for edge readiness before requesting the origin certificate and applying selected cache and Gzip rules.
Run one domain or a sequential batch with visible progress. Pending activation or certificates retain a retryable result and stop later domains from being written early.
Optionally save connection credentials in Windows Credential Manager. Site defaults use the current user's registry, and saved credentials can be forgotten from the tool.
The tool coordinates configuration; DNS propagation, service activation and certificate issuance remain with the respective providers.
| Scope | Capability | Use | Requirements |
|---|---|---|---|
| Alibaba Cloud ESA | Configuration inspection and SaaS resource creation | Organize domains, origins and rules | RAM permissions, an ESA site and available capabilities |
| Namecheap | Domain lookup and CNAME addition preserving existing records | Connect domain DNS to ESA | Namecheap DNS, API permissions and source IP allowlisting |
| Baota panel | Website creation and ACME certificate deployment | Prepare the origin website and HTTPS | HTTPS panel access, API allowlisting and supported site types |
| Windows and licensing | Desktop workflow and online validation | Manage onboarding from the desktop | Windows, a valid license and connectivity |
Combine tasks across several consoles into a reviewable workflow and check each domain's completion status.
Select eligible domains and follow conflicts, pending stages and successful completion one at a time.
Review site configuration and rules before confirming origins, DNS, site types and permissions.
Automated onboarding requires a valid online license and access to the relevant APIs; Baota writes require HTTPS. Conflicting root DNS or incompatible matching resources stop the workflow instead of being overwritten. Activation and certificates depend on provider status. Full caching should only be enabled for suitable public static content.
Prepare Windows, an ESA site, a Namecheap domain and the Baota panel, confirm site defaults and licensing, then start with a single-domain preflight.
Plan around your existing accounts, workflow and intended scope.
Prepare a valid license and the required permissions for each service.
Confirm Namecheap DNS, origin IP, site directory and site type.
Check DNS conflicts and certificate requirements before choosing cache and compression settings.