PAGES
← all tools
◆ Web Application Security

sslscan

2.2.3 open-source

sslscan tests SSL/TLS enabled services to discover supported cipher suites

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

all 8 features, with the evidence for each →

Languages

Not documented

Features

8 capabilities · 4 backed by code, an API document or a real run

Built from sslscan's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What sslscan offers you

  • Command-line interface2
All capabilities 8 capabilities
Cipher suite and signature reporting verified Enumerates supported cipher suites and signature algorithms, with the option to display cipher names using IANA/RFC naming rather than OpenSSL naming. 6 releases · 3 other sources · first seen Sep 2015

Also counts toward: Command-line interface

release

command line

  • --iana-names — Use IANA/RFC cipher names rather than OpenSSL ones 2.0.11 · Dec 2021 · command-line history
  • --show-sigs — Enumerate signature algorithms 2.0.7 · Feb 2021 · command-line history

example

  • Scan a host and output cipher suites using standardized IANA naming for easier reference against other documentation. sslscan --iana-names example.com 2.0.11 · Dec 2021 · source
Post-quantum key exchange scanning verified Supports scanning for post-quantum key exchange groups, including X25519MLKEM768 and PQ hybrid key exchange. 4 releases · 4 other sources · first seen Jun 2025

release

  • Adds --all-groups flag to scan for key exchange groups on all supported TLS protocols, not just the negotiated one.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ 2.2.3 · Sep 2026 · source · release history
  • Adds --all-groups flag to scan on all TLS protocols 2.2.3 · Sep 2026 · source · release history
  • Adds support for PQ hybrid key exchange groups 2.2.1 · Nov 2025 · source · release history
  • Supports scanning post-quantum key exchange groups such as X25519MLKEM768. 2.2.0 · Jun 2025 · source · release history

docs

  • --all-groups Enumerate key exchange groups for all supported TLS versions, not just the highest among TLS 1.0, 1.1, and 1.2. Use when auditing servers that may have different group policies per protocol version. docs update · Sep 2026 · source

command line

  • --all-groups — Enumerate key exchange groups for all supported TLS versions, not just the highest among TLS 1.0, 1.1, and 1.2. Use when auditing servers that may have different group policies per protocol version. 2.2.3 · Sep 2026 · command-line history

example

  • Scan a target against every available TLS protocol version and cipher group simultaneously. sslscan --all-groups <host> <port> 2.2.3 · Sep 2026 · source
  • Enumerate supported key exchange groups across all TLS protocol versions on a target to catch group misconfigurations not visible in a single handshake. sslscan --all-groups <target>:443 2.2.3 · Sep 2026 · source
Verbose output verified Displays verbose output during tool execution. 2 releases · 3 other sources · first seen Mar 2020

release

  • Enable --quiet flag in sslscan 2.1.3 CLI for quiet shutdown of the scan process. 2.1.3 · Jan 2024 · source · release history
  • Prints ECC certificate curve names and associated key strengths in output 2.0.0-beta1 · Mar 2020 · source · release history

docs

  • Scans SSL/TLS services to enumerate supported protocols, cipher suites, key exchange groups, and certificate details.

command line

example

  • Run a silent scan to suppress all output except errors, useful for scripting or background tasks. sslscan --quiet <target_host> 2.1.3 · Jan 2024 · source
Cipher preference order reporting shipped Displays the cipher suites in the order preferred by the server during the handshake. 5 releases · first seen Sep 2015

release

  • Adds support for SSLv2 and SSLv3 protocol checks via internal implementation 2.0.0 · Jul 2020 · source · release history
  • Adds support for TLSv1.3 protocol checks via internal implementation 2.0.0 · Jul 2020 · source · release history
  • Adds SSLv2 and SSLv3 protocol detection regardless of OpenSSL 2.0.0-alpha1 · Feb 2020 · source · release history
  • Adds TLSv1.3 protocol detection 2.0.0-alpha1 · Feb 2020 · source · release history
  • Outputs ciphers in order of server preference 1.11.0 · Sep 2015 · source · release history
TLS certificate chain inspection verified Displays the full certificate chain returned by a TLS handshake. 1 release · 1 other source · first seen Sep 2015

release

command line

  • --show-certificates — Display the full certificate chain. 2.1.4 · Jun 2024 · command-line history
Protocol version forcing shipped Forces the tool to connect using specific IP versions (IPv4 or IPv6) via command-line flags. 1 release · 1 other source · first seen Dec 2017

Also counts toward: Command-line interface

release

example

  • Force sslscan to connect over IPv6 only, useful for testing dual-stack servers or bypassing IPv4 routing issues. sslscan -6 target.com 1.11.11 · Dec 2017 · source
Enhanced visual grading output shipped Updates coloring of ciphers and algorithms to provide clearer visual grading of scan results. 1 release · first seen Jun 2025

release

  • Updated colouring of ciphers and algorithms for clearer visual grading of scan results. 2.2.0 · Jun 2025 · source · release history
TLS certificate curve reporting shipped Reports Elliptic Curve (ECC) certificate curve names and associated key strengths in the output. 1 release · first seen Mar 2020

release

  • Prints ECC certificate curve names and associated key strengths in output 2.0.0-beta1 · Mar 2020 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. 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 →

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…

Explore the full chart →

Releases

Show

11 entries

  1. September 20262
  2. November 20251
  3. June 20251
  4. January 20241
  5. December 20211
  6. July 20201
  7. March 20201
  8. February 20201
  9. December 20171
  10. September 20151
    Show

    11 entries

    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.

    1. Contributors 6 −1 vs prior 12 months
    2. Maintainers 1 +0 joined · −2 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 7.5 days first maintainer reply 3.9 days
    6. Open backlog 58 of 204 issues ever filed
    1. Issues opened / month 1 · 0 communitymaintainers
    2. Open backlog 58
    3. Contributors / month 1
    4. Commits / month 2
    5. Stars 2,624
    Issue themes, last 12 months
    • 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.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →