# HTTPS

> Mediated Wiki article. Canonical URL: https://mediated.wiki/source/HTTPS
> Markdown URL: https://mediated.wiki/source/HTTPS.md
> Source: https://en.wikipedia.org/wiki/HTTPS
> Source revision: 1355994962
> License: Creative Commons Attribution-ShareAlike 4.0 International (https://creativecommons.org/licenses/by-sa/4.0/)

HTTP extension supporting TLS encryption

HTTP Persistence Compression HTTPS QUIC Request methods OPTIONS GET HEAD POST PUT DELETE TRACE CONNECT PATCH Header fields Cookie ETag Location HTTP referer DNT X-Forwarded-For Upgrade Response status codes 301 Moved Permanently 302 Found 303 See Other 403 Forbidden 404 Not Found 451 Unavailable for Legal Reasons Security access control methods Basic access authentication Digest access authentication Security vulnerabilities HTTP header injection HTTP request smuggling HTTP response splitting HTTP parameter pollution v t e

Internet protocol suite Application layer BGP DHCP (v6) DNS FTP HTTP (HTTP/3) HTTPS IMAP IPP IRC LDAP MGCP MQTT NNTP NTP OSPF POP PTP ONC/RPC RTP RTSP RIP SIP SMTP SNMP SSH Telnet TLS/SSL XMPP more... Transport layer TCP UDP DCCP SCTP RSVP QUIC more... Internet layer IP v4 v6 ICMP (v6) NDP ECN L4S IGMP IPsec more... Link layer ARP Tunnels PPP MAC more... v t e

**Hypertext Transfer Protocol Secure** (**HTTPS**) is an extension of the [Hypertext Transfer Protocol](/source/HTTP) (HTTP). It uses [encryption](/source/Encryption) for [secure communication](/source/Secure_communications) over a [computer network](/source/Computer_network), and is widely used on the [Internet](/source/Internet).[1][2] In HTTPS, the [communication protocol](/source/Communication_protocol) is encrypted using [Transport Layer Security](/source/Transport_Layer_Security) (TLS) or, formerly, [Secure Sockets Layer](/source/Secure_Sockets_Layer) (SSL). The protocol is therefore also referred to as **HTTP over TLS**,[3] or **HTTP over SSL**.

The principal motivations for HTTPS are [authentication](/source/Authentication) of the accessed [website](/source/Website) and protection of the [privacy](/source/Information_privacy) and [integrity](/source/Data_integrity) of the exchanged data while it is in transit. It protects against [man-in-the-middle attacks](/source/Man-in-the-middle_attack), and the bidirectional [block cipher encryption](/source/Block_cipher_mode_of_operation) of communications between a [client](/source/Client_(computing)) and [server](/source/Server_(computing)) protects the communications against [eavesdropping](/source/Eavesdropping) and [tampering](/source/Tamper-evident#Tampering).[4][5] The authentication aspect of HTTPS requires a trusted third party to sign server-side [digital certificates](/source/Public_key_certificate). 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](/source/World_Wide_Web). In 2016, a campaign by the [Electronic Frontier Foundation](/source/Electronic_Frontier_Foundation) with the support of [web browser](/source/Web_browser) developers led to the protocol becoming more prevalent.[6] HTTPS has since 2018[7] been used more often by web users than non-secure HTTP, primarily to protect page authenticity on all types of websites, secure accounts, and keep user communications, identity, and web browsing private.

## Overview

Further information: [Transport Layer Security](/source/Transport_Layer_Security)

[URL](/source/URL) beginning with the HTTPS scheme and the [WWW](/source/World_Wide_Web) domain name label

The [Uniform Resource Identifier](/source/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](/source/Authentication). This is the case with HTTP transactions over the Internet, where typically only the [server](/source/Web_server) is authenticated (by the client examining the server's [certificate](/source/Public_key_certificate)).

HTTPS creates a secure channel over an insecure network. This ensures reasonable protection from [eavesdroppers](/source/Eavesdropping) and [man-in-the-middle attacks](/source/Man-in-the-middle_attack), provided that adequate [cipher suites](/source/Cipher_suite) 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's [URL](/source/URL), query parameters, headers, and cookies (which often contain identifying information about the user). However, because website addresses and [port](/source/Port_(computer_networking)) numbers are necessarily part of the underlying [TCP/IP](/source/TCP%2FIP) 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.[4]

Web browsers know how to trust HTTPS websites based on [certificate authorities](/source/Certificate_authority) 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 when all of the following are true:

- The user trusts that their device, hosting the browser and the method to get the browser itself, is not compromised (i.e. there is no [supply chain attack](/source/Supply_chain_attack)).

- 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 (i.e. the certificate authority is not compromised and there is no mis-issuance of certificates).

- 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](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](/source/Wi-Fi) access points, allow anyone on the same local network to [packet-sniff](/source/Packet_analyzer) and discover sensitive information not protected by HTTPS. Additionally, some free-to-use and paid [WLAN](/source/Wireless_LAN) networks have been observed tampering with webpages by engaging in [packet injection](/source/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](/source/Malware) onto webpages and stealing users' private information.[8]

HTTPS is also important for connections over the [Tor network](/source/Tor_(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](/source/Electronic_Frontier_Foundation) and [the Tor Project](/source/The_Tor_Project) started the development of [HTTPS Everywhere](/source/HTTPS_Everywhere),[4] which is included in Tor Browser.[9]

As more information is revealed about global [mass surveillance](/source/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.[10][11] Even though [metadata](/source/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.[12][13][14]

Deploying HTTPS also allows the use of [HTTP/2](/source/HTTP%2F2) and [HTTP/3](/source/HTTP%2F3) (and their predecessors [SPDY](/source/SPDY) and [QUIC](/source/QUIC)), which are new HTTP versions designed to reduce page load times, size, and latency.

It is recommended to use [HTTP Strict Transport Security](/source/HTTP_Strict_Transport_Security) (HSTS) with HTTPS to protect users from man-in-the-middle attacks, especially [SSL stripping](/source/Moxie_Marlinspike#SSL_stripping).[14][15]

HTTPS should not be confused with the seldom-used [Secure HTTP](/source/Secure_Hypertext_Transfer_Protocol) (S-HTTP) specified in RFC 2660.

### Usage in websites

As of April 2018[\[update\]](https://en.wikipedia.org/w/index.php?title=HTTPS&action=edit), 33.2% of Alexa top 1,000,000 websites use HTTPS as default[16] and 70% of page loads (measured by Firefox Telemetry) use HTTPS.[17] As of June 2025[\[update\]](https://en.wikipedia.org/w/index.php?title=HTTPS&action=edit), 71.2% of the Internet's 150,000 most popular websites have a secure implementation of HTTPS (up from 58.4% in December 2022),[18] However, despite [TLS 1.3](/source/TLS_1.3)'s release in 2018, adoption has been slow, with many still remaining on the older TLS 1.2 protocol.[19]

### Browser integration

Most [browsers](/source/Web_browser) 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](/source/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](/source/Address_bar). [Extended validation certificates](/source/Extended_validation_certificate) show the legal entity on the certificate information. 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](/source/Content-control_software) return a security warning when visiting prohibited websites.

Comparison between different kinds of [SSL/TLS](/source/Transport_Layer_Security) certificates
(Using [Firefox](/source/Firefox) as an example)

		- Many web browsers, including Firefox (shown here), use the [address bar](/source/Address_bar) to tell the user that their connection is secure, an [Extended Validation Certificate](/source/Extended_Validation_Certificate) should identify the legal entity for the certificate.

		- When accessing a site only with a common certificate, on the address bar of [Firefox](/source/Firefox) and other [browsers](/source/Web_browser), a "lock" sign appears.

		- Most web browsers alert the user when visiting sites that have invalid security certificates.

The [Electronic Frontier Foundation](/source/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](/source/Mozilla_Firefox), [Google Chrome](/source/Google_Chrome), [Chromium](/source/Chromium_(web_browser)), and [Android](/source/Android_(operating_system)), which enables HTTPS by default for hundreds of frequently used websites.[20][21]

Forcing a web browser to load only HTTPS content has been supported in Firefox starting in version 83.[22] Starting in version 94, Google Chrome is able to "always use secure connections" if toggled in the browser's settings.[23][24] Prior to version 117, Google Chrome displayed a lock icon in the [address bar](/source/Address_bar), which has since been replaced by a "tune" icon.[25] Many users believe that a lock icon implies a website is safe, ignoring other security concerns.[26]

## Security

Main article: [Transport Layer Security § Security](/source/Transport_Layer_Security#Security)

The security of HTTPS is that of the underlying TLS, which typically uses long-term [public](/source/Public-key_cryptography) and private keys to generate a short-term [session key](/source/Session_key), which is then used to encrypt the data flow between the client and the server. [X.509](/source/X.509) certificates are used to authenticate the server (and sometimes the client as well). As a consequence, [certificate authorities](/source/Certificate_authority) and [public key certificates](/source/Public_key_certificate) 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](/source/Web_of_trust), the [2013 mass surveillance disclosures](/source/2013_mass_surveillance_disclosures) drew attention to certificate authorities as a potential weak point allowing [man-in-the-middle attacks](/source/Man-in-the-middle_attack).[27][28] An important property in this context is [forward secrecy](/source/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.[29][*[needs update](https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Dates_and_numbers#Chronological_items)*]

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](/source/HTTP_cookie) on a site served through HTTPS must have the [secure attribute](/source/Secure_cookie) 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.[14]

## Technical

### Difference from HTTP

HTTPS [URLs](/source/URL) begin with "https://" and use [port](/source/List_of_TCP_and_UDP_port_numbers) 443 by default, whereas [HTTP](/source/HTTP) URLs begin with "http://" and use port 80 by default.

HTTP is not encrypted and thus is vulnerable to [man-in-the-middle](/source/Man-in-the-middle) and [eavesdropping attacks](/source/Eavesdropping_attack), which can let attackers gain access to website accounts and sensitive information, and modify webpages to inject [malware](/source/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).

### Network layers

HTTP operates at the highest layer of the [TCP/IP model](/source/TCP%2FIP_model)—the [application layer](/source/Application_layer); as does the [TLS](/source/Transport_Layer_Security) 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](/source/HTTP) over an [encrypted](/source/Encryption) SSL/TLS connection.

HTTPS encrypts all message contents, including the HTTP headers and the request/response data. With the exception of the possible [CCA](/source/Chosen-ciphertext_attack) cryptographic attack described in the [limitations](#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.

### Server setup

To prepare a web server to accept HTTPS connections, the administrator must create a [public key certificate](/source/Public_key_certificate) for the web server. This certificate must be signed by a trusted [certificate authority](/source/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](/source/Root_certificate) so that they can verify certificates signed by them.

#### Acquiring certificates

A number of commercial [certificate authorities](/source/Certificate_authority) exist, offering paid-for SSL/TLS certificates of a number of types, including [Extended Validation Certificates](/source/Extended_Validation_Certificate).

[Let's Encrypt](/source/Let's_Encrypt), launched in April 2016,[30] provides free and automated service that delivers basic SSL/TLS certificates to websites.[31] According to the [Electronic Frontier Foundation](/source/Electronic_Frontier_Foundation), Let's Encrypt will make switching from HTTP to HTTPS "as easy as issuing one command, or clicking one button."[32] The majority of web hosts and cloud providers now leverage Let's Encrypt, providing free certificates to their customers.

#### Use as access control

The system can also be used for client [authentication](/source/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) key

An important property in this context is [perfect forward secrecy](/source/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](/source/Diffie%E2%80%93Hellman_key_exchange) (DHE) and [Elliptic-curve Diffie–Hellman](/source/Elliptic-curve_Diffie%E2%80%93Hellman) 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](/source/Safari_(web_browser)) and [Microsoft Internet Explorer](/source/Internet_Explorer) sessions.[29] TLS 1.3, published in August 2018, dropped support for ciphers without forward secrecy. As of February 2019[\[update\]](https://en.wikipedia.org/w/index.php?title=HTTPS&action=edit), 96.6% of web servers surveyed support some form of forward secrecy, and 52.1% will use forward secrecy with most browsers.[33] As of July 2023[\[update\]](https://en.wikipedia.org/w/index.php?title=HTTPS&action=edit), 99.6% of web servers surveyed support some form of forward secrecy, and 75.2% will use forward secrecy with most browsers.[34]

#### Certificate revocation

Main article: [Certificate revocation](/source/Certificate_revocation)

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](/source/Firefox),[35] [Opera](/source/Opera_(web_browser)),[36] and [Internet Explorer](/source/Internet_Explorer) on [Windows Vista](/source/Windows_Vista)[37] implement the [Online Certificate Status Protocol](/source/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.[38] The CA may also issue a [CRL](/source/Certificate_revocation_list) to tell people that these certificates are revoked. CRLs are no longer required by the CA/Browser forum,[39][*[needs update](https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Dates_and_numbers#Chronological_items)*] nevertheless, they are still widely used by the CAs. Most revocation statuses on the Internet disappear soon after the expiration of the certificates.[40]

### Limitations

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](/source/Client_certificate) in the web browser for user authentication.[41] In either case, the level of protection depends on the correctness of the [implementation](/source/Implementation) of the software and the [cryptographic algorithms](/source/Cipher) in use.[42]

SSL/TLS does not prevent the indexing of the site by a [web crawler](/source/Web_crawler), and in some cases the [URI](/source/Uniform_resource_identifier) of the encrypted resource can be inferred by knowing only the intercepted request/response size.[43] This allows an attacker to have access to the [plaintext](/source/Plaintext) (the publicly available static content), and the [encrypted text](/source/Ciphertext) (the encrypted version of the static content), permitting a [cryptographic attack](/source/Chosen-ciphertext_attack).[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*]

Because [TLS](/source/Transport_Layer_Security) 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.[44] In the past, this meant that it was not feasible to use [name-based virtual hosting](/source/Virtual_hosting#Name-based) with HTTPS. A solution called [Server Name Indication](/source/Server_Name_Indication) (SNI) exists, which sends the hostname to the server before encrypting the connection, although older browsers do not support this extension. Support for SNI is available since [Firefox](/source/Firefox) 2, [Opera](/source/Opera_(web_browser)) 8, [Apple Safari](/source/Safari_(web_browser)) 2.1, [Google Chrome](/source/Google_Chrome) 6, and [Internet Explorer 7](/source/Internet_Explorer_7) on [Windows Vista](/source/Windows_Vista).[45][46][47]

A sophisticated type of [man-in-the-middle attack](/source/Man-in-the-middle_attack) called SSL stripping was presented at the 2009 [Blackhat Conference](/source/Black_Hat_Briefings). 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.[48] This prompted the development of a countermeasure in HTTP called [HTTP Strict Transport Security](/source/HTTP_Strict_Transport_Security).[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*]

HTTPS has been shown to be vulnerable to a range of [traffic analysis](/source/Traffic_analysis) attacks. Traffic analysis attacks are a type of [side-channel attack](/source/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](/source/Microsoft_Research) and [Indiana University](/source/Indiana_University_Bloomington) 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.[49]

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 [captive portal](/source/Captive_portal) Wi-Fi hot spot login page fails to load if the user tries to open an HTTPS resource.[50] Several websites, such as [NoSSL.sh](http://nossl.sh), guarantee that they will always remain accessible by HTTP[51].

## History

Main article: [Transport Layer Security § History and development](/source/Transport_Layer_Security#History_and_development)

[Netscape Communications](/source/Netscape_Communications) created HTTPS in 1994 for its [Netscape Navigator](/source/Netscape_Navigator) web browser.[52] Originally, HTTPS was used with the [SSL](/source/Secure_Sockets_Layer) protocol.[53] The original SSL protocol was developed by [Taher Elgamal](/source/Taher_Elgamal), chief scientist at [Netscape Communications](/source/Netscape).[54][55][56] As SSL evolved into [Transport Layer Security](/source/Transport_Layer_Security) (TLS), HTTPS was formally specified by RFC 2818[57] in May 2000. Google announced in February 2018 that its Chrome browser would mark HTTP sites as "Not Secure" after July 2018.[53] This move was to encourage website owners to implement HTTPS, as an effort to make the [World Wide Web](/source/World_Wide_Web) more secure.

## See also

- [Transport Layer Security](/source/Transport_Layer_Security)

- [Bullrun (decryption program)](/source/Bullrun_(decryption_program)) – a secret anti-encryption program run by the US [National Security Agency](/source/National_Security_Agency)

- [Computer security](/source/Computer_security)

- [HSTS](/source/HTTP_Strict_Transport_Security)

- [Opportunistic encryption](/source/Opportunistic_encryption)

- [Stunnel](/source/Stunnel)

## References

1. **[^](#cite_ref-1)** ["Secure your site with HTTPS"](https://support.google.com/webmasters/answer/6073543?hl=en). *Google Support*. Google Inc. [Archived](https://web.archive.org/web/20150301023624/https://support.google.com/webmasters/answer/6073543?hl=en) from the original on 2015-03-01. Retrieved 2018-10-20.

1. **[^](#cite_ref-2)** ["What is HTTPS?"](https://web.archive.org/web/20150212105201/https://www.instantssl.com/ssl-certificate-products/https.html). [Comodo CA Limited](/source/Comodo_Group). Archived from the original on 2015-02-12. Retrieved 2018-10-20. Hyper Text Transfer Protocol Secure (HTTPS) is the secure version of HTTP [...]

1. **[^](#cite_ref-3)** ["https URI Scheme"](https://datatracker.ietf.org/doc/html/rfc9110#section-4.2.2). [*HTTP Semantics*](https://www.rfc-editor.org/rfc/rfc9110). [IETF](/source/Internet_Engineering_Task_Force). June 2022. sec. 4.2.2. [doi](/source/Doi_(identifier)):[10.17487/RFC9110](https://doi.org/10.17487%2FRFC9110). [RFC](/source/Request_for_Comments) [9110](https://datatracker.ietf.org/doc/html/rfc9110).

1. ^ [***a***](#cite_ref-httpse_4-0) [***b***](#cite_ref-httpse_4-1) [***c***](#cite_ref-httpse_4-2) ["HTTPS Everywhere FAQ"](https://www.eff.org/https-everywhere/faq). 2016-11-08. [Archived](https://web.archive.org/web/20181114011956/https://www.eff.org/https-everywhere/faq/) from the original on 2018-11-14. Retrieved 2018-10-20.

1. **[^](#cite_ref-5)** ["Usage Statistics of Default protocol https for Websites, July 2019"](https://w3techs.com/technologies/details/ce-httpsdefault/all/all). *w3techs.com*. [Archived](https://web.archive.org/web/20190801134536/https://w3techs.com/technologies/details/ce-httpsdefault/all/all) from the original on 2019-08-01. Retrieved 2019-07-20.

1. **[^](#cite_ref-6)** ["Encrypting the Web"](https://www.eff.org/encrypt-the-web). *Electronic Frontier Foundation*. [Archived](https://web.archive.org/web/20191118094200/https://www.eff.org/encrypt-the-web) from the original on 2019-11-18. Retrieved 2019-11-19.

1. **[^](#cite_ref-7)** ["Majority of the world's top million websites now use HTTPS"](https://www.welivesecurity.com/2018/09/03/majority-worlds-top-websites-https/). *welivesecurity.com*. Retrieved 2025-05-22.

1. **[^](#cite_ref-8)** ["Hotel Wifi JavaScript Injection"](https://justinsomnia.org/2012/04/hotel-wifi-javascript-injection/). *JustInsomnia*. 2012-04-03. [Archived](https://web.archive.org/web/20181118154608/https://justinsomnia.org/2012/04/hotel-wifi-javascript-injection/) from the original on 2018-11-18. Retrieved 2018-10-20.

1. **[^](#cite_ref-9)** The Tor Project, Inc. ["What is Tor Browser?"](https://www.torproject.org/projects/torbrowser.html.en). *TorProject.org*. Retrieved 2012-05-30.{{[cite web](https://en.wikipedia.org/wiki/Template:Cite_web)}}: CS1 maint: deprecated archival service ([link](https://en.wikipedia.org/wiki/Category:CS1_maint:_deprecated_archival_service))

1. **[^](#cite_ref-10)** Konigsburg, Eitan; Pant, Rajiv; Kvochko, Elena (2014-11-13). ["Embracing HTTPS"](https://open.blogs.nytimes.com/2014/11/13/embracing-https/). *The New York Times*. [Archived](https://web.archive.org/web/20190108190000/https://open.blogs.nytimes.com/2014/11/13/embracing-https/) from the original on 2019-01-08. Retrieved 2018-10-20.

1. **[^](#cite_ref-11)** Gallagher, Kevin (2014-09-12). ["Fifteen Months After the NSA Revelations, Why Aren't More News Organizations Using HTTPS?"](https://freedom.press/news-advocacy/fifteen-months-after-the-nsa-revelations-why-arenat-more-news-organizations-using-https/). Freedom of the Press Foundation. [Archived](https://web.archive.org/web/20180810204919/https://freedom.press/news-advocacy/fifteen-months-after-the-nsa-revelations-why-arenat-more-news-organizations-using-https/) from the original on 2018-08-10. Retrieved 2018-10-20.

1. **[^](#cite_ref-12)** ["HTTPS as a ranking signal"](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html). *Google Webmaster Central Blog*. Google Inc. 2014-08-06. [Archived](https://web.archive.org/web/20181017052432/https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) from the original on 2018-10-17. Retrieved 2018-10-20. You can make your site secure with HTTPS (Hypertext Transfer Protocol Secure) [...]

1. **[^](#cite_ref-13)** Grigorik, Ilya; Far, Pierre (2014-06-26). ["Google I/O 2014 - HTTPS Everywhere"](https://www.youtube.com/watch?v=cBhZ6S0PFCY). Google Developers. [Archived](https://web.archive.org/web/20181120144918/https://www.youtube.com/watch?v=cBhZ6S0PFCY) from the original on 2018-11-20. Retrieved 2018-10-20.

1. ^ [***a***](#cite_ref-deployhttpscorrectly_14-0) [***b***](#cite_ref-deployhttpscorrectly_14-1) [***c***](#cite_ref-deployhttpscorrectly_14-2) ["How to Deploy HTTPS Correctly"](https://www.eff.org/https-everywhere/deploying-https). 2010-11-15. [Archived](https://web.archive.org/web/20181010233702/https://www.eff.org/https-everywhere/deploying-https) from the original on 2018-10-10. Retrieved 2018-10-20.

1. **[^](#cite_ref-15)** ["HTTP Strict Transport Security"](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security). *Mozilla Developer Network*. [Archived](https://web.archive.org/web/20181019171534/https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security) from the original on 2018-10-19. Retrieved 2018-10-20.

1. **[^](#cite_ref-16)** ["HTTPS usage statistics on top 1M websites"](https://statoperator.com/research/https-usage-statistics-on-top-websites/). *StatOperator.com*. [Archived](https://web.archive.org/web/20190209055130/https://statoperator.com/research/https-usage-statistics-on-top-websites/) from the original on 2019-02-09. Retrieved 2018-10-20.

1. **[^](#cite_ref-17)** ["Let's Encrypt Stats"](https://letsencrypt.org/stats/). *LetsEncrypt.org*. [Archived](https://web.archive.org/web/20181019221028/https://letsencrypt.org/stats/) from the original on 2018-10-19. Retrieved 2018-10-20.

1. **[^](#cite_ref-18)** ["Qualys SSL Labs - SSL Pulse"](https://www.ssllabs.com/ssl-pulse/). *www.ssllabs.com*. 2025-06-02. [Archived](https://web.archive.org/web/20221207004823/https://www.ssllabs.com/ssl-pulse/) from the original on 2022-12-07. Retrieved 2022-12-07..

1. **[^](#cite_ref-19)** ["TLS 1.3: Slow adoption of stronger web encryption is empowering the bad guys"](https://www.helpnetsecurity.com/2020/04/06/tls-1-3-adoption/). *Help Net Security*. 2020-04-06. [Archived](https://web.archive.org/web/20220524002257/https://www.helpnetsecurity.com/2020/04/06/tls-1-3-adoption/) from the original on 2022-05-24. Retrieved 2022-05-23.

1. **[^](#cite_ref-20)** Eckersley, Peter (2010-06-17). ["Encrypt the Web with the HTTPS Everywhere Firefox Extension"](https://www.eff.org/deeplinks/2010/06/encrypt-web-https-everywhere-firefox-extension). *EFF blog*. [Archived](https://web.archive.org/web/20181125102636/https://www.eff.org/deeplinks/2010/06/encrypt-web-https-everywhere-firefox-extension) from the original on 2018-11-25. Retrieved 2018-10-20.

1. **[^](#cite_ref-21)** ["HTTPS Everywhere"](https://www.eff.org/https-everywhere). *EFF projects*. 2011-10-07. [Archived](https://web.archive.org/web/20110605022218/https://www.eff.org/https-everywhere) from the original on 2011-06-05. Retrieved 2018-10-20.

1. **[^](#cite_ref-22)** ["HTTPS-Only Mode in Firefox"](https://support.mozilla.org/en-US/kb/https-only-prefs). [Archived](https://web.archive.org/web/20211112222245/https://support.mozilla.org/en-US/kb/https-only-prefs) from the original on 2021-11-12. Retrieved 2021-11-12.

1. **[^](#cite_ref-23)** ["Manage Chrome safety and security - Android - Google Chrome Help"](https://support.google.com/chrome/answer/10468685?hl=en&co=GENIE.Platform=Android). *support.google.com*. [Archived](https://web.archive.org/web/20220307190622/https://support.google.com/chrome/answer/10468685?hl=en&co=GENIE.Platform=Android) from the original on 2022-03-07. Retrieved 2022-03-07.

1. **[^](#cite_ref-24)** Eswarlu, Venkat (2021-07-19). ["Hands on Chrome's HTTPS-First Mode"](https://techdows.com/2021/07/hands-on-chromes-https-first-mode.html). *Techdows*. [Archived](https://web.archive.org/web/20220307190617/https://techdows.com/2021/07/hands-on-chromes-https-first-mode.html) from the original on 2022-03-07. Retrieved 2022-03-07.

1. **[^](#cite_ref-25)** Crane, Casey. ["Google to Replace the Padlock Icon in Chrome Version 117"](https://www.thesslstore.com/blog/google-to-replace-the-padlock-icon-in-chrome-version-117/#:%7E:text=But%20that's%20about%20to%20change,to%20have%20HTTPS%20by%20default.). *Hashed Out*. The SSL Store. Retrieved 2026-05-05.

1. **[^](#cite_ref-26)** Ruoti, Scott; Monson, Tyler; Wu, Jusin; Zappala, Daniel; Seamons, Kent (2017-07-12). ["Weighing context and trade-offs: how suburban adults selected their online security posture"](https://dl.acm.org/doi/10.5555/3235924.3235942). *Thirteenth Symposium on Usable Privacy and Security (SOUPS 2017)*: 211–228. Retrieved 2026-05-05.

1. **[^](#cite_ref-27)** Singel, Ryan (2010-03-24). ["Law Enforcement Appliance Subverts SSL"](https://www.wired.com/2010/03/packet-forensics/). *Wired*. [Archived](https://web.archive.org/web/20190117142906/https://www.wired.com/2010/03/packet-forensics/) from the original on 2019-01-17. Retrieved 2018-10-20.

1. **[^](#cite_ref-28)** Schoen, Seth (2010-03-24). ["New Research Suggests That Governments May Fake SSL Certificates"](https://www.eff.org/deeplinks/2010/03/researchers-reveal-likelihood-governments-fake-ssl). *EFF*. [Archived](https://web.archive.org/web/20160104234608/https://www.eff.org/deeplinks/2010/03/researchers-reveal-likelihood-governments-fake-ssl) from the original on 2016-01-04. Retrieved 2018-10-20.

1. ^ [***a***](#cite_ref-ecdhe_29-0) [***b***](#cite_ref-ecdhe_29-1) Duncan, Robert (2013-06-25). ["SSL: Intercepted today, decrypted tomorrow"](https://news.netcraft.com/archives/2013/06/25/ssl-intercepted-today-decrypted-tomorrow.html). *Netcraft*. [Archived](https://web.archive.org/web/20181006021916/https://news.netcraft.com/archives/2013/06/25/ssl-intercepted-today-decrypted-tomorrow.html) from the original on 2018-10-06. Retrieved 2018-10-20.

1. **[^](#cite_ref-softpedia-launch_30-0)** Cimpanu, Catalin (2016-04-12). ["Let's Encrypt Launched Today, Currently Protects 3.8 Million Domains"](https://news.softpedia.com/news/let-s-encrypt-launched-today-currently-protects-3-8-million-domains-502857.shtml). Softpedia News. [Archived](https://web.archive.org/web/20190209055129/https://news.softpedia.com/news/let-s-encrypt-launched-today-currently-protects-3-8-million-domains-502857.shtml) from the original on 2019-02-09. Retrieved 2018-10-20.

1. **[^](#cite_ref-31)** Kerner, Sean Michael (2014-11-18). ["Let's Encrypt Effort Aims to Improve Internet Security"](http://www.eweek.com/security/let-s-encrypt-effort-aims-to-improve-internet-security). *eWeek.com*. Quinstreet Enterprise. [Archived](https://web.archive.org/web/20230402154948/https://www.eweek.com/security/let-s-encrypt-effort-aims-to-improve-internet-security/) from the original on 2023-04-02. Retrieved 2018-10-20.

1. **[^](#cite_ref-32)** Eckersley, Peter (2014-11-18). ["Launching in 2015: A Certificate Authority to Encrypt the Entire Web"](https://www.eff.org/deeplinks/2014/11/certificate-authority-encrypt-entire-web). [Electronic Frontier Foundation](/source/Electronic_Frontier_Foundation). [Archived](https://web.archive.org/web/20181118160126/https://www.eff.org/deeplinks/2014/11/certificate-authority-encrypt-entire-web) from the original on 2018-11-18. Retrieved 2018-10-20.

1. **[^](#cite_ref-33)** [Qualys SSL Labs](/source/Qualys). ["SSL Pulse"](https://web.archive.org/web/20190215213454/https://www.ssllabs.com/ssl-pulse/). Archived from [the original](https://www.ssllabs.com/ssl-pulse/) (3 February 2019) on 2019-02-15. Retrieved 2019-02-25.

1. **[^](#cite_ref-34)** ["Qualys SSL Labs - SSL Pulse"](https://www.ssllabs.com/ssl-pulse/). *www.ssllabs.com*. Retrieved 2023-09-04.

1. **[^](#cite_ref-35)** ["Mozilla Firefox Privacy Policy"](https://www.mozilla.org/en-US/privacy/). [Mozilla Foundation](/source/Mozilla_Foundation). 2009-04-27. [Archived](https://web.archive.org/web/20181018063732/https://www.mozilla.org/en-US/privacy/) from the original on 2018-10-18. Retrieved 2018-10-20.

1. **[^](#cite_ref-36)** ["Opera 8 launched on FTP"](https://news.softpedia.com/news/Opera-8-launched-on-FTP-1330.shtml). [Softpedia](/source/Softpedia). 2005-04-19. [Archived](https://web.archive.org/web/20190209055128/https://news.softpedia.com/news/Opera-8-launched-on-FTP-1330.shtml) from the original on 2019-02-09. Retrieved 2018-10-20.

1. **[^](#cite_ref-37)** Lawrence, Eric (2006-01-31). ["HTTPS Security Improvements in Internet Explorer 7"](https://docs.microsoft.com/en-us/previous-versions/aa980989(v=msdn.10)). *[Microsoft Docs](/source/Microsoft_Docs)*. [Archived](https://web.archive.org/web/20211024181937/https://docs.microsoft.com/en-us/previous-versions/aa980989(v=msdn.10)) from the original on 2021-10-24. Retrieved 2021-10-24.

1. **[^](#cite_ref-38)** Myers, Michael; Ankney, Rich; Malpani, Ambarish; Galperin, Slava; Adams, Carlisle (1999-06-20). ["Online Certificate Status Protocol – OCSP"](https://tools.ietf.org/html/rfc2560). [Internet Engineering Task Force](/source/Internet_Engineering_Task_Force). [doi](/source/Doi_(identifier)):[10.17487/RFC2560](https://doi.org/10.17487%2FRFC2560). [Archived](https://web.archive.org/web/20110825095059/http://tools.ietf.org/html/rfc2560) from the original on 2011-08-25. Retrieved 2018-10-20.

1. **[^](#cite_ref-39)** ["Baseline Requirements"](https://cabforum.org/baseline-requirements-documents/). CAB Forum. 2013-09-04. [Archived](https://web.archive.org/web/20141020234802/https://cabforum.org/baseline-requirements-documents/) from the original on 2014-10-20. Retrieved 2021-11-01.

1. **[^](#cite_ref-RS_1_40-0)** Korzhitskii, N.; Carlsson, N. (2021-03-30). "Revocation Statuses on the Internet". *Passive and Active Measurement*. Lecture Notes in Computer Science. Vol. 12671. pp. 175–191. [arXiv](/source/ArXiv_(identifier)):[2102.04288](https://arxiv.org/abs/2102.04288). [doi](/source/Doi_(identifier)):[10.1007/978-3-030-72582-2_11](https://doi.org/10.1007%2F978-3-030-72582-2_11). [ISBN](/source/ISBN_(identifier)) [978-3-030-72581-5](https://en.wikipedia.org/wiki/Special:BookSources/978-3-030-72581-5).

1. **[^](#cite_ref-41)** ["Manage client certificates on Chrome devices – Chrome for business and education Help"](https://support.google.com/chrome/a/answer/6080885?hl=en). *support.google.com*. [Archived](https://web.archive.org/web/20190209055127/https://support.google.com/chrome/a/answer/6080885?hl=en) from the original on 2019-02-09. Retrieved 2018-10-20.

1. **[^](#cite_ref-42)** ["Practical Cryptography"](https://www.schneier.com/books/practical-cryptography/). *Schneier on Security*. [ISBN](/source/ISBN_(identifier)) [0471223573](https://en.wikipedia.org/wiki/Special:BookSources/0471223573). Retrieved 2026-04-14.

1. **[^](#cite_ref-43)** Pusep, Stanislaw (2008-07-31). ["The Pirate Bay un-SSL"](https://www.exploit-db.com/docs/english/13026-the-pirate-bay-un-ssl.pdf) (PDF). [Archived](https://web.archive.org/web/20180620001518/https://www.exploit-db.com/docs/english/13026-the-pirate-bay-un-ssl.pdf) (PDF) from the original on 2018-06-20. Retrieved 2018-10-20.

1. **[^](#cite_ref-44)** ["SSL/TLS Strong Encryption: FAQ"](https://httpd.apache.org/docs/2.0/ssl/ssl_faq.html#vhosts). *apache.org*. [Archived](https://web.archive.org/web/20181019105423/http://httpd.apache.org/docs/2.0/ssl/ssl_faq.html#vhosts) from the original on 2018-10-19. Retrieved 2018-10-20.

1. **[^](#cite_ref-45)** Lawrence, Eric (2005-10-22). ["Upcoming HTTPS Improvements in Internet Explorer 7 Beta 2"](https://blogs.msdn.microsoft.com/ie/2005/10/22/upcoming-https-improvements-in-internet-explorer-7-beta-2/). [Microsoft](/source/Microsoft). [Archived](https://web.archive.org/web/20180920113838/https://blogs.msdn.microsoft.com/ie/2005/10/22/upcoming-https-improvements-in-internet-explorer-7-beta-2/) from the original on 2018-09-20. Retrieved 2018-10-20.

1. **[^](#cite_ref-46)** ["Server Name Indication (SNI)"](https://blog.ebrahim.org/2006/02/21/server-name-indication-sni/). *inside aebrahim's head*. 2006-02-21. [Archived](https://web.archive.org/web/20180810173628/https://blog.ebrahim.org/2006/02/21/server-name-indication-sni/) from the original on 2018-08-10. Retrieved 2018-10-20.

1. **[^](#cite_ref-47)** Pierre, Julien (2001-12-19). ["Browser support for TLS server name indication"](https://bugzilla.mozilla.org/show_bug.cgi?id=116169). *Bugzilla*. Mozilla Foundation. [Archived](https://web.archive.org/web/20181008070112/https://bugzilla.mozilla.org/show_bug.cgi?id=116169) from the original on 2018-10-08. Retrieved 2018-10-20.

1. **[^](#cite_ref-48)** ["sslstrip 0.9"](https://moxie.org/software/sslstrip/index.html). [Archived](https://web.archive.org/web/20180620042059/https://moxie.org/software/sslstrip/index.html) from the original on 2018-06-20. Retrieved 2018-10-20.

1. **[^](#cite_ref-49)** Shuo Chen; Rui Wang; XiaoFeng Wang; Kehuan Zhang (2010-05-20). ["Side-Channel Leaks in Web Applications: a Reality Today, a Challenge Tomorrow"](https://www.microsoft.com/en-us/research/publication/side-channel-leaks-in-web-applications-a-reality-today-a-challenge-tomorrow/). *Microsoft Research*. [IEEE](/source/Institute_of_Electrical_and_Electronics_Engineers) Symposium on Security & Privacy 2010. [Archived](https://web.archive.org/web/20180722120329/https://www.microsoft.com/en-us/research/publication/side-channel-leaks-in-web-applications-a-reality-today-a-challenge-tomorrow/) from the original on 2018-07-22. Retrieved 2018-10-20.

1. **[^](#cite_ref-50)** Guaay, Matthew (2017-09-21). ["How to Force a Public Wi-Fi Network Login Page to Open"](https://zapier.com/blog/open-wifi-login-page/). [Archived](https://web.archive.org/web/20180810143254/https://zapier.com/blog/open-wifi-login-page/) from the original on 2018-08-10. Retrieved 2018-10-20.

1. **[^](#cite_ref-51)** ["nossl.sh HTTP-only disclaimer"](http://nossl.sh/disclaimer). *nossl.sh*. Retrieved 2025-12-18.

1. **[^](#cite_ref-52)** Walls, Colin (2005). [*Embedded Software: The Works*](https://books.google.com/books?id=FLvsis4_QhEC&pg=PA344). Newnes. p. 344. [ISBN](/source/ISBN_(identifier)) [0-7506-7954-9](https://en.wikipedia.org/wiki/Special:BookSources/0-7506-7954-9). [Archived](https://web.archive.org/web/20190209055124/https://www.google.com/books/edition/_/FLvsis4_QhEC?hl=en&gbpv=1&pg=PA344) from the original on 2019-02-09. Retrieved 2018-10-20.

1. ^ [***a***](#cite_ref-:0_53-0) [***b***](#cite_ref-:0_53-1) ["A secure web is here to stay"](https://blog.chromium.org/2018/02/a-secure-web-is-here-to-stay.html). *Chromium Blog*. [Archived](https://web.archive.org/web/20190424215132/https://blog.chromium.org/2018/02/a-secure-web-is-here-to-stay.html) from the original on 2019-04-24. Retrieved 2019-04-22.

1. **[^](#cite_ref-Messmer_54-0)** Messmer, Ellen. ["Father of SSL, Dr. Taher Elgamal, Finds Fast-Moving IT Projects in the Middle East"](https://web.archive.org/web/20140531105537/http://www.networkworld.com/news/2012/120412-elgamal-264739.html). *Network World*. Archived from [the original](http://www.networkworld.com/news/2012/120412-elgamal-264739.html) on 2014-05-31. Retrieved 2014-05-30.

1. **[^](#cite_ref-Greene_55-0)** Greene, Tim. ["Father of SSL says despite attacks, the security linchpin has lots of life left"](https://web.archive.org/web/20140531105257/http://www.networkworld.com/news/2011/101111-elgamal-251806.html). *Network World*. Archived from [the original](http://www.networkworld.com/news/2011/101111-elgamal-251806.html) on 2014-05-31. Retrieved 2014-05-30.

1. **[^](#cite_ref-Oppliger_56-0)** Oppliger, Rolf (2016). ["Introduction"](https://books.google.com/books?id=jm6uDgAAQBAJ&pg=PA15). *SSL and TLS: Theory and Practice* (2nd ed.). [Artech House](/source/Artech_House). p. 13. [ISBN](/source/ISBN_(identifier)) [978-1-60807-999-5](https://en.wikipedia.org/wiki/Special:BookSources/978-1-60807-999-5). Retrieved 2018-03-01 – via Google Books.

1. **[^](#cite_ref-57)** Rescorla, Eric (May 2000). [HTTP Over TLS](https://datatracker.ietf.org/doc/html/rfc2818) (Report). Internet Engineering Task Force.

## External links

Wikimedia Commons has media related to [HTTPS](https://commons.wikimedia.org/wiki/Category:HTTPS).

- RFC [8446](https://www.rfc-editor.org/rfc/rfc8446): The Transport Layer Security (TLS) Protocol Version 1.3

v t e Web interfaces Server-side Protocols HTTP v2 v3 Encryption WebDAV CGI SCGI FCGI AJP WSRP WebSocket Server APIs C NSAPI C ASAPI C ISAPI COM ASP Jakarta Servlet container CLI OWIN ASP.NET Handler Python WSGI Python ASGI Ruby Rack JavaScript JSGI Perl PSGI Portlet container Apache modules mod_include mod_jk mod_lisp mod_mono mod_parrot mod_perl mod_php mod_proxy mod_python mod_wsgi mod_ruby Phusion Passenger Topics Web service vs. Web resource WOA vs. ROA Open API Webhook Application server comparison Scripting Client-side Browser APIs C NPAPI LiveConnect XPConnect C NPRuntime C PPAPI NaCl ActiveX BHO XBAP Web APIs WHATWG Audio Canvas DOM SSE Video WebSockets Web messaging Web storage Web worker XMLHttpRequest W3C DOM events EME File Geolocation IndexedDB MSE SVG WebAssembly WebAuthn WebGPU WebRTC WebXR Khronos WebCL WebGL Others Gears Web SQL Database (formerly W3C) WebUSB Topics Ajax and Remote scripting vs. DHTML Browser extension Cross-site scripting and CORS Hydration Mashup Persistent data Web IDL Scripting Related topics Frontend and backend Microservices REST GraphQL Push technology Solution stack Web page Static Dynamic Web standards Web API security Web application Rich Single-page Progressive Web framework

v t e Web browsers Features, standards & protocols Features Bookmarks Extensions Privacy mode Web standards HTML v5 CSS DOM JavaScript WebAssembly Web storage IndexedDB WebGL WebGPU Protocols HTTP Encryption Cookies third-party OCSP WebRTC WebSocket Active Blink-based Proprietary Google Chrome Arc Atlas Avast Cốc Cốc Comet Comodo Ecosia Epic Huawei Maxthon Microsoft Edge Opera (Mobile) Puffin QQ Samsung Silk Sleipnir SRWare UC Vivaldi Whale Yandex FOSS Chromium Brave Dooble Falkon Otter Supermium ungoogled Gecko-based Firefox Floorp GNU IceCat LibreWolf Midori Mullvad SlimBrowser SeaMonkey (uses unnamed Gecko fork) Tor Waterfox Zen Goanna-based Basilisk K-Meleon Pale Moon WebKit-based Safari GNOME Web iCab Orion Multi-engine 360 DuckDuckGo Konqueror Lunascape NetFront qutebrowser Other Dillo eww Flow Ladybird Links Lynx NetSurf Opera Mini w3m Discontinued Blink-based Beaker Citrio Flock Redcore Rockmelt SalamWeb Sputnik Torch Gecko-based Beonex Camino Classilla Conkeror Firefox Lite Galeon Ghostzilla IceDragon Kazehakase Kylo Lotus MicroB Minimo Mozilla suite PirateBrowser Pogo Strata Swiftfox TenFourFox Timberwolf Waterfox Classic xB MSHTML-based Internet Explorer AOL Deepnet GreenBrowser MediaBrowser MSN Explorer MSN Program Viewer NeoPlanet NetCaptor SpaceTime ZAC WebKit-based Arora BOLT Dolphin Fluid Google TV Iris Mercury Nokia Symbian OmniWeb Opera Coast Origyn QtWeb Shiira Steel surf Uzbl WebPositive xombrero Other abaco Amaya Arachne Arena Blazer Cake CM Deepfish Edge Legacy ELinks Gazelle HotJava IBM Home Page Reader IBM WebExplorer IBrowse Internet Explorer for Mac KidZui Line Mode Mosaic MSN TV NetPositive Netscape Skweezer Skyfire ThunderHawk Vision WinWAP WorldWideWeb List Comparison Category

v t e Uniform Resource Identifier (URI) schemes Official about acct crid data file ftp geo gopher http https info ldap mailto nfs nntp sip / sips tag telnet urn view-source ws / wss xmpp Unofficial coffee ed2k gemini feed finger irc / irc6 / ircs ldaps magnet rsync ymsgr Protocol list

v t e TLS and SSL Protocols and technologies Transport Layer Security / Secure Sockets Layer (TLS/SSL) Datagram Transport Layer Security (DTLS) Server Name Indication (SNI) Application-Layer Protocol Negotiation (ALPN) DNS-based Authentication of Named Entities (DANE) DNS Certification Authority Authorization (CAA) HTTPS HTTP Strict Transport Security (HSTS) HTTP Public Key Pinning (HPKP) OCSP stapling Opportunistic TLS Perfect forward secrecy Public-key infrastructure Automated Certificate Management Environment (ACME) Certificate authority (CA) CA/Browser Forum Certificate policy Certificate revocation Certificate revocation list (CRL) Online Certificate Status Protocol (OCSP) OCSP stapling Domain-validated certificate (DV) Extended Validation Certificate (EV) Public key certificate Public-key cryptography Public key infrastructure (PKI) Root certificate Self-signed certificate See also Domain Name System Security Extensions (DNSSEC) Internet Protocol Security (IPsec) Secure Shell (SSH) History Export of cryptography from the United States Server-Gated Cryptography Implementations Bouncy Castle BoringSSL Botan BSAFE cryptlib GnuTLS JSSE LibreSSL MatrixSSL mbed TLS NSS OpenSSL Rustls s2n-tls SChannel SSLeay stunnel wolfSSL Notaries Certificate Transparency Convergence HTTPS Everywhere Vulnerabilities Theory Man-in-the-middle attack Padding oracle attack Cipher Bar mitzvah attack Protocol BEAST BREACH CRIME DROWN Logjam POODLE (in regards to SSL 3.0) Implementation Certificate authority compromise Random number generator attacks FREAK goto fail Heartbleed Lucky Thirteen attack POODLE (in regards to TLS 1.0) Kazakhstan MITM attack

v t e Internet censorship circumvention technologies Background Internet censorship Internet censorship in China National intranet Censorship and blocking technologies IP address blocking DNS cache poisoning Wordfilter Great Firewall of China Blocks on specific websites Facebook GitHub Twitter Wikipedia Principles With a proxy server P2P Web proxies SSH VPN PAC Without a proxy server HTTPS IPv6 transition mechanism hosts DNSCrypt Domain fronting Refraction networking Anti-censorship software Free software Psiphon Shadowsocks OnionShare Orbot Outline VPN GoAgent PirateBox VPN Gate WireGuard Proprietary software Lantern Freegate Ultrasurf Hotspot Shield Telex Proxify Shadowrocket Browser extensions Snowflake uProxy Anonymity Anonymous software Tor JAP (JonDonym) Flash proxy Mixmaster Anonymous P2P network Hyphanet I2P StealthNet Tribler ZeroNet Physical circumvention methods Sneakernet USB dead drop Relevant organizations GreatFire FreeWeibo NetBlocks OONI Turkey Blocks Reference Great Cannon Italics indicates that maintenance of the tool has been discontinued. Category Commons

---
Adapted from the Wikipedia article [HTTPS](https://en.wikipedia.org/wiki/HTTPS) by Wikipedia contributors ([contributor history](https://en.wikipedia.org/wiki/HTTPS?action=history)). Available under [Creative Commons Attribution-ShareAlike 4.0 International](https://creativecommons.org/licenses/by-sa/4.0/). Changes may have been made.