Domains and SSL

What domains and SSL do

Domain and SSL tools help route traffic, configure provider DNS records, manage platform subdomains, select primary domain behaviour, issue certificates, renew certificates, and keep HTTPS status visible after launch.

Before moving DNS

• Decide which hostname is primary.
• Decide whether www, apex, wildcard, staging, or preview hostnames are needed.
• Confirm the site works on a temporary platform domain.
• Check whether ForgedBase or the client DNS provider will manage records.

Typical workflow

1. Add the site domain.
2. Copy or create the required DNS records.
3. Wait for DNS to point at the correct target.
4. Issue the SSL certificate.
5. Enable HTTPS behaviour after the certificate is active.
6. Monitor renewal status and failure context.

Checks before enabling HTTPS redirects

• DNS points to the intended server or site.
• The certificate is active for every hostname that will receive traffic.
• The application knows its production URL.
• The apex and www behaviour is documented.
• Wildcard coverage is present when subdomains need HTTPS.

Common issues

• The apex domain works but www does not.
• HTTPS redirects are enabled before the certificate is ready.
• The wrong DNS zone was edited.
• A wildcard certificate is expected, but only one hostname is covered.

Related guides

• How to manage domains and SSL for client sites
• How to deploy a Laravel site on a cloud server
• How to deploy a PHP site with Git and SSL