How to add a wildcard domain like *.myapp.in on Voroa
Send every name under your domain, like shop.myapp.in and blog.myapp.in, to one Voroa service with a wildcard domain, two DNS records and automatic HTTPS.
A wildcard domain sends every name one level under your domain to the same service. Add
*.myapp.in once, and shop.myapp.in, blog.myapp.in and any other name you create later all reach
your service over HTTPS, with no extra setup per name. Wildcard domains are available on every plan.
How a wildcard counts against your plan
- A wildcard counts as one custom domain against your workspace plan’s limit, however many names sit under it. It counts from the moment you add it, including while it is waiting to be verified.
- When you have used every custom domain your plan includes, a paid plan can add one more at a time at the price per domain per month shown on the pricing page, plus GST. The price is shown before the domain is added, and nothing is added until you confirm it. Each plan has a maximum number of custom domains in total; above it, upgrade your plan.
- An extra domain is billed after use, on a later monthly bill. Any part of a calendar month is charged as a full month.
- On the Free plan extra domains are not sold. Upgrade your plan to add more.

Step 1 — Add the wildcard
- Open your service and go to Settings, then Custom Domains.
- Enter the wildcard, for example
*.myapp.in, and select Add domain.
The domain appears as Ownership not verified. Nothing is served on it yet. Before any traffic reaches your service, you prove that you own the domain.
Step 2 — Create both DNS records
Open View DNS in the domain’s menu. You will see two records. Add both at your DNS provider.
| Record | Type | What it does |
|---|---|---|
_acme-challenge |
CNAME | Proves the domain is yours and lets Voroa issue its wildcard certificate. The value is unique to your domain - copy it exactly. |
* |
CNAME | Sends the traffic for every name under the domain to your service. |
If your wildcard sits under a subdomain, for example *.shop.myapp.in, the record names include it:
_acme-challenge.shop and *.shop. The dashboard always shows the exact names to use.
If your DNS provider can proxy records, set both records to DNS only. A proxied ownership record cannot be checked, and a proxied traffic record hides the certificate check.
Step 3 — Verify
After adding the records, select Verify next to the domain. If the ownership record is not visible yet, Voroa tells you which record is still missing - DNS changes can take a few minutes to spread, so try again shortly.
Once verified, the domain starts routing and its certificate is issued automatically. The status then follows the same steps as any custom domain: Verified, then Certificate issued.
Keep the ownership record in place
Voroa checks the _acme-challenge record every day. It is also how the certificate renews. If the
record is removed or changed and stays that way for three days in a row, the wildcard stops
serving and goes back to Ownership not verified, and the account owner gets an email. Put the
record back and select Verify again to restore it.
A wildcard that is added but never verified is removed after seven days, so it does not keep counting against your plan.
Notes
- A wildcard covers one level only.
*.myapp.incoversshop.myapp.inbut notmyapp.initself, and nota.shop.myapp.in. Add the bare domain separately if you need it. - A name you add on its own, like
www.myapp.in, always takes priority over your wildcard for that name. Use this to send one name to a different service. - If your domain has a CAA record, it must allow
letsencrypt.org, or the certificate cannot be issued. - You cannot add a wildcard for a public suffix such as
*.co.in, or for a Voroa address.