
Editorial illustration.
Originally published 16 June 2023; rewritten and reviewed on 15 October 2026.
“The website already works—why does it need HTTPS?” I still hear that question from small business owners in Malaysia who only run a company profile, a restaurant menu, or a simple WordPress inquiry site. When they hear “SSL certificate” or “TLS encryption,” it sounds like an expensive add-on meant only for banks and e-commerce checkouts.
Explaining it with acronyms rarely convinces anyone. What actually lands is talking about the road between the visitor’s browser and the server—and what happens when that road is left wide open.
Explain the connection first
HTTPS wraps standard HTTP traffic inside TLS (Transport Layer Security). In plain terms, it does two practical jobs for every visit:
- It encrypts the traffic in transit. Anyone sitting on the same network path—whether it is a public Wi-Fi router at a mamak stall, a hotel hotspot, or a compromised upstream hop—cannot casually read passwords, contact form details, or session cookies passing between the browser and your server.
- It authenticates the destination. The browser checks the server’s certificate against trusted certificate authorities so the visitor knows they are talking to
yourdomain.com, not an impersonator intercepting the request.
Even if your site has no login page and no payment gateway, plain HTTP still leaves your visitors exposed. On an unencrypted connection, an intermediate network device can alter the HTML or inject third-party scripts and ads into your page before it reaches the user’s screen. Your site does not need to process credit cards for visitors to deserve a clean, unaltered connection.
Keep the trust claim accurate
Just as important is being honest about what HTTPS does not guarantee. A valid certificate does not prove that a business is legitimate, that the information on the page is accurate, or that the web application behind it has no security bugs.
Phishing domains use valid Let’s Encrypt and Cloudflare certificates every day. An encrypted connection to a scam site is still a scam site—it just means nobody else on the Wi-Fi can eavesdrop on you getting scammed. Separating transport security (the pipe) from application security and organisational trust (what sits at the end of the pipe) prevents clients from treating HTTPS as a magic shield that replaces updates, backups, or input validation.
Browser indicators have also evolved. Modern browsers no longer show a prominent green padlock; instead, they flag plain HTTP as “Not Secure.” The screenshot retained at the bottom of this post is kept as historical context from the original 2023 article rather than a current UI reference.
Make the deployment complete
Turning on HTTPS is rarely just clicking one toggle in a hosting panel. When I audit client sites in WordPress or ASP.NET Core, half-finished TLS setups are one of the most common sources of subtle bugs.
Start by verifying what the server actually serves from the command line:
curl -I http://example.com
openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null | openssl x509 -noout -dates -subject
You want to see a clean 301 or 308 redirect from http:// to https:// and a certificate covering both the apex domain and www (or whichever hostnames you serve), with automated renewal confirmed.
If you sit behind Cloudflare, check your SSL/TLS encryption mode. Leaving it on Flexible is a classic trap: Cloudflare talks to the visitor over HTTPS, but talks to your origin server over plain HTTP. That frequently causes infinite redirect loops when WordPress (FORCE_SSL_ADMIN) or ASP.NET Core (app.UseHttpsRedirection()) sees an incoming HTTP request and keeps redirecting back to HTTPS. Always use Full (strict) with a valid Let’s Encrypt certificate or a Cloudflare Origin CA certificate installed on your server.
Next, clean up mixed content and cookie flags:
- Mixed content: Old WordPress posts often hardcode
http://image or script URLs. Runningwp search-replace 'http://example.com' 'https://example.com' --dry-runwith WP-CLI catches most of these before you commit the database update. - Nginx redirects: Terminate HTTP cleanly on port 80 and forward to HTTPS:
server {
listen 80;
server_name example.com www.example.com;
return 301 https://$host$request_uri;
}
- Cookies and HSTS: Mark session cookies with
Secure; HttpOnly; SameSite=Lax. If you enableStrict-Transport-Security(HSTS), start with a shortmax-age=300while testing, and only move tomax-age=31536000; includeSubDomainsonce you are certain every subdomain has a working certificate and a reliable renewal pipeline. A hasty HSTS header can lock users out of an internal subdomain that still runs on HTTP.
HTTPS is foundational hygiene for any public website today, right alongside keeping your CMS or framework patched and your backups tested. Protect the connection first, then focus on securing the application behind it.
Related reading
Images from the original article
The following images are retained as historical context; interfaces and configuration options may have changed.
