Browse documentation
Domains & SSL
Connect a domain you own, follow the generated DNS instructions, and make it the primary address.
Where to find it
- Editor menu
- Project settings
- Domains
In this guide
A verified custom hostname with working HTTPS and the intended primary-domain setting.
Before you start: You need domain-management permission, an eligible plan, and access to the domain’s DNS settings. Publish a production release before expecting the domain to serve a website.
Connect an existing domain
Open Project settings → Domains. Use Connect Existing Domain for a domain you already own.
- 1Exact hostname. Use the hostname you want visitors to open.
- 2Generate instructions. The next screen supplies your DNS records.
- 1
Enter the hostname
In Hostname, enter the exact host you want to use, such as www.example.com. Do not include a page path.
- 2
Connect the domain
Choose Connect domain. Read any validation or plan message before proceeding.
You should see: The domain appears under Connected Domains with its verification state and DNS instructions.
- 3
Copy the generated records
Use the Ownership TXT and Routing Record shown for that hostname. Copy each record’s type, name, and value into your DNS provider’s settings.
Verify DNS and HTTPS
DNS, routing, and SSL are separate checks. A record saved at your DNS provider does not mean all three have completed yet.
- 1
Check DNS
Return to Connected Domains and choose Check DNS. If verification is pending, confirm the records and allow time for propagation before checking again.
- 2
Check SSL
Choose Check SSL. Resolve any displayed issue and wait for the certificate to be issued.
| Status | What it confirms | What to do |
|---|---|---|
| DNS | The required DNS records are visible. | Check the record type, name, and value, then choose Check DNS. |
| Routing | The hostname is attached to the site’s serving route. | Confirm the generated routing record and allow verification to complete. |
| SSL | A certificate is issued for HTTPS. | Choose Check SSL after DNS and routing are correct. |
Set and test the primary domain
The primary domain is the canonical host. Healthy secondary domains redirect to it.
- 1
Choose the verified host
Use the domain’s primary-domain action after DNS and Routing are verified and SSL is issued. The action is unavailable while those checks are incomplete.
- 2
Test HTTPS and redirects
Open the custom HTTPS address and check an inner page. Check that any connected secondary host redirects to the intended primary host.
Before you move on
- The exact hostname is connected to the correct project.
- The generated ownership and routing records are present.
- DNS and routing are verified; SSL is issued.
- A production release exists and loads over HTTPS.
Screenshots use a local sample workspace.