An SSL certificate must cover the hostnames visitors actually use and be installed on the server that terminates their HTTPS connection. A certificate for the main domain does not automatically cover every unrelated hostname or nested subdomain. Check the requested names and service scope before generating an order or certificate signing request.
Recommended workflow
- List the exact primary, www and subdomain names that need HTTPS, and confirm which names the selected certificate covers.
- Confirm the destination hosting server, DNS ownership and validation method before creating the certificate request.
- Install the issued certificate with its required chain, test externally, and record how renewal or reissuance will be handled.
Control validation is a separate step from purchasing the service. Depending on the issuer, you may need to publish a DNS record or make a validation resource available. Existing CAA records, incorrect DNS or an unreachable validation endpoint can prevent issuance even when an order has been paid.
After installation, test the hostname, certificate chain and browser connection before enabling a permanent HTTPS redirect. Keep private keys out of support messages and public folders. Weeby SSL plans use a twelve-month service subscription; certificate validity follows the issuer requirements, so reissuance can be necessary during that subscription. Plan renewal and reissuance checks before expiry rather than waiting for browser warnings.
