How to add a custom domain with free HTTPS: step by step

To add a custom domain on Voroa, open your service’s Settings → Custom Domains, enter the domain, and select Add domain. Then create the DNS record Voroa shows you at your domain registrar: a CNAME for a subdomain like www.myapp.in, or an ALIAS/ANAME (or an A record) for a root domain like myapp.in. Voroa verifies the record and issues a free HTTPS certificate on its own.

Every service also keeps its free default address, your-app.onvoroa.com, so nothing goes offline while you set this up. A service created before 4 November 2026 has your-app.getvoroa.com as its default address instead; wherever this page says your-app.onvoroa.com, use that address.

The short version:

1. Open your service and go to Settings → Custom Domains.
2. Enter your domain and select Add domain.
3. Open View DNS in the domain’s row and copy the record.
4. Create that record at your domain registrar.
5. Wait for Verified and Certificate issued, then open your domain over HTTPS.

Which DNS record do I need?

Always copy the exact value from View DNS; it is the one that applies to your service. If the domain’s row shows DDoS protection, View DNS shows an edge address instead, and a root domain then needs ALIAS or ANAME.

Step 1 — Add your domain

1. Open your service and go to Settings.
2. Under Custom Domains, enter the domain you want to use (for example myapp.in or www.myapp.in) and select Add domain.

Voroa shows the exact DNS record you need to create. The domain is listed with two statuses - Verified status and Certificate status - and both start at amber until the record is live.

Step 2 — Create the DNS record

Go to your domain registrar (where you bought the domain) and add the record Voroa shows you:

• Subdomain (www.myapp.in): add a CNAME record
  • Name / Host: the subdomain (for example www)
  • Value: your your-app.onvoroa.com address shown in Voroa
• Root domain (myapp.in): if your registrar offers an ALIAS or ANAME record (Cloudflare, Route 53 and most modern providers do), prefer it:
  • Name / Host: @
  • Value: your your-app.onvoroa.com address shown in Voroa
• Root domain, registrar with no ALIAS: add an A record instead
  • Name / Host: @
  • Value: the IP address shown in Voroa

Save the record at your registrar.

Root domains are not always two words long. myapp.co.in, mybiz.co.uk and myshop.my.id are root domains too, even though they have three parts, because co.in, co.uk and my.id are shared domain endings rather than somebody’s domain. Voroa shows you the root-domain records for these, and the Name or Host field stays @ (or blank, if your registrar does not accept @). If your registrar adds your domain name to whatever you type in that field, leaving it blank is the safer choice.

Why the name is the better answer for a root domain. A CNAME, ALIAS or ANAME points at your your-app.onvoroa.com address, and we keep that address pointing at whichever machine is currently running your service. An A record points at one machine directly, so if your service is later moved you would have to update it yourself. Use the name wherever your registrar allows it, and keep the A record as the fallback where it does not.

Step 3 — Wait for verification

DNS changes can take a few minutes to propagate. Your domain moves through two statuses, in order:

1. Verified status turns to Verified once your record actually resolves to Voroa. Until then it reads Waiting for DNS.
2. Certificate status turns to Certificate issued once HTTPS is live on our side. Until then it reads Waiting for verification.

HTTPS is provisioned automatically — you don’t need to manage any certificates.

Both statuses describe your domain at Voroa specifically. If your domain is currently served by another host, that does not make it verified here: the status stays amber until the record points at Voroa and the certificate is issued.

If you use Cloudflare

You can keep the record Proxied (orange cloud). A proxied record shows Cloudflare’s address instead of ours, so Voroa verifies the domain by sending an HTTPS request through it and checking that Voroa answers. Set Cloudflare’s SSL/TLS encryption mode to Full (strict) or Full. In Flexible mode the domain stays at Waiting for DNS, because visitors on that mode get stuck in a redirect loop.

This is for a domain that is not served through the edge network. If the domain’s row says edge protection is ready or on, add exactly the record View DNS shows, as DNS only. See Custom domains through the edge.

Change your default subdomain

Full guide, with what happens to the old name: How to change your service’s onvoroa.com subdomain.

Every service gets a <name>.onvoroa.com address. To change it, open the service, go to Settings, then Custom domains, and select Change subdomain. Enter the new name (1-30 lowercase letters, numbers or single hyphens, starting and ending with a letter or number) and select Change and redeploy.

• The old address stops working immediately. There is no redirect. The old name stays reserved for your workspace for 30 days (you can take it back in that time); after that anyone can take it.
• If a custom domain points to the old address with a CNAME record, update that record to the new address.
• The name must be free and not reserved. If it is taken, you are told so and nothing changes.
• The change happens through a redeploy. If your monthly build minutes or free hours are used up, it is refused and nothing changes.

Notes

• Your default your-app.onvoroa.com address keeps working when you add a custom domain.
• You can add more than one custom domain to the same service.
• To stop using a domain, select Remove next to it in Custom Domains.
• To send every name under a domain (like shop.myapp.in and blog.myapp.in) to one service, see Wildcard domains.
• Where DDoS protection for custom domains is offered, the record View DNS shows can change to a CNAME to the edge address. Follow the domain’s row, and see Custom domains through the edge. Before you remove a domain whose record points at the edge, change that record first.

Common custom domain problems

Frequently asked questions

Is HTTPS free for custom domains?

Yes. Voroa issues and renews an HTTPS certificate for every verified custom domain at no extra cost. You never upload or renew a certificate yourself. See SSL and HTTPS.

How long does a custom domain take to work?

Usually a few minutes after you create the record. Some registrars take longer to publish DNS changes. The domain’s row shows Verified and then Certificate issued as soon as each step is done.

Should I use www or the root domain?

Either works, and you can add both. Many sites use www.myapp.in as the main address because a CNAME is easy to set at any registrar. If you add both, create a DNS record for each name.

How many custom domains can I add?

Each workspace plan includes a set number of custom domains, and the Custom Domains page shows how many you have used. To add more, move up a plan. See pricing for the allowance on each plan.

Will my onvoroa.com address stop working?

No. Your default your-app.onvoroa.com address keeps working after you add a custom domain.

Related

• What is Voroa?
• How to deploy a web app from GitHub on Voroa