People often read a browser’s HTTPS indicator as a sign that a website is safe. It confirms a narrower protection: the connection is encrypted. The site receiving your data still needs its own security checks.

What HTTPS verifies

HTTPS protects data in transit between the browser and server. Someone observing an untrusted network cannot simply read the login credentials, payment details, or session tokens as plain text. That protection ends at the systems handling the data.

A domain-validated certificate confirms control of the domain. It does not assess the operator’s legitimacy or the application’s security practices. A site built to steal credentials can obtain a valid certificate too.

Attackers figured this out years ago

Phishing sites can use HTTPS, so the encrypted connection does not make their login forms trustworthy. Check the domain and the reason for the request before entering credentials. The certificate cannot make that decision for you.

What HTTPS doesn't cover

The server still has to handle requests safely after receiving them. TLS does not check account permissions, input validation, or the application’s business rules.

Security headers are a separate layer entirely. Whether your site restricts what scripts are allowed to run, blocks itself from being embedded in a malicious iframe, or stops browsers from misreading file types, none of that has anything to do with your certificate. A perfectly encrypted connection can still deliver a page vulnerable to cross-site scripting or clickjacking, because HTTPS was never designed to answer those questions.

Cookie attributes are configured separately from TLS. Check Secure, HttpOnly, and SameSite on session cookies and review how the application uses them. Enforcing HTTPS does not automatically set these protections.

Cross-origin resource sharing configuration is another blind spot. An encrypted API can still be configured to trust any requesting origin by default, which hands out authenticated access to your data regardless of how strong the underlying encryption is. The connection being private doesn't mean the data behind it is protected from the wrong requester.

Check HTTP redirects, accepted protocol versions, and mixed content separately. An HTTPS page may still request resources over plain HTTP, and a visitor’s initial request may reach HTTP before being redirected.

Two padlocked sites, two different realities

Two sites can both support HTTPS while differing in their headers, session protections, account permissions, and API configuration. The connection indicator does not show those differences.

Seeing past the padlock

Ceron Check inspects headers, cookie flags, CORS, and transport behavior at a public URL. It returns the observed evidence and suggested fixes, ordered by severity. The read-only check is free and requires no login or installation.

Require HTTPS, then verify the other controls your application relies on. Encryption protects the connection; account and application tests establish who can reach the data at either end.

Back to the blogExplore Ceron