Domains & HTTPS

Help me prepare my existing project for PhotonSpark Webhost using the guide below. Ask for the project requirements and deployment choice when missing. Inspect existing files before editing, preserve behavior and data, and do not invent supported flags or deployment options. Keep credentials out of code and prompts. Explain dashboard settings and test production behavior. Publishing, DNS changes, and destructive actions need my authorization. Report what passed and what remains unverified.

# Domains & HTTPS

Connect a hostname, verify DNS delegation, and let Webhost manage its certificate.

Source: https://webhost.photonspark.com/docs/domains

## Connect a domain you control

Use direct-a or alias-cname according to the dashboard's setup instructions. Do not copy server IP addresses from old tutorials. DNS propagation and caching can delay what different resolvers see.

1. Add your zone using PhotonSpark DNS or connect a supported Cloudflare account.
2. For PhotonSpark DNS, set the domain's nameservers at your registrar to the exact nameservers shown by Webhost. Adding a zone in Webhost alone does not change the registrar.
3. Check delegation status. Needs delegation means Webhost has not verified the parent DNS delegation it requires.
4. Create the Site or App hostname and use the DNS records Webhost provides. If DNS is managed elsewhere, add the required records there.

## Enable HTTPS

Select the supported TLS mode for the resource. The usual HTTP-01 flow requires the hostname to reach the platform so the certificate challenge can complete. DNS-01 through Cloudflare requires the appropriate zone access.

Check the Certificates or TLS view for issuance status and errors. Enable HTTP-to-HTTPS redirects after checking the intended route. Do not repeatedly recreate the resource to retry certificate issuance.

- [Deployment verification](https://webhost.photonspark.com/docs/deployments)

## Check each layer separately

Replace the example hostname and health path with your application's values. DNS resolution, TLS issuance, proxy connectivity, and an application's own HTTP response are separate checks. A certificate being Ready does not establish application health.

```sh
dig NS example.com
dig A app.example.com
curl -I https://app.example.com/
curl --fail https://app.example.com/api/healthz
```