<p>Stuart Henderson wrote at <a href="https://www.monitoring-plugins.org/archive/devel/2015-September/010076.html">https://www.monitoring-plugins.org/archive/devel/2015-September/010076.html</a>:</p>

<p>You could do something like this which changes the default check to<br>
TLSv1.0+ (I think at this point in the game it's reasonable to consider<br>
a service which doesn't TLS at all as down/broken ;-) and adds a new<br>
option to enforce TLSv1.2+ (allowing it to autodetect and connect to<br>
future protocol versions).</p>

<p><a href="https://github.com/monitoring-plugins/monitoring-plugins/files/2220/check_http_support_TLS_v1.2.patch.txt">check_http_support_TLS_v1.2.patch.txt</a></p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br><a href="https://github.com/monitoring-plugins/monitoring-plugins/issues/1338#issuecomment-141904034">Reply to this email on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AFQl2fcMPuE14eFM74x7KO6eBIJNob68ks5oz7LwgaJpZM4EXI0C.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/monitoring-plugins/monitoring-plugins/issues/1338#issuecomment-141904034"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>