SSL types

| Type | DNS validation | Best for |
|---|---|---|
| Tenbyte SSL (Free) | Automatic | System-generated *.tenbytecdn.com host. Zero setup. |
| Let’s Encrypt | Domain validation via HTTP-01 / DNS-01 | Custom domains where you control DNS. Free, auto-renews. |
| Custom SSL | You manage | Bring-your-own cert (EV, wildcard, internal CA, multi-SAN). |
Provision a certificate
Tenbyte SSL (free)
Auto-issued for the system-generated hostname. Nothing to configure.Let’s Encrypt
- Pick Let’s Encrypt as the SSL type.
- Confirm the custom domain CNAMEs to your distribution:
- Click Issue certificate. Validation runs automatically.
- Status moves from
Pending→Activeonce issued. Auto-renewal handles future cycles.
Custom SSL
Upload an existing cert. See Custom Certificates for the full upload flow and PEM format.Verify the cert
https://www.ssllabs.com/ssltest/) gives you a deeper grade.
Additional SSL settings

| Setting | What it does | When to use |
|---|---|---|
| SNI Hostname | Sent during the TLS handshake. | Set if your origin’s TLS cert doesn’t match the distribution hostname. |
| Redirect HTTP → HTTPS | Sends 301 for any plain-HTTP request. | Always on for production. |
| HTTP/2 | Multiplexed connections. | Always on — universally supported. |
| HTTP/3 (QUIC) | UDP-based transport, faster on lossy networks. | On for end-user-facing distributions; off if you have strict-firewall users. |
Verify the protocol
Renewal and rotation
| Cert type | Renewal |
|---|---|
| Tenbyte SSL | Automatic. No action needed. |
| Let’s Encrypt | Automatic, ~30 days before expiry. Failures emit a webhook. |
| Custom SSL | You are responsible. Watch notAfter and upload the new cert before it expires. |
notAfter and a hard alert 7 days before.
Operational tips
- Mixed-content audits — once HTTPS redirect is on, scan your site for
http://asset URLs. - HSTS — add
Strict-Transport-Securityvia response headers only after you’re sure all subdomains are HTTPS. - Cipher / version — Tenbyte CDN serves TLS 1.2 and 1.3 with modern cipher suites. Older clients (XP, ancient Android) won’t connect.
- Origin TLS — the edge talks TLS to your origin too. If you use a self-signed cert, mark the origin as such; otherwise the cert must validate.
Troubleshooting
| Symptom | Fix |
|---|---|
Cert stuck at Pending | DNS not resolving to the distribution. Confirm CNAME and wait for TTL to expire. |
| Browser shows cert mismatch | SNI Hostname misconfigured, or DNS resolves to a different distribution. |
| Origin handshake fails | Set the SNI Hostname to match the origin’s cert CN. |
| Mixed-content warnings | Your HTML still references http://... assets. Update or rely on protocol-relative URLs. |
| HTTP/3 not negotiated | Client or network blocks UDP/443. Falls back to HTTP/2 silently. |