TLS 1.3: Browser Support, Features, vs TLS 1.2

What is TLS 1.3?

TLS 1.3 is the Transport Layer Security protocol version that the IETF standardized as RFC 8446. It encrypts data between a browser and a server using a faster handshake and a smaller cipher suite list than TLS 1.2. Web browsers, web servers, load balancers, and CDNs use it to secure HTTPS traffic.

Which browsers does TLS 1.3 support?

TLS 1.3 works in every major modern browser, including Chrome, Edge, Firefox, Safari, Opera, and Samsung Internet, on desktop and mobile. Internet Explorer 11 is the only mainstream browser that never added support.

What are the key features of TLS 1.3?

TLS 1.3 cuts the handshake to one round trip, drops insecure ciphers, encrypts most handshake messages, and makes forward secrecy mandatory.

• One-round-trip handshake: TLS 1.3 sets up a secure connection in a single round trip. The client sends its key share in the first flight, so the new-connection handshake finishes one round trip faster than TLS 1.2.
• 0-RTT session resumption: When the client has connected to the server before, TLS 1.3 can resume the session in zero round trips. The client sends application data in the first packet, the server replies, and the connection is live.
• Mandatory forward secrecy: Every TLS 1.3 session uses an ephemeral Diffie-Hellman key, so a stolen private key cannot decrypt past traffic. The TLS 1.2 RSA key transport mode that broke this guarantee is removed.
• Five AEAD cipher suites only: TLS 1.3 keeps TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384, TLS_CHACHA20_POLY1305_SHA256, TLS_AES_128_CCM_SHA256, and TLS_AES_128_CCM_8_SHA256. RC4, MD5, SHA-1, CBC-mode ciphers, RSA key transport, and static Diffie-Hellman are gone.
• Encrypted handshake messages: Every handshake message after the ServerHello is encrypted, including the server certificate. Passive observers see the ClientHello, the ServerHello, and almost nothing else.
• Signature scheme upgrade: TLS 1.3 servers must sign with RSA-PSS or ECDSA. Old RSA-PKCS1-v1_5 signatures are out, which lifts the signing security floor across the web.

How do you enable TLS 1.3 in your browser?

TLS 1.3 is on by default in every modern browser. You only flip a flag if your IT team disabled the protocol, or you are running an old Firefox or Chrome build that shipped a draft version.

• Open the browser flags page: Type chrome://flags in Chrome or edge://flags in Edge and press Enter. Firefox users open about:config and accept the warning.
• Search for the TLS 1.3 entry: In the search box, type tls and look for the TLS 1.3 entry. On Firefox, search for security.tls.version.max.
• Set the value to Enabled: Choose Enabled in the dropdown on Chrome or Edge. On Firefox, set security.tls.version.max to 4, the value that maps to TLS 1.3.
• Relaunch the browser: Click Relaunch at the bottom of the flags page so the change takes effect on every tab.
• Confirm the negotiation: Open any HTTPS page, click the padlock icon in the address bar, and read the connection details. The line should list TLS 1.3.

If the connection still uses TLS 1.2 after the relaunch, a corporate proxy, firewall, or antivirus product is forcing the downgrade. Whitelist the site or disable TLS interception on the test machine.

// Paste this snippet into the DevTools console of any modern browser to confirm TLS 1.3.
// The check uses the Network panel of DevTools because the JS Security API does not
// expose the negotiated TLS version directly.
console.log("Open the DevTools Security tab and reload the page.");
console.log("Look for: 'Connection - secure connection settings: TLS 1.3'.");

// Programmatic alternative: inspect performance entries for the main document.
const nav = performance.getEntriesByType("navigation")[0];
if (nav && nav.nextHopProtocol) {
  console.log("Next-hop protocol:", nav.nextHopProtocol);
} else {
  console.log("Performance Navigation Timing is unavailable in this context.");
}

What are the known issues with TLS 1.3?

TLS 1.3 ships in every modern browser, but middleboxes, legacy IE 11 traffic, and 0-RTT replays still cause real-world friction.

• Middlebox interference: Some corporate firewalls, intrusion-detection systems, and antivirus proxies block or downgrade TLS 1.3 because the encrypted handshake breaks deep packet inspection. Browsers fall back to TLS 1.2 or fail the connection outright.
• Internet Explorer 11 traffic: Sites that still serve IE 11 visitors must keep TLS 1.2 enabled at the load balancer or origin. Disabling TLS 1.2 to enforce TLS 1.3 will drop those connections.
• 0-RTT replay risk: 0-RTT early data can be replayed by an active attacker. Servers must mark only idempotent endpoints as 0-RTT safe and refuse early data on writes, payments, and login.
• Server certificate signature mismatch: Old TLS 1.3 draft clients reject certificates signed with RSA-PKCS1-v1_5. TLS 1.3 servers must sign with RSA-PSS or ECDSA to interoperate with every client in the wild.
• Captive portal downgrades: Some hotel and airport Wi-Fi gateways man-in-the-middle TLS to redirect users to a portal. The browser logs a TLS error until the user completes the portal flow, after which TLS 1.3 negotiates cleanly.
• Old Android WebView builds: Apps embedding the legacy Android System WebView below WebView 70 negotiate TLS 1.2 only. Update the WebView component or move the app to a modern WebView build.

In my experience, the middlebox issue is the most common reason a TLS 1.3-capable browser still negotiates TLS 1.2 on a corporate network. The fix is rarely on the browser side: ask your IT team to whitelist the destination or disable TLS interception for development domains.

Citations

All TLS 1.3 version numbers and platform notes in this guide come from these primary sources:

• IETF RFC 8446 - The Transport Layer Security (TLS) Protocol Version 1.3: datatracker.ietf.org/doc/html/rfc8446
• IETF RFC 5246 - The Transport Layer Security (TLS) Protocol Version 1.2: datatracker.ietf.org/doc/html/rfc5246
• MDN Web Docs - Transport Layer Security: developer.mozilla.org/en-US/docs/Web/Security/Transport_Layer_Security
• Wikipedia - Transport Layer Security: en.wikipedia.org/wiki/Transport_Layer_Security
• Wikipedia - Version history for TLS/SSL support in web browsers: en.wikipedia.org/wiki/Version_history_for_TLS/SSL_support_in_web_browsers
• Mozilla Hacks - TLS 1.3 in Firefox: hacks.mozilla.org/2018/03/transport-layer-security-version-1-3-in-firefox
• WebKit - Safari Release Notes: developer.apple.com/documentation/safari-release-notes
• Chromium - TLS 1.3: chromium.org/Home/tls13
• Microsoft Security Blog - Taking Transport Layer Security (TLS) to the next level with TLS 1.3: microsoft.com/en-us/security/blog/taking-transport-layer-security-tls-to-the-next-level-with-tls-1-3
• Cloudflare SSL/TLS docs - TLS 1.3: developers.cloudflare.com/ssl/edge-certificates/additional-options/tls-13
• Cloud Google blog - TLS 1.3 is now on by default for Google Cloud services: cloud.google.com/blog/products/networking/tls-1-3-is-now-on-by-default-for-google-cloud-services