What is HTTPS?

TLS protects the connection over an untrusted network. In ordinary web browsing, the server authenticates itself to the browser; the browser does not normally use a client certificate to authenticate the person. Account sign-in is a separate application function. TLS on the web.

Protect the connection without overstating trust

A contact form can contain information that needs protection during transfer. Serving it over HTTPS addresses that transport concern. It does not show how the business stores the information, who has access later, or whether the offer on the page is reliable.

The TLS handshake sets up the connection

During the handshake, client and server agree on protocol settings and keys, and the server authenticates itself. Afterward, the negotiated keys protect the transferred messages. There is no universal handshake-duration figure established here. TLS handshake.

HTTP and HTTPS describe different transport protection

The https URL scheme indicates HTTP over TLS. An http URL does not provide that TLS protection. Moving a site between schemes also changes its URLs, so treat the transition as a migration rather than just installing a certificate.

An HTTPS page can still reference insecure resources

Mixed content occurs when a secure page requests subresources over HTTP. Browsers upgrade some resource requests to HTTPS and block others; saying that every insecure image is simply blocked is too broad. Mixed-content handling.

HTTPS checks describe different issues
ObservationWhat to inspect
Page loads over HTTPSCertificate, hostname and TLS connection
An HTTP resource appears in page markupThe resource URL and the browser’s upgrade or blocking behavior
Old HTTP page URL still existsIts response and intended HTTPS destination

A certificate binds the site’s public key to its domain name for server authentication. HTTPS is the protected HTTP communication that uses TLS, not the certificate file itself. Server authentication.

See SSL certificate for the credential and its lifecycle.

Handle an HTTP-to-HTTPS move as a URL migration

Google’s migration guidance recommends mapping old URLs to their replacements, using server-side permanent redirects where possible, and updating canonical links to the new URLs. It also identifies HTTP-to-HTTPS changes as site moves. Site moves with URL changes.

Do not infer the result from a browser icon

Check the final URL and network responses, including images, scripts and styles. Verify the intended host and test important forms after a change. A browser’s connection indicator is not a measurement of conversions, security of stored data or search ranking.

HTTPS questions

Does HTTPS mean the website itself is trustworthy?

HTTPS protects a connection and supports server authentication. You still need to assess the site’s identity, offer and content separately. Encryption in transit does not establish that a claim is true or that a business will handle your data appropriately.

Is switching the URL scheme enough?

No. Google’s migration guidance includes configuring the required TLS certificates, checking the replacement URLs and their canonicals, and planning redirects from the old URLs. Test the completed move rather than assuming a scheme change fixes every resource and navigation path.

SSL certificate · 301 redirect · Canonical URL

Sources