---
title: SSL/TLS
description: The technology behind HTTPS that encrypts data between browser and server — foundation for trust, forms, and online transactions.
canonical: https://penasihathosting.com/en/hosting-wiki/ssl-tls
type: wiki
locale: en
updated: 2026-07-15
author: Willya Randika
---

# SSL/TLS

## Overview

- **Summary:** The technology behind HTTPS that encrypts data between browser and server — foundation for trust, forms, and online transactions.
- **Author:** Willya Randika ([profile](/penulis/willya-randika))

## Article

**SSL/TLS** encrypts the connection between your website and a visitor’s browser so data (logins, forms, payments) is harder to intercept in transit. The familiar signs are a URL that starts with **`https://`** and a padlock icon in the browser.

## A Simple Analogy

Without encryption, you mail sensitive papers in an open envelope. With SSL/TLS, the contents sit in a **locked vault** only the legitimate endpoints can open. That lock is negotiated automatically whenever someone loads your site.

## SSL vs TLS

**TLS** (Transport Layer Security) is the modern successor to **SSL** (Secure Sockets Layer). Classic SSL is obsolete.

Hosting pages still say “Free SSL” because the brand stuck. Under the hood you almost always get **modern TLS**.

## How It Works (Short)

When a visitor opens your site:

1. The browser asks the server to identify itself  
2. The server sends a **certificate** (a digital ID)  
3. The browser checks that the certificate is valid and trusted  
4. An encrypted session starts (the *handshake*)  

It finishes in a fraction of a second without extra clicks from the visitor.

## Why It Matters

- **Trust** — browsers label plain HTTP as “Not Secure”  
- **Sensitive data** — logins, checkout, and personal forms need protection  
- **SEO** — HTTPS is a ranking signal; competitors on HTTPS have the edge  

## Common Certificate Types

| Type | Best for | Notes |
| --- | --- | --- |
| **DV** (Domain Validation) | Blogs, SMBs, brochure sites | Most common; free via Let’s Encrypt |
| **OV** (Organization Validation) | Companies | Organization identity checked; paid |
| **EV** (Extended Validation) | Banks / large commerce | Strict checks; rarer in modern browser chrome |
| **Wildcard** | Many subdomains | One cert for `*.example.com` |

For most sites, **DV Let’s Encrypt** is enough.

## Free vs Paid

Most hosts include Let’s Encrypt with auto-renewal. Consider paid options if:

- You need a **wildcard** and your plan does not include one  
- Compliance or enterprise policy asks for **OV/EV**  

A blog or company profile rarely needs a paid upgrade just for a “premium” label.

## What to Watch For

- **Keep auto-renewal on** — Let’s Encrypt lasts ~90 days; let the panel renew it  
- **Mixed content** — leftover `http://` assets can still trigger “Not Secure”  
- **Redirect HTTP → HTTPS** — force visitors onto `https://`  
- Issue certificates **per domain** (including [addon domains](/en/hosting-wiki/addon-domains))  

To inspect a live certificate, use the [SSL Checker](/en/tools/ssl-checker) tool.

## FAQ

<Accordion>
  <AccordionItem title="Does SSL slow a website down?">
    Older setups had noticeable overhead; modern TLS impact is usually tiny. Security benefits outweigh the cost for almost every site.
  </AccordionItem>
  <AccordionItem title="How do I install SSL in cPanel?">
    Open [cPanel](/en/hosting-wiki/cpanel) → SSL/TLS or Let’s Encrypt → choose the domain → Issue. It often completes in minutes if DNS is already correct.
  </AccordionItem>
  <AccordionItem title="Certificate is active but the browser still says Not Secure?">
    Check mixed content: images or scripts still loading over http. Fix asset URLs or force HTTPS, then hard-refresh the browser.
  </AccordionItem>
  <AccordionItem title="Does email need SSL/TLS too?">
    Mail connections (IMAP/POP/SMTP) should also use encrypted ports. That ties into [SMTP](/en/hosting-wiki/smtp) and mail client settings, separate from the site padlock.
  </AccordionItem>
</Accordion>