Skip to content

A Site can have a platform address and, where the domain workflow is available, an existing custom domain. Connecting a domain points it at an authorized Site; it does not transfer domain registration or purchase anything.

Connect and verify

Choose the intended Site and domain. Complete the shown ownership and DNS steps, then wait for routing and TLS readiness before using the hostname publicly. DNS propagation and certificate setup may take time. Keep the working Site route available while a custom domain is pending or an update fails.

The Workspace owns the domain relationship and its financial obligations. Site management alone does not grant domain purchase, payment, or transfer authority. Review Permissions and the current domain status before changing a binding.

Example: connect a customer address

To use a hostname such as portal.example.com, select the intended Site and follow the DNS values shown by its domain workflow. Keep using the known working Site address while ownership, routing, or certificate checks remain pending.

Once ready, visit the custom hostname and verify the expected release and visitor access. If it reaches the wrong destination, inspect the domain binding before making unrelated source changes. See Site access.

Keep routing separate from publishing

A domain change selects where traffic goes; it does not publish a newer source revision. If the hostname works but shows an older result, inspect the Site's active Release. If the release is correct but the hostname fails, investigate the domain status and DNS values shown in the setup flow.