OOmnistu

Blog / Web & Ecommerce

Web & Ecommerce

HTTPS and TLS for business sites: certificates, mixed content and HSTS

Understand TLS certificates, mixed content and HSTS when reviewing secure connections for a business website.

OOmnistu
Reviewed 2026-11-16 · 2 min read

HTTPS is HTTP carried over TLS. MDN's page on Transport Layer Security (https://developer.mozilla.org/en-US/docs/Web/Security/Transport_Layer_Security) describes TLS as a protocol that lets a client talk securely to a server across an untrusted network.

What TLS gives you

MDN lists three protections: encryption (data in transit cannot be read by attackers), integrity (an attacker cannot secretly modify data in transit without detection) and authentication (the server can prove it is who it claims to be; on the web, usually only the server does). HTTPS is the defence against a manipulator-in-the-middle attack. MDN also notes that browsers treat HTTPS pages as a secure context, and many powerful web APIs only work there. Its position is that all websites should serve all pages and subresources over HTTPS.

Certificates

For server authentication, a site needs a digital certificate that binds its keys to its domain name. MDN names Let's Encrypt as a widely used nonprofit certificate authority issuing free certificates, and says modern hosting services often manage certificates for you, by default or through a setting. Ask your host whether yours does and who renews it.

TLS versions

MDN says the current version is TLS 1.3, the most widely used; TLS 1.2 is still used by some sites; TLS 1.1 and 1.0 should no longer be used. For your own server, MDN points to Mozilla's TLS Recommended Configurations and a configuration generator. Version guidance changes, so check those pages when configuring.

Mixed content

If an HTTPS page loads scripts, styles, images or fonts over HTTP, that is mixed content. MDN says it is unsafe because those resources lose HTTPS protection and could be modified, and that browsers do not allow it: depending on the resource type they upgrade the request to HTTPS or block it. If you cannot fix every URL, a Content Security Policy with upgrade-insecure-requests tells the browser to upgrade them.

Redirects and HSTS

Visitors may still type http:// addresses. MDN says to redirect HTTP to HTTPS with a 301. It warns this first request can be intercepted (an "SSL stripping" attack), so servers should also send the Strict-Transport-Security (HSTS) header. After the first visit it makes the browser connect over HTTPS directly until the record expires. Chrome also keeps an HSTS preload list for domains, and MDN says Safari and Firefox behave similarly with a list derived from it. We did not research preload submission rules or the risks of long HSTS lifetimes, so treat that as something to confirm with MDN's HSTS page before enabling.

Checklist for your developer

  1. Is a valid certificate installed, and does it renew automatically?
  2. Do all http:// URLs redirect to https:// with a 301?
  3. Does any page load a script, image or font over http://?
  4. Is TLS 1.0/1.1 disabled?
  5. Has HSTS been considered, and tested before a long lifetime is set?

The checklist is ours, based on the page.

Limits

This is an overview. We did not read MDN's HSTS reference, mixed content page or Mozilla's configuration guidance.

By Omnistu.

Sources

Previous
Is your business content helpful? A self-assessment based on Google's own questions