A platform address proves that your app is online. A domain you own makes the product easier to remember and keeps its public identity under your control.
Connecting a domain has three parts. The live app must work. Your domain settings must send visitors to it. HTTPS must show the padlock that protects visitors. Check the parts in that order so you know where a problem starts.
Which address should be the main one?
Choose one address before changing anything. The root domain is the shortest version, such as company.com. A subdomain adds a label, such as www.company.com or app.company.com.
- Use the root domain when the app is the brand's main destination.
- Use
wwwwhen that is already your primary website address. - Use
appor another subdomain when the marketing site and product are separate.
Write down the final choice. Sign-in return pages, links in emails, and preview cards shown on social apps should all use it. So should the sitemap, which is the list of public pages given to search engines.
Does the existing app work first?
Open the default JustDeploy address. Test the home page and one deeper page, then confirm that the intended version has a Live badge in the Deployments list.
A custom domain changes how visitors reach the app. It does not repair a broken release.
How do you connect the domain?
- Open the project's detail page in JustDeploy.
- Find Custom Domain and choose Connect. The dialog is called Connect domain.
- Enter the exact root domain or subdomain in Domain, then select Connect.
- Expand DNS records on the domain card. Copy each record's Type, Name, and Value.
- Add those records at the company where your domain settings are managed.
These domain settings are commonly called DNS records. They tell the internet where the address should lead. A coding AI can explain the fields, but only someone with access to the domain account can save them.
Which record type should you add?
| Address | Typical record | Name field |
|---|---|---|
| Subdomain | CNAME—a name that points to the JustDeploy address | The label only, such as www or app |
| Root domain | A records—address entries that point to the numbers JustDeploy shows | @, or blank if the provider uses that convention |
Use the values shown for your own project. Never copy a target from a tutorial, screenshot, or another app.
Why are there extra records for HTTPS?
JustDeploy also shows records that prove you control the domain. These let JustDeploy create the certificate used for a secure HTTPS connection. Add every record shown. Missing validation records can leave the certificate pending even when the address points to the app.
After you save the records, the change needs time to spread between domain providers. It often finishes within minutes but can take 24–48 hours. Avoid repeated edits while the displayed values already match.
Why is the domain still pending?
- The name is duplicated: some providers add the domain automatically, so entering the full address can create
www.company.com.company.com. - An old record conflicts: an older domain record may already use the same name.
- A certificate validation record is missing: traffic may arrive while HTTPS stays pending.
- The domain is connected elsewhere: disconnect it from the old JustDeploy project before moving it.
- The change is still spreading: if every value matches, wait before editing again.
Before deleting an old record, confirm that another website or email service does not depend on it.
Which app settings need the new address?
Search the project for the old platform address, preview links, and localhost, which means your own computer during testing. Update the return pages used by sign-in and payments. Also update links in emails, preview cards on social apps, and the sitemap used by search engines. If another service sends a message back to your app—a webhook—give it the new address too.
If the public address is stored in a private setting in your hosting project, publish a new version after the change. This gives the live app the new value.
How do you test the finished domain?
- Open the domain over HTTPS in a private browsing window and confirm that the browser shows no certificate or connection warning. The security icon varies by browser.
- Paste a deeper page address and refresh it.
- Complete the main form, payment, or sign-in flow.
- Open images, uploads, and downloads.
- Check social previews, the sitemap, and email links.
- Confirm that sign-in and payment services return people to the new address.
The work is finished when the app, domain settings, HTTPS connection, and generated links all use one public address. Opening the home page alone is not enough.
What should you read next?
- I Vibe-Coded an App. Now What?
- Why Your AI App Works in Preview but Breaks Online
- AI App Launch Checklist for Solo Founders
Open the JustDeploy custom domain guide beside your domain provider and copy only the values shown for your project.