Overview
testssl.sh checks TLS-enabled services for protocol support, cipher configuration and selected cryptographic issues. It works from the command line and produces human-readable and machine-readable reports for remediation.
Key features
TLS protocol and cipher checks; machine-readable output; broad platform support; no separate package manager required for basic use.
Install & first run
# Plain shell script - nothing to compile
git clone --depth 1 https://github.com/drwetter/testssl.sh.git
cd testssl.sh
./testssl.sh https://lab.example.com
# Docker
docker run --rm -it drwetter/testssl.sh https://lab.example.com
# Only the protocol and cipher sections
./testssl.sh --protocols --server-defaults https://lab.example.com
--fast skips the slow checks, --jsonfile out.json writes machine-readable output, and --color 0 keeps logs clean. Docs: https://testssl.sh/
Real-world example
Assess your own public-facing service or staging endpoint and use the report to prioritize outdated protocol and cipher settings.
Common questions
Can it test non-HTTPS services?
It supports TLS/STARTTLS services on various ports; check the official documentation for protocol-specific options.
What is the difference from an online SSL test?
Nothing is uploaded and nothing is stored: the script opens the same TLS connections from your machine, which is what you want for internal or pre-release hosts.
Why do some sections take minutes?
Several checks deliberately test slow or malformed handshakes. --fast skips them, and --wide adds even more.
Can I check a STARTTLS service?
Yes: --starttls smtp|imap|pop3|xmpp|ftp switches protocol, which is how you audit mail servers with the same script.
Related tools
Nikto
Fast web-server vulnerability scanner: outdated software, misconfigurations and dangerous files on your hosts. Free.
Nuclei
Template-driven scanner for CVEs, misconfigurations and exposed panels across thousands of community checks. Free, open source, Go.
Keep exploring: browse every assessment phase in the Pentest Hub.
Authorized testing only — only ever test systems you own or have explicit written permission to assess.
