SSL

SSL certificates.

HTTPS that is set up once, renewed automatically, and never expires on a Friday afternoon.

HTTPS is not optional any more

Browsers mark sites without a valid certificate as "Not secure" in the address bar, next to your business name. Visitors notice, forms feel unsafe to complete, and search engines have treated HTTPS as a ranking signal for years.

The technology is settled and largely free. What still goes wrong is administration: a certificate that was installed manually two years ago, on a server nobody has logged into since, expiring on a weekend. Every browser then shows a full-page security warning until somebody fixes it.

What we provide

Free SSL on hosting

Every hosting account includes a certificate, issued and renewed automatically. There is nothing to remember and nothing to buy.

Wildcard certificates

One certificate covering all subdomains, for businesses running several services under the same domain.

Extended validation

Where an organisation wants the higher validation level, we handle the verification process with the certificate authority.

Installation

Including on servers and platforms we do not host, if you have a certificate that needs deploying correctly.

Renewal management

Expiry tracked and renewed ahead of time, so a lapse never becomes a browser warning in front of your customers.

Mixed content fixes

A certificate alone does not give you the padlock if the page still loads images or scripts over HTTP. We find and fix those.

SSL questions

Is the free certificate as secure as a paid one?
The encryption is identical. Paid certificates differ in validation level and warranty, not in the strength of the connection. For the large majority of business websites, the included certificate is genuinely all you need — and we will tell you when it is not.
Do I need a wildcard certificate?
Only if you are running several subdomains. For a single website, one standard certificate covering the domain and its www version is sufficient.
My site has a certificate but still shows a warning. Why?
Almost always mixed content — the page loads at least one image, stylesheet or script over plain HTTP. The browser then refuses to show the padlock. It is straightforward to find and fix, and we do it as part of setup.
Can you install a certificate we bought elsewhere?
Yes. Send us the certificate and key and we will install and configure it properly, including the intermediate chain that people frequently forget — which is what causes certificates to work in one browser and fail in another.

Certificate expiring, or already expired?

Send us the domain. We'll sort the certificate and stop it happening again.