Why a website needs SSL
An SSL certificate (strictly, a TLS certificate) confirms that a website belongs to its domain and enables the encrypted HTTPS connection. Without it, browsers show “Not secure”, forms and payments trigger warnings, and visitors leave.
A certificate protects data in transit between the visitor and the server. It does not make the website itself secure — that takes CMS and PHP updates, protection and backups.
Certificates are getting shorter-lived
The CA/Browser Forum — the body that brings together certificate authorities and browser vendors — approved a phased reduction in the validity of public certificates (Ballot SC-081v3):
| Issued | Maximum validity | Reissues per year |
|---|---|---|
| before 15 March 2026 | 398 days | ≈ 1 |
| from 15 March 2026 | 200 days | ≈ 2 |
| from 15 March 2027 | 100 days | ≈ 4 |
| from 15 March 2029 | 47 days | ≈ 8 |
What this means for you. An annual certificate subscription is still possible, but the certificate itself must be reissued and reinstalled during the year. We track the dates, reissue and install certificates in advance and automate renewal wherever we can.
Which certificate to choose
| Type | What is validated | Best for |
|---|---|---|
| DV | control of the domain | most websites and stores; issued quickly |
| OV | the domain and the organisation’s existence | companies that need the organisation named in the certificate |
| EV | extended company validation | partner or regulatory requirements |
| Wildcard | the domain and its subdomains at one level | projects with many subdomains |
| SAN | several domains in one certificate | companies with several websites |
Encryption is equally strong for every type. The difference is how thoroughly the owner is checked and what appears in the certificate details.
What we do
- Choose a certificate to suit the task and budget
- Generate the key and certificate signing request (CSR) and complete domain validation
- Install the certificate with the full chain on your hosting or server
- Set up the HTTPS redirect and modern TLS protocols
- Remove mixed content — resources still loaded over HTTP
- Reissue and reinstall before the certificate expires
Common errors and their causes
- “Not secure” — the site is served over HTTP or the certificate has an error
- Expired — the renewal or reissue didn’t happen
- Issued for another domain — for example, without www or a subdomain
- Incomplete chain — the intermediate certificate isn’t installed
- Mixed content — images or scripts are loaded over HTTP