Automatic HTTPS means your website gets a valid security certificate and an encrypted connection the moment it goes live — issued and renewed for you, with nothing to buy, install, or configure. The little padlock in the address bar just appears, and stays. To understand why that's a big deal, it helps to know what HTTPS is doing in the first place.
HTTPS encrypts the connection between your visitor and your site, and proves the site is really yours. "Automatic" means the certificate that makes this possible is issued and renewed for you — you never touch it.
What HTTP, HTTPS, TLS, and SSL actually mean
These terms get tangled together, so quickly: HTTP is the language browsers and websites speak. HTTPS is the same language, encrypted. The encryption is provided by TLS (Transport Layer Security) — the modern successor to the older SSL, though people still say "SSL certificate" out of habit. When you hear "SSL certificate," "TLS certificate," and "HTTPS certificate," they're all pointing at the same thing: the credential that lets a site prove its identity and encrypt its traffic.
What that certificate does
A TLS certificate does two jobs at once. It encrypts the connection, so what passes between your visitor and your site can't be read or tampered with along the way. And it authenticates your site, so the browser can confirm your visitor is really talking to your site and not an impostor. Both together are what turn "http://" into "https://" and light up the padlock.
How the certificate gets used — the handshake
Every time someone visits an HTTPS site, the browser and the site do a quick, invisible negotiation called a TLS handshake. The browser says hello, the site presents its certificate, they agree on encryption keys, and from that point on everything is encrypted. It happens in a fraction of a moment, before the page appears. Here's the sequence:
Why "automatic" is the part that matters
The handshake has always worked like that. What used to be painful was getting and keeping the certificate. In the old model you'd buy a certificate, prove you owned your domain, install it on your server, and then remember to renew it before it expired — because an expired certificate turns your site into a scary browser warning overnight. Automatic HTTPS removes every one of those steps:
- Issued for you — a valid certificate is provisioned automatically when your site goes live.
- Renewed for you — certificates expire on a schedule; the network renews them quietly before they do, so your padlock never lapses.
- Nothing to install — there's no server to upload a certificate file to and no configuration to get wrong.
- On by default — HTTPS isn't an upgrade you opt into; every site is served encrypted from the first request.
Why every site needs HTTPS now — even a simple one
It's tempting to think a small site "doesn't need" encryption. It does. Browsers now visibly mark plain HTTP pages as "not secure," which erodes trust instantly. Search engines prefer secure sites. And encryption protects your visitors regardless of how simple your page is. HTTPS stopped being a feature for shops and logins a long time ago — it's the baseline for being online at all.
How this works on Just Web Hosting
Every site published with Just Publish is served over HTTPS with a valid certificate from the moment it's live — issued and renewed automatically, with nothing for you to buy or configure. The same applies when you connect your own domain: the certificate is handled for you there too. It's one less thing to think about, which is rather the point.
HTTPS on every site, handled for you.
Just Publish serves every site over automatic HTTPS from the first request — no certificate to buy or renew.