Operating HTTPS
Install your SSL certificate and keep HTTPS working
An SSL/TLS certificate is used when establishing an encrypted connection between a visitor’s browser and a server. Selecting domain coverage, installing the certificate chain and tracking renewal are parts of the same process.
Certificate validation, connection encryption and overall website security involve different checks. Use these steps to verify the connection and how your website uses HTTPS after installation.
- Verify names
- Test HTTPS
- Track renewal
01
Check the names the browser validates
During the TLS handshake, the browser checks the hostname, certificate validity and trust chain. The server must present the right certificate and prove possession of its associated private key.
Compare coverage with your base domain, www address and other required subdomains. Do not assume wildcard coverage: list each required name and confirm whether the certificate includes it before ordering.
Verify during installation
- Required hostnames and the certificate chain presented
- Validity dates and the correct server configuration
02
Maintain application security alongside encryption
After a successful TLS handshake, application data sent over that connection is encrypted. This protection alone does not prevent unauthorised access to the server or a user account.
Manage updates, account permissions and application security separately. A browser’s HTTPS indicator describes the connection; it does not guarantee that a seller is trustworthy or that the content contains no malicious software.
Manage together
- Updated applications, appropriate access and secure accounts
- Private-key protection and independent data backups
03
Use one preferred HTTPS address consistently
Choose the primary address you want visitors and search engines to use. Redirect HTTP and other domain versions to the appropriate HTTPS address, avoiding unnecessary redirect chains.
Update internal links, canonical URLs and the sitemap to match. Check images, scripts and form destinations for remaining HTTP addresses. A paid certificate alone does not deliver an increase in search rankings.
Test on your website
- Redirects, canonical URLs and sitemap addresses
- Forms, images and mixed-content warnings
04
Verify the replacement after renewal
Certificate expiry and a service billing period are different things. Track renewal requirements and domain validation, and keep the required DNS or server access available.
After installing a replacement, test the names, dates and chain seen by an external connection. If you use multiple servers or a load balancer, check every relevant connection endpoint.
Track for continuity
- Certificate expiry and required renewal validation
- Deployment of the replacement to all relevant servers