Mozilla published several TLS profiles with varied compatibility/security tradeoffs. Note that there are lots of other parameters that affect security, including ciphers and various other settings. You probably want to compare against your own Analytics for the business impact on your own site. So disabling TLS v1.0 would mean rejecting HTTPS from a bit over 4% of browsers out there. It may vary a bit based on your target markets.

You can use our good friend Can I Use, which tells us that TLS v1.1 is supported since: It is often possible to configure web-servers and other services to not support TLS 1.0 - thus blocking browsers that don't support more recent versions. Preventing use of insecure protocols by browsers a week) you would have some good statistics about the number of customers affected. If you need to work out how many of a server's customers rely on TLS 1.0 you can enable TLS version logging in Apache and probably in other webservers etc. Predicting Impact of barring browsers that use TLS 1.0 This makes relying on a list more risky.ĭepending on what you are doing, you may not need a list of browsers (user agents?).

A browser might not be on such a list because it has support for TLS 1.2 even if support for 1.1 and 1.2 is disabled by default. Trouble finding a suitable list might be partly because such a list might be large, incomplete, frequently changing and might need to take account very large numbers of plugins and addons.Īs Tripehound mentioned in a comment. I am having trouble finding a list Lists of browsers with specific features

What is an insecure browser