What is HTTPS?
HTTP (Hypertext Transfer Protocol) is the foundation of data communication on the web. HTTPS (Hypertext Transfer Protocol Secure) is the secure version of HTTP, hence the trailing “S”. With HTTPS, information is encrypted while transmitting to and from web servers. With HTTP, no information is encrypted while in transit. Encryption is important because it is relatively simple to intercept packets of information as they shoot across the web. If encrypted information is intercepted, it cannot be read by the person or software that intercepted it.
For example, if the text:
Hello, my name is Alfred Pennyworth.
was encrypted, it would look something like this to anyone besides the intended recipient:
In other words, it would be nothing more than meaningless gibberish that does not even tell you how many characters the original information was composed of. Modern encryption algorithms are so complex that even with a tremendous amount of computing power, it could take many years (depending on numerous variables) to decipher the key required to decrypt this gibberish.
Now imagine the harmless Alfred Pennyworth statement was instead, the password to your primary financial institution. It then becomes clear why encrypting sensitive information is so important. To recap, HTTPS encrypts your data while in transit, whereas HTTP does not.
Am I Using HTTPS?
As a user of the web, there are a few fundamental bits of knowledge that go a long way in protecting your data and therefore yourself. Knowing if any given website is using HTTPS, is one of those valuable bits of knowledge that I believe everyone, technical and non-technical people alike, should be aware of.
Every modern web browser tells you if HTTPS is in use, all you need to know is what to look for. I use all five major browsers on a regular basis and, as of this writing, I think Chrome does the best job of communicating if HTTPS is in use. Let us take a look at Chrome’s address bar as our first browser example. Note the lock and green https text preceding the domain name.
Now contrast that with a website loading over unsecure HTTP, as seen below.
Mixed Content Warning
A feature that can only be found in Chrome and Opera, at the time of this writing, is what is called a mixed content warning. It means something is loading onto the HTTPS site from a HTTP source. This type of vulnerability can be exploited by those who might not have your best interests at heart. Here is what it looks like in Chrome.
The irony is this particular article is advising WordPress sites on how to avoid the very kind of mixed content errors that can be found on their blog. I suppose this is a classic case of "do as I say, not as I do".
While under the hood Firefox is handling HTTPS in the same secure manner as Chrome, it is not as obvious with its communication to you. There is nothing wrong with this, in fact, I prefer browsers that do not add bright and potentially distracting colors to their interface. However, for someone who does not know what to look for, HTTPS or the lack of it can easily be overlooked. Here is Firefox loading the first two websites we looked at earlier.
HTTPS websites have a public key certificate, which is an electronic document proving ownership of a public key. A public key is used to decrypt information sent over HTTPS. An Extended Validation (EV) certificate is a public key certificate issued after additional identity information has been verified. In the United States, it normally means an organization's physical address and legal documents have been reviewed and determined to be legitimate.
When you connect to an HTTPS website with an EV certificate, your browser adds some additional information to the address bar. I have put together a simple infographic with an example EV certificate being loaded in each of the five browsers mentioned in previous examples.
Is an EV certificate more secure?
In a word, no. There is no technical difference between standard validation, extended validation or even self-signed certificates. Encryption strength is determined by the key, not the certificate that simply proves ownership of a public key. Your driver's license proves your identity (like a certificate) but it does not determine how well you can parallel park (encryption strength).
EV certificates only provide additional browser feedback, they do not improve security. For this reason, I generally advise clients against spending extra money to buy an EV certificate and choose a standard public certificate instead. In a future article, I will explain how to do this yourself.
When is HTTPS important?
If you have stayed with me up to this point, you understand what HTTPS is and how to identify its proper use in the browser(s) of your choice. But one question remains, when should you be looking for HTTPS? A good rule of thumb would be anytime you are dealing with information that should not be available to the general public.
Anytime a password is entered into any kind of web service, HTTPS should most definitely be in effect. Those dots that appear on password fields are only hiding what you type from someone looking over your shoulder. If HTTPS is not present, there is a good chance your password will be sent across the web as plain text. Because there is no encryption, if your information is intercepted, it can easily be read.
HTTPS is also very important when connected to a public Wi-Fi network. Because these networks are usually unencrypted, it becomes trivial to listen in on passing HTTP traffic. With HTTPS, your information is protected from prying eyes.
In a follow up article titled HTTPS Everywhere I expand on these base concepts and then examine why HTTPS is important for all pages of all websites, even when there is no sensitive information to protect.
If you have any questions or comments about HTTPS, I can be reached directly on Twitter @BenjaminPatch. Until next time, take care and stay safe on the web!← InSites