It's very easy to have a '' statement to include a CSS style sheet which shows a warning for older IE version However IE10 no longer supports this syntax in standards mode and it is an affected browser.

You could also do some browser detection on your website to add a warning to these users for a month or so before you switch off TLS 1.0 and 1.1. You will be mostly concerned with older versions of IE and older versions of android. Highly recommend doing this scan anyway to see the state of your SSL/TLS config. You can also use the ssllabs scanning tool ( ) which will scan you site to test your SSL/TLS setup - including a telling you which version of TLS and which cipher a list of reference browsers will use. , and that should allow you to work out a rough percentage. Once you have the browser and OS version of your visitors, you can look up this table to see if they support TLS 1.2: See here for more details on how to go about doing it that way if you want.

Note using Google Analytics or the like is much better than trying to figure out the cryptic USER_AGENT field, though in theory that's another way of doing this and that will probably be logged in your server logs. This won't be 100% accurate (some people turn off JavaScript and/or tracking in their browsers). Google Analytics) which track OS and browser versions. So the best way I can think of doing this is if you use any analytics software (e.g. I'm not aware of any way of checking server logs to see what SSL/TLS protocol was used for the connection for Windows server (its easy enough with Nginx and Apache).

Hwo to test tls 1.2 iis