You may notice that one web address begins with http:// and another with https://. The difference matters when information travels between your browser and a website. It is also easy to give HTTPS more credit than it deserves, so start with what it actually does.
The connection is encrypted
HTTP is the set of rules a browser and a web server use to exchange requests and responses. HTTPS uses HTTP over an encrypted connection, commonly protected with TLS. In plain terms, encryption makes the exchanged data much harder for someone observing the connection to read.
When you sign in over HTTPS, for example, the connection helps protect the information sent between your device and the site from being read in transit. Your browser also checks a digital certificate to help confirm that it is connecting to the site named in the address. These protections work together; neither is just a decorative padlock.
A secure connection has limits
HTTPS does not prove that a website is honest, accurate, or safe to use. A misleading site can still encrypt its connection, just as a legitimate site can publish incorrect information. The security cue describes the connection, not the quality of everything on the page.
Before entering sensitive information, check that the web address is the one you intended to visit, not merely that it begins with https. Watch for misspellings or an unexpected domain, and be cautious if a page asks for information unrelated to its purpose. The useful takeaway is simple: HTTPS helps protect the journey, while you still need to check the destination.