sslscan
2.2.3 open-sourceThe section your link pointed to isn't on sslscan's page any more, so we've brought you to the top.
sslscan tests SSL/TLS enabled services to discover supported cipher suites
sslscan --all-groups <target> sslscan --all-groups <target>:443 sslscan --quiet <target_host> sslscan --iana-names example.com sslscan -6 target.com
Summary
sslscan is an open-source command-line tool that scans SSL/TLS services to enumerate supported protocols, cipher suites, key exchange groups, and certificate details. It runs from the terminal or as a Docker container, and its output flags colour-code weak ciphers (SSLv2/SSLv3, RC4, 3DES) against stronger configurations like PFS with GCM, so a reader can grade a server's configuration at a glance. It is aimed at people doing hands-on TLS configuration review — penetration testers, sysadmins hardening servers, and application security engineers — rather than teams wanting continuous monitoring across a fleet. Version 2 rewrote the scanning backend so checks no longer depend on the host's OpenSSL version, adding support for legacy SSLv2/SSLv3 and TLSv1.3 plus post-quantum key exchangepost-quantum key exchangeA cryptographic handshake algorithm designed to resist attacks from quantum computers, using math problems like lattices that quantum algorithms cannot efficiently solve, letting tools stay secure against future quantum-capable adversaries. groups. First committed in 2010 and still active, with 67 contributors and a release 144 days ago.
sslscan tests SSL/TLS enabled services to discover supported cipher suites
How sslscan helps
Which weak protocols and ciphers is this server still willing to negotiate?
connects and walks the full set of SSL/TLS versions and cipher suites, flagging SSLv2/SSLv3, RC4, 3DES, NULL and export-strength ciphers so a reader can spot them immediately instead of reading a raw handshake list
Is this configuration actually using forward secrecy where it should be?
colour-codes cipher suites that combine perfect forward secrecy with GCM as strong versus weaker CBC or non-PFS choices, letting a reader grade the negotiated set at a glance
Is this server exposed to POODLE-style downgrade issues?
separately highlights CBC ciphers offered under SSLv3 so that combination stands out from the rest of the cipher list
What does this server's certificate chain and signing setup actually look like?
retrieves the certificate presented in the handshake, and can pull the full chain and enumerate the signature algorithms in use so a reader can check for weak signing or an incomplete chain
Are the key exchange groups this server offers consistent across every TLS version it supports?
repeats the key exchange enumeration against each supported protocol version separately, rather than only the one negotiated by default, surfacing groups offered under one version but not another
Is this server ready for post-quantum key exchange?
checks the negotiated and offered groups against post-quantum entries such as the newer hybrid key exchange groups and reports whether the server will select them
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for sslscan, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail sslscan puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
11 entries
No entries match these filters.
- September 20262
- November 20251
- June 20251
- January 20241
- December 20211
- July 20201
- March 20201
- February 20201
- December 20171
- September 20151
Project health
Issue, contributor and maintainer activity in rbsec/sslscan, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 6 −1 vs prior 12 months
- Maintainers 1 +0 joined · −2 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 7.5 days first maintainer reply 3.9 days
- Open backlog 58 of 204 issues ever filed
- Issues opened / month 1 · 0 communitymaintainers
- Open backlog 58
- Contributors / month 1
- Commits / month 2
- Stars 2,624
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.