Hypertext Transfer Protocol Secure (HTTPS) is an extension of the Hypertext Transfer Protocol (HTTP). It is used for secure communication over a computer network, and is widely used on the Internet. In HTTPS, the communication protocol is encrypted using Transport Layer Security (TLS) or, formerly, Secure Sockets Layer (SSL). The protocol is therefore also referred to as HTTP over TLS, or HTTP over SSL.
The principal motivations for HTTPS are authentication of the accessed website, and protection of the privacy and integrity of the exchanged data while in transit. It protects against man-in-the-middle attacks, and the bidirectional encryption of communications between a client and server protects the communications against eavesdropping and tampering. In practice, this provides a reasonable assurance that one is communicating with the intended website without interference from attackers.
The authentication aspect of HTTPS requires a trusted third party to sign server-side digital certificates. This was historically an expensive operation, which meant fully authenticated HTTPS connections were usually found only on secured payment transaction services and other secured corporate information systems on the World Wide Web. In 2016, a campaign by the Electronic Frontier Foundation with the support of web browser developers led to the protocol becoming more prevalent. HTTPS is now used more often by web users than the original non-secure HTTP, primarily to protect page authenticity on all types of websites; secure accounts; and to keep user communications, identity, and web browsing private.
The Uniform Resource Identifier (URI) scheme HTTPS has identical usage syntax to the HTTP scheme. However, HTTPS signals the browser to use an added encryption layer of SSL/TLS to protect the traffic. SSL/TLS is especially suited for HTTP, since it can provide some protection even if only one side of the communication is authenticated. This is the case with HTTP transactions over the Internet, where typically only the server is authenticated (by the client examining the server's certificate).
HTTPS creates a secure channel over an insecure network. This ensures reasonable protection from eavesdroppers and man-in-the-middle attacks, provided that adequate cipher suites are used and that the server certificate is verified and trusted.
Because HTTPS piggybacks HTTP entirely on top of TLS, the entirety of the underlying HTTP protocol can be encrypted. This includes the request URL (which particular web page was requested), query parameters, headers, and cookies (which often contain identifying information about the user). However, because website addresses and port numbers are necessarily part of the underlying TCP/IP protocols, HTTPS cannot protect their disclosure. In practice this means that even on a correctly configured web server, eavesdroppers can infer the IP address and port number of the web server, and sometimes even the domain name (e.g. www.example.org, but not the rest of the URL) that a user is communicating with, along with the amount of data transferred and the duration of the communication, though not the content of the communication.
Web browsers know how to trust HTTPS websites based on certificate authorities that come pre-installed in their software. Certificate authorities are in this way being trusted by web browser creators to provide valid certificates. Therefore, a user should trust an HTTPS connection to a website if and only if all of the following are true:
- The user trusts that the browser software correctly implements HTTPS with correctly pre-installed certificate authorities.
- The user trusts the certificate authority to vouch only for legitimate websites.
- The website provides a valid certificate, which means it was signed by a trusted authority.
- The certificate correctly identifies the website (e.g., when the browser visits "https://example.com", the received certificate is properly for "example.com" and not some other entity).
- The user trusts that the protocol's encryption layer (SSL/TLS) is sufficiently secure against eavesdroppers.
HTTPS is especially important over insecure networks and networks that may be subject to tampering. Insecure networks, such as public Wi-Fi access points, allow anyone on the same local network to packet-sniff and discover sensitive information not protected by HTTPS. Additionally, some free-to-use and paid WLAN networks have been observed tampering with webpages by engaging in packet injection in order to serve their own ads on other websites. This practice can be exploited maliciously in many ways, such as by injecting malware onto webpages and stealing users' private information.
HTTPS is also important for connections over the Tor anonymity network, as malicious Tor nodes could otherwise damage or alter the contents passing through them in an insecure fashion and inject malware into the connection. This is one reason why the Electronic Frontier Foundation and the Tor project started the development of HTTPS Everywhere, which is included in the Tor Browser Bundle.
As more information is revealed about global mass surveillance and criminals stealing personal information, the use of HTTPS security on all websites is becoming increasingly important regardless of the type of Internet connection being used. Even though metadata about individual pages that a user visits might not be considered sensitive, when aggregated it can reveal a lot about the user and compromise the user's privacy.
Usage in websitesEdit
As of April 2018[update], 33.2% of Alexa top 1,000,000 websites use HTTPS as default, 57.1% of the Internet's 137,971 most popular websites have a secure implementation of HTTPS, and 70% of page loads (measured by Firefox Telemetry) use HTTPS.
Most browsers display a warning if they receive an invalid certificate. Older browsers, when connecting to a site with an invalid certificate, would present the user with a dialog box asking whether they wanted to continue. Newer browsers display a warning across the entire window. Newer browsers also prominently display the site's security information in the address bar. Extended validation certificates turn the address bar green in newer browsers. Most browsers also display a warning to the user when visiting a site that contains a mixture of encrypted and unencrypted content. Additionally, many web filters return a security warning when visiting prohibited websites.
Many web browsers, including Firefox (shown here), use the address bar to tell the user that their connection is secure, often by coloring the background.
The Electronic Frontier Foundation, opining that "In an ideal world, every web request could be defaulted to HTTPS", has provided an add-on called HTTPS Everywhere for Mozilla Firefox, Google Chrome, Chromium, and Android, that enables HTTPS by default for hundreds of frequently used websites.
The security of HTTPS is that of the underlying TLS, which typically uses long-term public and private keys to generate a short-term session key, which is then used to encrypt the data flow between the client and the server. X.509 certificates are used to authenticate the server (and sometimes the client as well). As a consequence, certificate authorities and public key certificates are necessary to verify the relation between the certificate and its owner, as well as to generate, sign, and administer the validity of certificates. While this can be more beneficial than verifying the identities via a web of trust, the 2013 mass surveillance disclosures drew attention to certificate authorities as a potential weak point allowing man-in-the-middle attacks. An important property in this context is forward secrecy, which ensures that encrypted communications recorded in the past cannot be retrieved and decrypted should long-term secret keys or passwords be compromised in the future. Not all web servers provide forward secrecy.[needs update]
For HTTPS to be effective, a site must be completely hosted over HTTPS. If some of the site's contents are loaded over HTTP (scripts or images, for example), or if only a certain page that contains sensitive information, such as a log-in page, is loaded over HTTPS while the rest of the site is loaded over plain HTTP, the user will be vulnerable to attacks and surveillance. Additionally, cookies on a site served through HTTPS must have the secure attribute enabled. On a site that has sensitive information on it, the user and the session will get exposed every time that site is accessed with HTTP instead of HTTPS.
Difference from HTTPEdit
HTTP is not encrypted and thus is vulnerable to man-in-the-middle and eavesdropping attacks, which can let attackers gain access to website accounts and sensitive information, and modify webpages to inject malware or advertisements. HTTPS is designed to withstand such attacks and is considered secure against them (with the exception of HTTPS implementations that use deprecated versions of SSL).
HTTP operates at the highest layer of the TCP/IP model—the application layer; as does the TLS security protocol (operating as a lower sublayer of the same layer), which encrypts an HTTP message prior to transmission and decrypts a message upon arrival. Strictly speaking, HTTPS is not a separate protocol, but refers to the use of ordinary HTTP over an encrypted SSL/TLS connection.
HTTPS encrypts all message contents, including the HTTP headers and the request/response data. With the exception of the possible CCA cryptographic attack described in the limitations section below, an attacker should at most be able to discover that a connection is taking place between two parties, along with their domain names and IP addresses.
To prepare a web server to accept HTTPS connections, the administrator must create a public key certificate for the web server. This certificate must be signed by a trusted certificate authority for the web browser to accept it without warning. The authority certifies that the certificate holder is the operator of the web server that presents it. Web browsers are generally distributed with a list of signing certificates of major certificate authorities so that they can verify certificates signed by them.
Let's Encrypt, launched in April 2016, provides free and automated service that delivers basic SSL/TLS certificates to websites. According to the Electronic Frontier Foundation, Let's Encrypt will make switching from HTTP to HTTPS "as easy as issuing one command, or clicking one button." The majority of web hosts and cloud providers now leverage Let's Encrypt, providing free certificates to their customers.
Use as access controlEdit
The system can also be used for client authentication in order to limit access to a web server to authorized users. To do this, the site administrator typically creates a certificate for each user, which the user loads into their browser. Normally, the certificate contains the name and e-mail address of the authorized user and is automatically checked by the server on each connection to verify the user's identity, potentially without even requiring a password.
In case of compromised secret (private) keyEdit
This section needs to be updated. The reason given is: Out of date.April 2019)(
An important property in this context is perfect forward secrecy (PFS). Possessing one of the long-term asymmetric secret keys used to establish an HTTPS session should not make it easier to derive the short-term session key to then decrypt the conversation, even at a later time. Diffie–Hellman key exchange (DHE) and Elliptic curve Diffie–Hellman key exchange (ECDHE) are in 2013 the only schemes known to have that property. In 2013, only 30% of Firefox, Opera, and Chromium Browser sessions used it, and nearly 0% of Apple's Safari and Microsoft Internet Explorer sessions. TLS 1.3, published in August 2018, dropped support for ciphers without forward secrecy. As of February 2020[update], 96.6% of web servers surveyed support some form of forward secrecy, and 52.1% will use forward secrecy with most browsers.
A certificate may be revoked before it expires, for example because the secrecy of the private key has been compromised. Newer versions of popular browsers such as Firefox, Opera, and Internet Explorer on Windows Vista implement the Online Certificate Status Protocol (OCSP) to verify that this is not the case. The browser sends the certificate's serial number to the certificate authority or its delegate via OCSP (Online Certificate Status Protocol) and the authority responds, telling the browser whether the certificate is still valid or not.The CA may also issue a CRL to tell people that these certificates are revoked.
SSL (Secure Sockets Layer) and TLS (Transport Layer Security) encryption can be configured in two modes: simple and mutual. In simple mode, authentication is only performed by the server. The mutual version requires the user to install a personal client certificate in the web browser for user authentication. In either case, the level of protection depends on the correctness of the implementation of the software and the cryptographic algorithms in use.
SSL/TLS does not prevent the indexing of the site by a web crawler, and in some cases the URI of the encrypted resource can be inferred by knowing only the intercepted request/response size. This allows an attacker to have access to the plaintext (the publicly available static content), and the encrypted text (the encrypted version of the static content), permitting a cryptographic attack.
Because TLS operates at a protocol level below that of HTTP and has no knowledge of the higher-level protocols, TLS servers can only strictly present one certificate for a particular address and port combination. In the past, this meant that it was not feasible to use name-based virtual hosting with HTTPS. A solution called Server Name Indication (SNI) exists, which sends the hostname to the server before encrypting the connection, although many old browsers do not support this extension. Support for SNI is available since Firefox 2, Opera 8, Apple Safari 2.1, Google Chrome 6, and Internet Explorer 7 on Windows Vista.
From an architectural point of view:
- An SSL/TLS connection is managed by the first front machine that initiates the TLS connection. If, for any reasons (routing, traffic optimization, etc.), this front machine is not the application server and it has to decipher data, solutions have to be found to propagate user authentication information or certificate to the application server, which needs to know who is going to be connected.
- For SSL/TLS with mutual authentication, the SSL/TLS session is managed by the first server that initiates the connection. In situations where encryption has to be propagated along chained servers, session timeOut management becomes extremely tricky to implement.
- Security is maximal with mutual SSL/TLS, but on the client-side there is no way to properly end the SSL/TLS connection and disconnect the user except by waiting for the server session to expire or by closing all related client applications.
A sophisticated type of man-in-the-middle attack called SSL stripping was presented at the 2009 Blackhat Conference. This type of attack defeats the security provided by HTTPS by changing the
https: link into an
http: link, taking advantage of the fact that few Internet users actually type "https" into their browser interface: they get to a secure site by clicking on a link, and thus are fooled into thinking that they are using HTTPS when in fact they are using HTTP. The attacker then communicates in clear with the client. This prompted the development of a countermeasure in HTTP called HTTP Strict Transport Security.
HTTPS has been shown to be vulnerable to a range of traffic analysis attacks. Traffic analysis attacks are a type of side-channel attack that relies on variations in the timing and size of traffic in order to infer properties about the encrypted traffic itself. Traffic analysis is possible because SSL/TLS encryption changes the contents of traffic, but has minimal impact on the size and timing of traffic. In May 2010, a research paper by researchers from Microsoft Research and Indiana University discovered that detailed sensitive user data can be inferred from side channels such as packet sizes. The researchers found that, despite HTTPS protection in several high-profile, top-of-the-line web applications in healthcare, taxation, investment, and web search, an eavesdropper could infer the illnesses/medications/surgeries of the user, his/her family income, and investment secrets. Although this work demonstrated the vulnerability of HTTPS to traffic analysis, the approach presented by the authors required manual analysis and focused specifically on web applications protected by HTTPS.
The fact that most modern websites, including Google, Yahoo!, and Amazon, use HTTPS causes problems for many users trying to access public Wi-Fi hot spots, because a Wi-Fi hot spot login page fails to load if the user tries to open an HTTPS resource. Several websites, such as neverssl.com and nonhttps.com, guarantee that they will always remain accessible by HTTP.
Netscape Communications created HTTPS in 1994 for its Netscape Navigator web browser. Originally, HTTPS was used with the SSL protocol. As SSL evolved into Transport Layer Security (TLS), HTTPS was formally specified by RFC 2818 in May 2000. Google announced in February 2018 that its Chrome browser would mark HTTP sites as "Not Secure" after July 2018. This move was to encourage website owners to implement HTTPS, as an effort to make the World Wide Web more secure.
- "Secure your site with HTTPS". Google Support. Google, Inc. Archived from the original on 2015-03-01. Retrieved 2018-10-20.
- "What is HTTPS?". Comodo CA Limited. Archived from the original on 2015-02-12. Retrieved 2018-10-20.
Hyper Text Transfer Protocol Secure (HTTPS) is the secure version of HTTP [...]
- Network Working Group (May 2000). "HTTP Over TLS". The Internet Engineering Task Force. Archived from the original on 2018-10-31. Retrieved 2018-10-20.
- "HTTPS Everywhere FAQ". 2016-11-08. Archived from the original on 2018-11-14. Retrieved 2018-10-20.
- "Usage Statistics of Default protocol https for Websites, July 2019". w3techs.com. Archived from the original on 2019-08-01. Retrieved 2019-07-20.
- "Encrypting the Web". Electronic Frontiers Foundation. Archived from the original on 18 November 2019. Retrieved 19 November 2019.
- "HTTP, HTTPS, SSL Over TLS". November 2019. Archived from the original on 2019-12-13. Retrieved 2019-11-19.
- The Tor Project, Inc. "What is Tor Browser?". TorProject.org. Archived from the original on 2013-07-17. Retrieved 2012-05-30.
- Konigsburg, Eitan; Pant, Rajiv; Kvochko, Elena (2014-11-13). "Embracing HTTPS". The New York Times. Archived from the original on 2019-01-08. Retrieved 2018-10-20.
- Gallagher, Kevin (2014-09-12). "Fifteen Months After the NSA Revelations, Why Aren't More News Organizations Using HTTPS?". Freedom of the Press Foundation. Archived from the original on 2018-08-10. Retrieved 2018-10-20.
- "HTTPS as a ranking signal". Google Webmaster Central Blog. Google Inc. 2014-08-06. Archived from the original on 2018-10-17. Retrieved 2018-10-20.
You can make your site secure with HTTPS (Hypertext Transfer Protocol Secure) [...]
- Grigorik, Ilya; Far, Pierre (2014-06-26). "Google I/O 2014 - HTTPS Everywhere". Google Developers. Archived from the original on 2018-11-20. Retrieved 2018-10-20.
- "How to Deploy HTTPS Correctly". 2010-11-15. Archived from the original on 2018-10-10. Retrieved 2018-10-20.
- "HTTP Strict Transport Security". Mozilla Developer Network. Archived from the original on 2018-10-19. Retrieved 2018-10-20.
- "HTTPS usage statistics on top 1M websites". StatOperator.com. Archived from the original on 2019-02-09. Retrieved 2018-10-20.
- "Qualys SSL Labs - SSL Pulse". www.ssllabs.com. 2018-04-03. Archived from the original on 2017-12-02. Retrieved 2018-10-20.
- "Let's Encrypt Stats". LetsEncrypt.org. Archived from the original on 2018-10-19. Retrieved 2018-10-20.
- Eckersley, Peter (2010-06-17). "Encrypt the Web with the HTTPS Everywhere Firefox Extension". EFF blog. Archived from the original on 2018-11-25. Retrieved 2018-10-20.
- "HTTPS Everywhere". EFF projects. 2011-10-07. Archived from the original on 2011-06-05. Retrieved 2018-10-20.
- Singel, Ryan (2010-03-24). "Law Enforcement Appliance Subverts SSL". Wired. Archived from the original on 2019-01-17. Retrieved 2018-10-20.
- Schoen, Seth (2010-03-24). "New Research Suggests That Governments May Fake SSL Certificates". EFF. Archived from the original on 2016-01-04. Retrieved 2018-10-20.
- Duncan, Robert (2013-06-25). "SSL: Intercepted today, decrypted tomorrow". Netcraft. Archived from the original on 2018-10-06. Retrieved 2018-10-20.
- Cimpanu, Catalin (2016-04-12). "Let's Encrypt Launched Today, Currently Protects 3.8 Million Domains". Softpedia News. Archived from the original on 2019-02-09. Retrieved 2018-10-20.
- Kerner, Sean Michael (2014-11-18). "Let's Encrypt Effort Aims to Improve Internet Security". eWeek.com. Quinstreet Enterprise. Retrieved 2018-10-20.
- Eckersley, Peter (2014-11-18). "Launching in 2015: A Certificate Authority to Encrypt the Entire Web". Electronic Frontier Foundation. Archived from the original on 2018-11-18. Retrieved 2018-10-20.
- Qualys SSL Labs. "SSL Pulse". Archived from the original (3 February 2019) on 15 February 2019. Retrieved 25 February 2019.
- "Opera 8 launched on FTP". Softpedia. 2005-04-19. Archived from the original on 2019-02-09. Retrieved 2018-10-20.
- Lawrence, Eric (2006-01-31). "HTTPS Security Improvements in Internet Explorer 7". MSDN. Archived from the original on 2018-10-20. Retrieved 2018-10-20.
- Myers, Michael; Ankney, Rich; Malpani, Ambarish; Galperin, Slava; Adams, Carlisle (1999-06-20). "Online Certificate Status Protocol – OCSP". Internet Engineering Task Force. Archived from the original on 2011-08-25. Retrieved 2018-10-20.
- "Manage client certificates on Chrome devices – Chrome for business and education Help". support.google.com. Archived from the original on 2019-02-09. Retrieved 2018-10-20.
- Pusep, Stanislaw (2008-07-31). "The Pirate Bay un-SSL" (PDF). Archived (PDF) from the original on 2018-06-20. Retrieved 2018-10-20.
- "SSL/TLS Strong Encryption: FAQ". apache.org. Archived from the original on 2018-10-19. Retrieved 2018-10-20.
- Lawrence, Eric (2005-10-22). "Upcoming HTTPS Improvements in Internet Explorer 7 Beta 2". Microsoft. Archived from the original on 2018-09-20. Retrieved 2018-10-20.
- "Server Name Indication (SNI)". inside aebrahim's head. 2006-02-21. Archived from the original on 2018-08-10. Retrieved 2018-10-20.
- Pierre, Julien (2001-12-19). "Browser support for TLS server name indication". Bugzilla. Mozilla Foundation. Archived from the original on 2018-10-08. Retrieved 2018-10-20.
- "sslstrip 0.9". Archived from the original on 2018-06-20. Retrieved 2018-10-20.
- Shuo Chen; Rui Wang; XiaoFeng Wang; Kehuan Zhang (2010-05-20). "Side-Channel Leaks in Web Applications: a Reality Today, a Challenge Tomorrow". Microsoft Research. IEEE Symposium on Security & Privacy 2010. Archived from the original on 2018-07-22. Retrieved 2018-10-20.
- Guaay, Matthew (2017-09-21). "How to Force a Public Wi-Fi Network Login Page to Open". Archived from the original on 2018-08-10. Retrieved 2018-10-20.
- "NeverSSL". Archived from the original on 2018-09-01. Retrieved 2018-10-20.
- "a non https website". Archived from the original on 2018-10-17. Retrieved 2018-10-20.
- Walls, Colin (2005). Embedded Software: The Works. Newnes. p. 344. ISBN 0-7506-7954-9. Archived from the original on 2019-02-09. Retrieved 2018-10-20.
- "A secure web is here to stay". Chromium Blog. Archived from the original on 2019-04-24. Retrieved 2019-04-22.
|Wikimedia Commons has media related to HTTPS.|