A wildcard domain routes matching subdomains to one Agiler project with automatic HTTPS. For example, adding *.example.com lets the project serve shop.example.com, docs.example.com, and new matching names without adding each one in Agiler.
What a wildcard covers
A wildcard covers exactly one subdomain level:
| Name | Covered by *.example.com? |
|---|---|
shop.example.com | Yes |
docs.example.com | Yes |
example.com | No; add the root domain separately |
preview.shop.example.com | No; add the exact name or *.shop.example.com separately |
Use the form *. followed by a full domain name. Patterns such as shop*.example.com, www.*.example.com, and *.*.example.com are not supported. If an exact domain is also connected to a project, its routing takes precedence over the matching wildcard.
Add the wildcard
You need the Admin or Developer workspace role and access to edit the domain’s DNS records. API and MCP clients also need the projects.domains:write scope to manage domains.
- Open your project in the dashboard and select Domains.
- Click Add Domain, enter a name such as
*.example.com, and click Save. - Under Configure wildcard DNS, copy both CNAME records to your DNS provider.
For *.example.com, the records are:
| Purpose shown in Agiler | Type | Record name | Value |
|---|---|---|---|
| Traffic | CNAME | *.example.com | global.agilercdn.net |
| Certificate validation | CNAME | _acme-challenge.example.com | Copy the domain-specific value shown in Agiler |
The certificate-validation value is a generated hostname under acme.agilercdn.net. Copy the complete value from your project’s Domains page; it is different for each wildcard. If your DNS provider expects record names relative to the example.com zone, the names are * and _acme-challenge.
Keep both records configured permanently. The traffic record sends requests to Agiler. The certificate-validation record lets Agiler issue and renew the wildcard’s HTTPS certificate automatically.
Check the setup
The domain shows Provisioning while Agiler checks DNS and provisions its certificate. Allow time for DNS changes to propagate. If the domain shows Error, read the details beneath it, compare both required records with your DNS configuration, and click Recheck domain after correcting them.
Once provisioning finishes, visit a concrete matching address such as https://shop.example.com and confirm that your project’s site loads over HTTPS. Test an actual subdomain, rather than opening https://*.example.com. If you also need the root domain or deeper names, test their separate domain configurations too.
See Troubleshooting domains if checks continue to fail.
Choose a site domain
A wildcard cannot be the project’s primary Site Domain. Keep an exact domain for that purpose, such as www.example.com or the project’s generated agiler.cloud address.
You can add an exact domain that overlaps your wildcard, then use Set as site domain on that exact domain. For example, www.example.com can be the site domain while *.example.com serves the project’s other matching subdomains.