We're now 3.2rc2 and 3.0.8 (stable).Īs of 2019, you should use the latest 3.0.x version as 2.9.5 is not supported anymore.Īs I do releases on github you can pull the zip for a stable release from there.

If you want a deductable commercial invoice in return please get in touch with me before using paypal.ĭevelopment takes place at github.

If you like this software, you or your company uses it a lot or even your company makes money from any service around testssl.sh, why not support the project with a donation? It helps keeping the project alive and kicking.ĭirk setup a paypal account for it, keeps track of the money and makes sure it is spend on project related activities. In addition starting from version 3.0rc1 if you're offering it as a public and / or paid service you need to mention to your audience that you're using this program and where to get this program from. You can use it under the terms of GPLv2, please review the License before using it. License testssl.sh is free and open source software. Documentation: In HTML, markdown or groff format.Heck, even the development is open (github) You can look at the code, see what's going on and you can change it. Privacy: It's only you who sees the result, not a third party.Verbosity: If a particular check cannot be performed because of a missing capability on your client side, you'll get a warning.

Reliability: features are tested thoroughly.

Toolbox: Several command line options help you to run your test and configure your output.

Flexibility: You can test any SSL/TLS enabled and STARTTLS service, not only webservers at port 443.

Alternatively a Dockerfile is provided or you can just use docker run -rm -ti drwetter/testssl.sh.

OpenBSD only needs bash to be postinstalled.

Ease of installation: Works for Linux, Mac OSX, FreeBSD, NetBSD and WSL/MSYS2/Cygwin out of the box: no need to install or configure something, no gems, CPAN, pip or the like.

Clear output: you can tell easily whether anything is good or bad.

How to test tls 1.2 connection