Protecting the connection

HTTPS uses HTTP over a TLS-protected connection. In ordinary browser use, certificate validation helps establish that the connection is to the named service, while encryption protects data in transit. This is different from deciding whether the content itself is accurate or the business is honest.

A misleading page can still be delivered over HTTPS. When entering sensitive information, check the exact hostname and the reason you are on that page. A familiar logo inside the page does not establish ownership of the address.

Names and certificates must agree

A certificate is issued for particular names. Visiting a different name, an IP address, or a service with an expired or incorrect certificate can produce a browser warning. Do not train yourself to dismiss these warnings just to make a page load.

For your own website, configure the domain through the hosting provider and wait for its certificate process to finish. Test each intended hostname independently. A working temporary hostname does not automatically prove that a newly added custom domain is ready.

What remains outside the transport layer

HTTPS does not control what a site does with information after receiving it. Retention, account security, tracking, and third-party sharing are separate questions. Read the actual data practices before submitting information that matters.

A useful review has three parts: is the connection valid, is this the intended publisher, and is the requested action appropriate? Keeping those questions separate avoids placing more trust in a padlock than it can justify.

Further reading

Original sources and related references. These links lead to independent websites; inclusion does not imply a partnership or endorsement.

Browse the complete resource shelf →