SSL certificates: what your business website needs
An SSL certificate, more accurately a TLS certificate in modern use, helps a browser verify the server it is connecting to and establish a protected connection. It is a basic part of HTTPS, but it is not a guarantee that the website's business is trustworthy or its software is free of vulnerabilities.
For a business owner, the important questions are whether the correct hostnames are covered, renewal works and the connection is configured properly. The certificate's purchase price alone cannot answer those questions.
What HTTPS protects
TLS helps protect information in transit between the browser and server against eavesdropping and undetected modification. It does not automatically protect information after it reaches the application, secure a compromised device or prevent someone entering information into a convincing fraudulent website. MDN TLS documentation.
That means HTTPS should accompany secure application maintenance and access controls. Our WordPress security guide explains the additional layers.
Understand validation and coverage
Domain validation establishes control of the relevant domain. Other certificate categories add organisation checks according to their rules. Additional identity checks do not, by themselves, make every encrypted connection stronger or make the application more secure.
Match the certificate to the names you actually use. The main hostname, a www variant and separate subdomains need appropriate coverage. A wildcard has a defined scope and should not be assumed to cover every possible nested name.
Ask for a specific reason before buying a particular certificate category. A contractual or sector requirement should be identified in the applicable document, not inferred from a general statement that banks or healthcare organisations need a paid certificate.
Free certificates can be a practical option
Let's Encrypt is an automated certificate authority. Its ACME-based process allows an authorised client to prove domain control and request certificates. Automation can reduce manual renewal work, provided the validation and deployment continue to function. Let's Encrypt explanation.
Free issuance does not remove every operating cost. Someone still manages the server, DNS permissions, monitoring and repair if renewal fails. Compare a provider's service on that basis rather than equating a certificate line item with the whole HTTPS service.
Renewal needs verification
Record who owns certificate renewal and how failures are detected. A certificate can stop renewing after a DNS change, an expired API credential, a routing change or a configuration error. Check the certificate actually served to visitors, not only the file saved somewhere on the server.
Avoid building a manual process around a fixed certificate lifetime quoted in an old article. Follow the current authority and client guidance, automate where appropriate and monitor expiry independently.
When moving a WordPress website, prepare the certificate for the new environment and test the intended hostname before the final switch. Do not assume the old provider's certificate configuration moves with the files.
Look beyond the certificate
The server's protocol and cryptographic configuration matter. Use current maintained server guidance and check compatibility with the clients you need to support. Review redirects, mixed content and any reverse proxy between the visitor and the application.
A CDN may terminate one connection while a separate connection reaches the origin. Both parts need an appropriate configuration. A valid certificate at the edge does not tell you everything about the origin path.
A public TLS test can expose certificate and protocol issues. Its grade is a useful observation, not a comprehensive security assessment or proof of compliance. Test the real site and customer journeys too.
Ask the hosting provider these questions
| Question | Why it matters |
|---|---|
| Which names are covered? | Visitors may use more than one hostname |
| Who manages renewal? | Automation still needs an accountable owner |
| How is failure detected? | A silent renewal failure becomes a public warning |
| What happens during migration? | The new environment must serve valid HTTPS |
| Who fixes application issues? | Certificates do not update vulnerable plugins |
ResaHost SSL certificates form part of the managed service described in the applicable plan. Use pricing and scope to check the whole offer rather than buying a badge in isolation.
Common questions
Frequently asked questions
Does the browser's secure-connection indicator prove a business is legitimate?
No. It concerns the connection, not an endorsement of the seller.
Will a certificate fix a hacked website?
No. Investigate and remove the compromise, repair the cause and restore from a verified position where needed.
Should I ignore a certificate warning during a move?
No. Resolve the hostname or configuration issue and verify before directing customers to the new environment.