Cloudflare SSL cipher, browser, and protocol support

Understand which TLS ciphers and protocols are supported by Cloudflare. Learn which browsers Cloudflare SSL certificates support and which intermediate and root certificates are used to sign Cloudflare certificates.

Cloudflare TLS/SSL cipher support

Since traffic encryption occurs either between website visitors and Cloudflare or between Cloudflare and your origin web server, Cloudflare distinguishes between:

Origin web server TLS/SSL ciphers supported by Cloudflare

Depending on the SSL option specified in the Cloudflare Crypto app, Cloudflare either connects to an origin web server over HTTP or HTTPS. Below is the list of origin server SSL ciphers that Cloudflare supports for TLS 1.3, TLS 1.2, and earlier TLS versions when connecting to your origin web server over HTTPS:

TLS 1.2 and earlier TLS versions:

  • AES128-GCM-SHA256
  • AES128-SHA
  • AES256-SHA

TLS 1.3:

Cipher Suite Name (IANA)

Cipher Suite (Octal Value)








Cloudflare TLS/SSL ciphers

The configuration of both the client browser and the web server determine the cipher suite used, not the SSL certificate. When a browser initiates an HTTPS connection, it sends a list of cipher suites it supports. The web server then picks the one it wants to use.

Cloudflare currently prefers to negotiate a connection using AES128. To use AES256, a client’s browser must enforce a 256 bit cipher suite. Our preference to use AES128 may change in the future.

Below is the list of SSL ciphers that Cloudflare supports for TLS 1.3 and TLS 1.2 and older for customer’s on paid plans:


OpenSSL Name

TLS 1.0

TLS 1.1

TLS 1.2

TLS 1.3
























For the most current details on Cloudflare’s SSL configuration, see our public repository of SSL configurations.

Free domains using Universal SSL are issued SHA2+ECDSA certificates. This requires client browsers that support elliptic curve cryptography (ECC) and SNI.

Cloudflare TLS/SSL protocol support

Cloudflare only uses TLS 1.0, TLS 1.1, TLS 1.2, and TLS 1.3 to establish SSL connections between the visitor and Cloudflare.

TLS 1.2 became the industry standard in 2008. Both the Payment Cards Industry Security Standards Council (PCI SSC) and the National Institute of Standards and Technology (NIST) endorse TLS 1.2 for tighter security on the web.

SSLv3 is not supported due to security vulnerabilities. TLS Version 1.0 is considered insecure due to its vulnerability to attacks such as BEAST and POODLE.

Cloudflare TLS/SSL modern browser support

Cloudflare deploys additional SSL certificates for paid plans than compared to Free plans. This allows paid plans to support certain older devices. For information on what SSL protocols and ciphers your current browser supports, visit

Modern browser support for domains on paid Cloudflare plans

Cloudflare SSL certificates utilize the Subject Alternative Names (SAN) extension to support multiple domains on the same SSL certificate.  Additionally, Dedicated Certificates and Universal SSL certificates use Server Name Indication (SNI) with Elliptic Curve Digital Signature Algorithm (ECDSA). SNI and ECDSA certificates work with the following modern browsers:

Desktop Browsers installed on Windows Vista or OS X 10.6 or later:

  • Internet Explorer 7
  • Firefox 2
  • Opera 8 (with TLS 1.1 enabled)
  • Google Chrome v5.0.342.0
  • Safari 2.1

Mobile Browsers:

  • Mobile Safari for iOS 4.0
  • Android 3.0 (Honeycomb) and later
  • Windows Phone 7

Modern browser support on Free Cloudflare domains

Due to fewer SSL certificates provided for Cloudflare domains on Free plans, SSL browser support for Free domains is limited to slightly newer browsers:

Minimum supported desktop browsers:

  • Firefox 2
  • Internet Explorer 7 on Windows Vista
  • Windows Vista or OS X 10.6 with:
    • Chrome 5.0.342.0
    • Opera 14
    • Safari 4

Minimum supported mobile browsers:

  • Mobile Safari on iOS 4.0
  • Android 4.0 ("Ice Cream Sandwich")
  • Windows Phone 7
For compatibility with older browsers/operating systems, upgrade your domain to Pro, Business, or Enterprise.

Cloudflare TLS/SSL Legacy Browser Support

Legacy Browser Support allows website owners with a paid Cloudflare plan to provide a secure connection for visitors with an older operating system or browser. Legacy Browser Support toggles whether your domain supports client browsers connecting via a SHA-1 SSL certificate.

When a visitor connects to a website protected by Cloudflare, the optimal certificate presented to the browser is automatically determined during the SSL/TLS handshake:

  1. Cloudflare presents an ECDSA SHA-256 certificate to browsers supporting Elliptic Curve Cryptography (ECC) and SHA-2 signatures.
  2. Cloudflare presents an RSA SHA-256 certificate to browsers supporting SHA-256 but not ECC.
  3. If the browser doesn’t support ECC or SHA-256, Cloudflare serves an RSA SHA-1 certificate.

Examples of browsers that do not support SHA-256 signatures and require RSA SHA-1 include:

  • IE on Windows XP SP2 (or earlier), and
  • pre-Gingerbread Android devices.

Business or Enterprise customers with specific concerns about SHA-1 security can disable Legacy Browser Support in their Cloudflare protected sites.

Disable Legacy Browser Support (Business or Enterprise domains only)

Disabling Legacy Browser Support causes errors for visitors with older operating systems (OS) or browsers establishing an HTTPS session with your website. These errors are not always obvious or prominently displayed in the visitor’s browser.

These minimum OS and browser versions are required when SHA-1 support is disabled:

  • IE7 on Windows Vista
  • Google Chrome on Windows Vista or OS X 10.5.7
  • Safari 3.0 on Windows Vista or Mac OS X 10.5.6
  • Mozilla Firefox 2.0
  • Opera 8.0 (with TLS 1.1 enabled)
  • BlackBerry 10
  • Windows Phone 7
Disabling Legacy Browser Support also prevents browsers without Server Name Indication (SNI) support from connecting to your site.

To Disable Legacy Browser Support:

1. Log in to the Cloudflare dashboard.

2. Click the appropriate Cloudflare account for your domain.

3. Ensure the proper domain is selected.

4. Click the Crypto app.

5. Scroll to the Legacy Browser Support section and click Disable SHA-1Support.

6. Read the warning messages in the modal that appears.

7. To proceed, check the I understand box and click Disable.

If you only have a SHA-1 custom SSL certificate, it is still served to your customers when SHA-1 support is disabled.  Upload a replacement SHA-2 certificate and remove the existing SHA-1.

SSL intermediates and roots used to sign Cloudflare certificates

Universal SSL certificates are issued by Comodo or Digicert. Dedicated SSL and SSL for SaaS certificates are issued by Digicert.


Click to expand the collapsed content below for details on the root and intermediate certificates used to sign the following Cloudflare certificates:


Click to expand the collapsed content below for details on the root and intermediate certificates used to sign the following Cloudflare certificates:

Related resources

Not finding what you need?

95% of questions can be answered using the search tool. This is the quickest way to get a response.

Powered by Zendesk