Connect a Custom Domain

Custom domains let people open your deployed project from your own domain, such as app.example.com or www.example.com. They are available on paid plans and include automatic HTTPS. Each project can have one custom domain.

Your Getlaunch URL remains available while DNS and SSL are activating, so you can keep sharing or testing the project during setup.


Setup Checklist

  1. Open the project in your dashboard.
  2. Open the Domain panel.
  3. Enter the hostname you want to connect.
  4. Add the CNAME and TXT records shown by Getlaunch at your DNS provider.
  5. Wait while Getlaunch checks the records. The panel checks automatically while it's open, or click Check now.
  6. Wait for SSL to become active.
  7. Open the domain with https://.

DNS propagation and SSL activation usually take 5-30 minutes, but some DNS providers can take longer.

A domain has 7 days to be verified. If it still isn't live by then, it is removed automatically so the hostname isn't held forever. You can add it again any time.


CNAME Record

The CNAME record points your hostname to Getlaunch.

Use the exact target shown in the dashboard. For the record name, many DNS providers want only the subdomain part:

  • For www.example.com, use www
  • For app.example.com, use app
  • For toko.example.co.id, use toko (the domain you registered is example.co.id)
  • For an apex/root domain like example.com, use @ if your DNS provider supports CNAME flattening

If your provider does not support CNAME flattening for apex domains, use a subdomain such as www.example.com or app.example.com.


TXT Records

TXT records prove ownership and allow SSL validation.

Add every TXT record shown by the dashboard:

  • Ownership TXT
  • SSL TXT. There are often two SSL records with the same name and different values. Add both. Some DNS providers, such as AWS Route 53, refuse two records with one name: there, create one TXT record and put each value on its own line, each in double quotes. Others take two separate records with the same name.

The SSL records can appear a minute or two after you add the domain. Copy the name and value exactly. Do not remove quotes unless your DNS provider adds them automatically.


Status Meanings

Waiting for DNS

The required DNS records have not been detected yet, or ownership hasn't been confirmed.

Issuing SSL

DNS is verified and the certificate is being issued and attached.

Live

The custom domain is live with HTTPS.

Needs attention

Something stopped the domain from going live: the records weren't found in time, the domain no longer points to Getlaunch, or the certificate expired. Fix the records shown in the panel, then click Retry verification.


Troubleshooting

DNS records look correct but status is still waiting

Wait a few minutes and click Check now again. Some providers cache DNS changes longer than expected.

CNAME is not detected

Check whether the DNS provider expects www instead of www.example.com in the record name.

TXT is not detected

Copy the TXT name and value again. Extra spaces, missing prefixes, and quote handling are common causes.

Apex domain is not working

Some DNS providers do not allow CNAME records on root domains. Use www.example.com, or enable CNAME flattening/ALIAS/ANAME if your provider supports it.

The status says verification timed out

Getlaunch stops waiting after a while. Check every record against the panel, then click Retry verification.

HTTPS is not active yet

SSL issuance starts after DNS is detected. Keep the records in place and check again after a few minutes.