To put it simply, HTTP does not encrypt any website traffic, meaning any information inputted can be leaked and/or hacked.

While HTTPS has an S at the end, which stands for "Secure". HTTPS has an SSL certificate installed, which encrypts your traffic, allowing for a secure data transfer, including any information input.

HTTP looks like so:
7192a24c4107fefbd6d865883a34003d5abc9a92?t=6104444cf118e4710f6feeb18b904633
HTTPS looks like so:
485b814030a1d1186b90b172445e615f03ad2b1a?t=caafe6beedb6193e7d2c853d77870ba1
See the difference? The first image above does not have a lock attached to it, while the second one does. Most browsers do this (Firefox on Linux is shown here) to indicate that the website is encrypted and secure.

If you see a https:// and you don't get any shady warnings, like so:
c74846d89e68aba0a05f9038b7349950e77f9d56?t=2af1dcd3ded2940f15af01a0b139a9cb
Then you're good to go and the website is secure.

However, if you do get an error like that, then that means that the website is using https:// without an SSL certificate installed, which is what makes the website flag up by the browser.

It's really as simple as that.

Thank you for taking the time to read our knowledgebase,
Getspace

Comments

Confirm Submission

Please enter the text from the image in the box provided; this helps us to prevent spam.