TLS 1.0 and its deprecated predecessor, SSL are vulnerable to some well-known security issues such as POODLE and BEAST attacks. When we run the same app on a Windows 10 or Windows Server 2012 R2, the app doesn't encounter the error and SSLLabs reports TLS 1.2 as available.Transport Layer Security (TLS) are cryptographic protocols designed to provide communications security over a computer network, typically between a website and a browser. (*) Without JavaScript, this test reliably detects only the highest

Trying the SSLLabs site, it got these results: The handle is in the wrong state for the requested operation Trying the FancySSL site, it got this error: Unfortunately, our app did not work seamlessly on Windows 2008 R2. According to may not work correctly if your client doesn't send SNI and doesn't handle (or mishandles) renegotiation.It appears to be an individual's site and despite a good Google rank, it doesn't seem like a long term stable solution.The site won't require TLS 1.2 in a way which emulates the behavior of sites which do.Īs pointed out in the comments, this site will only work if TLS 1.2 is available:.Our app could be configured either way, but some might not. The site doesn't allow a POST it requires a GET.

It appears not to be required, as we were able to show different responses as between a Windows 10 machine running the app and a Windows Server 2008 R2 server running the app. It's not crystal clear whether the response requires JavaScript to give a valid response. The response is designed for human consumption in a browser.As pointed out in the comments, this site assesses the client capabilities and reports on them in the response:

Test tls 1.2 support in net framework