{"id":20725,"date":"2018-01-17T11:26:49","date_gmt":"2018-01-17T16:26:49","guid":{"rendered":"https:\/\/www.kaspersky.com\/blog\/?p=20725"},"modified":"2020-02-26T11:12:04","modified_gmt":"2020-02-26T16:12:04","slug":"https-does-not-mean-safe","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/https-does-not-mean-safe\/20725\/","title":{"rendered":"HTTPS doesn&#8217;t mean safe"},"content":{"rendered":"<p>Let\u2019s be honest, when most people see a little green lock with the word \u201cSecure\u201d to the left of a URL, they think the site is safe. Ditto for spotting the words \u201cthis site uses a secure connection\u201d or a URL beginning with the letters \u201chttps.\u201d More and more sites these days are switching to HTTPS. Most have no choice, in fact. So what\u2019s the problem? The more secure sites there are, the better \u2014 right?<\/p>\n<p>We\u2019re about to let you in on a little secret: Those \u201cSecure\u201d symbols don\u2019t guarantee a website is safe from all threats. A <a href=\"https:\/\/encyclopedia.kaspersky.com\/glossary\/phishing\/?utm_source=kdaily&amp;utm_medium=blog&amp;utm_campaign=termin-explanation\" target=\"_blank\" rel=\"noopener\">phishing<\/a> site, for example, can legitimately display that comforting green lock next to its https address. So, what\u2019s going on? Let\u2019s find out.<\/p>\n<p>\u00a0<\/p>\n<h2>A secure connection does not mean a secure site<\/h2>\n<p>\u00a0<\/p>\n<p>The green lock means that the site has been issued a certificate and that a pair of <a href=\"https:\/\/encyclopedia.kaspersky.com\/glossary\/cryptographic-key\/?utm_source=kdaily&amp;utm_medium=blog&amp;utm_campaign=termin-explanation\" target=\"_blank\" rel=\"noopener\">cryptographic keys<\/a> has been generated for it. Such sites encrypt information transmitted between you and the site. In this case, the page URLs begin with HTTPS, with the last \u201cS\u201d standing for \u201cSecure.\u201d<\/p>\n<p>Sure, encrypting transmitted data is a good thing. It means that information exchanged between your browser and the site is not accessible to third parties\u2014ISPs, network administrators, intruders, and so on. It lets you enter passwords or credit card details without worrying about prying eyes.<\/p>\n<p>But the problem is that the green lock and the issued certificate say nothing about the site itself. A phishing page can just as readily get a certificate and encrypt all traffic that flows between you and it.<\/p>\n<p>Put simply, all a green lock ensures is that no one <em>else<\/em> can spy on the data you enter. But your password can still be stolen by the site itself, if it\u2019s fake.<\/p>\n<p>Phishers make active use of this: <a href=\"https:\/\/info.phishlabs.com\/blog\/quarter-phishing-attacks-hosted-https-domains\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">According to Phishlabs<\/a>, a quarter of all phishing attacks today are carried out on HTTPS sites (two years ago it was less than 1 percent). Moreover, <a href=\"https:\/\/info.phishlabs.com\/blog\/quarter-phishing-attacks-hosted-https-domains\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">more than 80 percent of users believe<\/a> that the mere presence of a little green lock and the word \u201cSecure\u201d next to the URL means the site is safe, and they don\u2019t think too hard before entering their data.<\/p>\n<p>\u00a0<\/p>\n<h3>What if the lock isn\u2019t green?<\/h3>\n<p>\u00a0<\/p>\n<p>If the address bar shows no lock at all, that means the website does not use encryption, exchanging information with your browser using standard HTTP. Google Chrome has started tagging such websites as insecure. They might in fact be squeaky clean, but they don\u2019t encrypt traffic between you and the server. Most website owners don\u2019t want Google to label their websites as unsafe, so more and more are migrating to HTTPS. In any case, entering sensitive data on an HTTP site is a bad idea \u2014 anyone can spy on it.<\/p>\n<p>The second variant you might see is a lock icon crisscrossed with red lines and the HTTPS letters marked in red. That means the website has a certificate, but the certificate is unverified or out of date. That is, the connection between you and the server is encrypted, but no one can guarantee that the domain really belongs to the company indicated on the site. This is the most suspicious scenario; usually such certificates are used for test purposes only.<\/p>\n<p>Alternatively, if the certificate has expired and the owner has not gotten around to renewing it, browsers will tag the page as unsafe, but more visibly, by displaying a red lock warning. In either case, take the red as the warning it is and avoid those sites \u2014 never mind entering any personal data on them.<\/p>\n<p>\u00a0<\/p>\n<h3>How not to fall for the bait<\/h3>\n<p>\u00a0<\/p>\n<p>To sum up, the presence of a certificate and the green lock means only that the data transmitted between you and the site is encrypted, and that the certificate was issued by a trusted certificate authority. But it doesn\u2019t prevent an HTTPS site from being malicious, a fact that is most skillfully manipulated by phishing scammers.<\/p>\n<p>So always be alert, no matter how safe the site seems at first glance.<\/p>\n<ul>\n<li>Never enter logins, passwords, banking credentials, or any other personal information on the site unless you are sure of its authenticity. To do so, always check the domain name \u2014 and very carefully; the name of a fake site might differ by only one character. And ensure links are reliable before clicking.<\/li>\n<li>Always consider what a particular site is offering, whether it looks suspicious, and whether you really need to register on it.<\/li>\n<li>Make sure your devices are well protected: <a href=\"https:\/\/www.kaspersky.com\/advert\/multi-device-security?redef=1&amp;THRU&amp;reseller=gl_socmed_pro_ona_smm__onl_b2c_kasperskydaily_lnk____kismd___\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">Kaspersky Internet Security<\/a> checks URLs against an extensive database of phishing sites, and it detects scams regardless of how \u201csafe\u201d the resource looks.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Many people assume that an HTTPS connection means that the site is secure. In fact, HTTPS is increasingly being used by malicious sites, especially phishing ones.<\/p>\n","protected":false},"author":2455,"featured_media":20728,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2683],"tags":[22,682,1134,135,76,97,589,422],"class_list":{"0":"post-20725","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-threats","8":"tag-google","9":"tag-https","10":"tag-internet","11":"tag-mozilla","12":"tag-phishing","13":"tag-security-2","14":"tag-ssl","15":"tag-threats"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/https-does-not-mean-safe\/20725\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/https-does-not-mean-safe\/12221\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/https-does-not-mean-safe\/10154\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/https-does-not-mean-safe\/14424\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/https-does-not-mean-safe\/12648\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/https-does-not-mean-safe\/12331\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/https-does-not-mean-safe\/15135\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/https-does-not-mean-safe\/14923\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/https-does-not-mean-safe\/19464\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/https-does-not-mean-safe\/4636\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/https-does-not-mean-safe\/9932\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/https-does-not-mean-safe\/10049\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/https-does-not-mean-safe\/8789\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/https-does-not-mean-safe\/15669\/"},{"hreflang":"zh","url":"https:\/\/www.kaspersky.com.cn\/blog\/https-does-not-mean-safe\/9188\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/https-does-not-mean-safe\/19268\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/https-does-not-mean-safe\/19383\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/https-does-not-mean-safe\/19347\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/threats\/","name":"threats"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/20725","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/2455"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=20725"}],"version-history":[{"count":9,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/20725\/revisions"}],"predecessor-version":[{"id":33771,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/20725\/revisions\/33771"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/20728"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=20725"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=20725"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=20725"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}