# TLS 1.3 support on iOS **URL:** \ **Category:** Feature Proposal\ **Tags:** ios\ **Created:** [September 21, 2022, 7:52pm UTC](https://support.delta.chat/t/tls-1-3-support-on-ios/2239 "2022-09-21T19:52:11Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![scatterd](https://support.delta.chat/user_avatar/support.delta.chat/scatterd/32/1566_2.png) [@scatterd](https://support.delta.chat/u/scatterd)\ **Post date:** [September 21, 2022, 7:52pm UTC](https://support.delta.chat/t/tls-1-3-support-on-ios/2239/1 "2022-09-21T19:52:11Z")
Hi, I have a security-related feature request. As far as I can tell DC on iOS does not support TLS 1.3 I’m running my IMAP server on TLS 1.3 only. Android and flatpak clients can log in but on iOS the TLS handshake fails with the following error: ```auto dovecot: imap-login: Disconnected: Connection closed: SSL_accept() failed: error:0A000102:SSL routines::unsupported protocol (no auth attempts in 0 secs): Delta Chat: Error: error code -9806 ``` I’m running Delta Chat v.1.32.0 on iOS 16. ---
**Author:** ![info\_fx](https://support.delta.chat/letter_avatar_proxy/v4/letter/i/c4cdca/32.png) [@info\_fx](https://support.delta.chat/u/info_fx)\ **Post date:** [December 13, 2025, 3:48pm UTC](https://support.delta.chat/t/tls-1-3-support-on-ios/2239/2 "2025-12-13T15:48:09Z")
In general it looks like DeltaChat stoped or never did sending SNI during request to server, so server replies with default certificate, which creates error during TLS handshkae. When a client does not send the Server Name Indication (SNI) extension during a TLS handshake, the server cannot determine which hostname the client is trying to reach if it hosts multiple secure websites on a single IP address. This leads to a **certificate mismatch error** and a failed connection. The most effective solution is to upgrade the DeltaChat or application library to a modern version that supports SNI.