Confirm the certificate
Check which certificate your plan includes, and which hostnames you need covered.
KICKHOST FREE SSL
Explore included domain-validated SSL for HTTPS where it is offered with your hosting package. Confirm covered hostnames, installation and renewal before relying on the certificate for your website.
WHAT YOU GET
The free certificate most often included with hosting is domain validated. It verifies that you control the domain and enables HTTPS for the hostnames it covers. It does not verify the identity of your organisation, and it does not replace updates, access controls, malware protection or backups.
Review an organisation-validated certificate when verified business identity needs to appear in the certificate, or a wildcard or multi-domain certificate when you need coverage for eligible subdomains or several distinct names.
Compare SSL certificatesFREE OR PAID
Both types encrypt the connection when they are installed correctly. The difference is what the certificate proves, how many names it covers and how much help you get when something breaks.
| What matters | Free or included DV | Paid DV | OV or EV | Wildcard or multi-domain |
|---|---|---|---|---|
| Connection encrypted | Yes | Yes | Yes | Yes |
| What it validates | Control of the domain | Control of the domain | Domain plus organisation details | Control of the domain or domains |
| Typical coverage | One hostname, sometimes the www variant | One hostname | One hostname | Many subdomains or several names |
| Renewal | Often automated by the host | Usually annual | Usually annual, with revalidation | Usually annual |
| Help if it breaks | Depends on the hosting plan | Vendor and host | Vendor and host | Vendor and host |
| Good fit for | Blogs, portfolios, staging and most small sites | A low-cost single-name upgrade | Businesses that need verified identity | Sites with several subdomains or domains |
Coverage and renewal terms depend on the issuing certificate authority and the plan you buy. Confirm the details in your order before you rely on them.
GET READY FOR HTTPS
Check which certificate your plan includes, and which hostnames you need covered.
Follow the issuer’s domain checks. Keep the relevant DNS and access details ready.
Deploy the certificate, check the chain, and confirm HTTPS and redirects behave as expected.
AFTER INSTALLATION
A certificate makes HTTPS possible; it does not rewrite your pages. If a page loads images, scripts, fonts or forms over http://, the browser blocks the insecure parts and may remove the padlock. This is mixed content, and it is the most common reason a correctly installed certificate still produces a warning.
http:// URLs after a move.Open the browser developer tools, reload the page and filter network requests by protocol. Fix each HTTP request at its source, then purge caches and test again in a private window. If the request comes from a plugin or theme you no longer use, removing it is usually cleaner than patching its output.
Confirm the certificate is served for the exact hostname, that the chain is complete and that the page no longer requests insecure resources. The SSL checker explains the common results and what each one means.
Check a live certificateA CLEARER CHOICE