sslyze
6.3.0 open-sourceThe section your link pointed to isn't on sslyze's page any more, so we've brought you to the top.
Fast and powerful SSL/TLS scanning library.
python -m sslyze www.google.com www.facebook.com --json_out=result.json
results_as_json = results_as_json_file.read_text()
parsed_results = SslyzeOutputAsJson.model_validate_json(results_as_json)
for server_scan_result in parsed_results.server_scan_results:
print(server_scan_result.server_location.hostname)
sslyze --custom_tls_config <path_to_config> <target>
sslyze --certinfo <target>
sslyze --regular example.com --elliptic_curves
parsed_json_result = SslyzeOutputAsJson.parse_file("result.json")
python -m sslyze --resum --resum_attempts=20 www.google.com
python -m sslyze --elliptic_curves www.cloudflare.com
python -m sslyze google.com
python -m sslyze --tls_1_3 www.cloudflare.com
python -m sslyze --early_data www.cloudflare.com
sslyze --update_trust_stores
from sslyze import TrustStoresRepository
TrustStoresRepository.update_default()
sslyze --robot www.google.com
python -m sslyze --tlsv1_3 tls13.crypto.mozilla.org
python -m sslyze --server_info server.example.com:443
sslyze --http_headers ssl.example.com
sslyze --certinfo_basic ssl.example.com
sslyze --certinfo=scan_commands server.example.com:443
sslyze --json_out /tmp/scan_results.json tls://example.com:443
sslyze --regular example.com --xml_out -
sslyze --regular example.com --xml_out output.xml
sslyze --targets_in targets.txt
sslyze --compression example.com
sslyze --starttls=imap imap.example.com:993
sslyze --starttls=rdp my-rdp-server.com
sslyze my-server.com --nb_retries 3
sslyze --heartbleed <target>
sslyze --https_tunnel=http://user:password@proxy.example.com:8080 <target>
sslyze --chrome_sha1 server.example.com:443
Summary
sslyze is an open-source SSL/TLS scanning tool and Python library, free to use, and it is run as a command-line tool (installable via pip, Docker, or a precompiled Windows executable) or embedded directly into Python applications through its API. It connects to a server to check certificate validity, cipher suites, elliptic curves, and exposure to known TLS attacks like Heartbleed and ROBOT, checking results against Mozilla's recommended TLS profiles or a custom baseline. This suits application security engineers and developers who want TLS checks wired into CI/CD rather than run manually, and it covers non-HTTP protocols like SMTPSMTPThe application-layer protocol used to send email between servers and from clients to servers; cyber tools use it to relay alerts, phishing simulations, or exfiltrated data over standard mail infrastructure. and LDAPLDAPA protocol for querying and modifying directory services, standardized under RFC 4511, commonly used to look up users, groups, and attributes in corporate identity stores like Active Directory. as well as HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate.. It sits in the TLS/certificate scanning category rather than broader web-app testing. First committed in 2011, it has 86 contributors and a release within the past five months, so it is actively maintained.
Fast and powerful SSL/TLS scanning library.
How sslyze helps
Will my server's certificate be trusted by the browsers and devices my users actually run?
validates the chain against five separate trust stores (Android, Apple, Java, Mozilla, Windows) and reports issuer, expiry, and structural problems like a missing subjectAltName that would cause silent trust failures on some platforms but not others
Is this server still open to known TLS attacks like Heartbleed or ROBOT?
actively probes for each named vulnerability (Heartbleed, ROBOT, OpenSSL CCS injection, insecure renegotiation, downgrade attacks) and reports vulnerable or not for each, rather than inferring risk from version numbers alone
Does this endpoint meet the TLS baseline my organization or Mozilla recommends?
runs the relevant scan commands automatically against Mozilla's old/intermediate/modern profiles, or against a custom baseline profile supplied as a file, and reports where the server's cipher suites, protocols, and curves fall short
Can I catch a TLS misconfiguration before it reaches production?
runs as a step in a CI/CD pipeline or is called through the Python API from application code, so a scan and compliance check happen automatically on every build rather than manually after deployment
Is my mail server or directory service exposed the same way my HTTPS servers are?
scans non-HTTP protocols like SMTP, XMPP, LDAP, POP, IMAP, RDP, Postgres and FTP using their own STARTTLS negotiation, giving the same certificate and cipher analysis outside of a browser context
Can I get a TLS reading on a server that's addressed only by IP, with no hostname?
retrieves the certificate chain even when no Server Name Indication is supplied, which matters for IP-only endpoints that would otherwise be skipped or misread by tools that require SNI
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 sslyze, 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 sslyze 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
36 entries
No entries match these filters.
- October 20261
- December 20251
- August 20251
- January 20251
- September 20231
- April 20231
- January 20231
- October 20221
- March 20221
- November 20211
- November 20201
- June 20201
- April 20201
- December 20181
- September 20181
- March 20181
- February 20181
- December 20172
- November 20171
- September 20171
- April 20171
- February 20171
- October 20161
- September 20161
- June 20161
- February 20162
- September 20151
- April 20151
- September 20146
Project health
Issue, contributor and maintainer activity in nabla-c0d3/sslyze, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 2 −5 vs prior 12 months
- Maintainers 1 +0 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 83% of issues opened, last 12 months
- Median time to close 131 days first maintainer reply 7.2 days
- Open backlog 24 of 557 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 24
- Contributors / month 0
- Commits / month 0
- Stars 3,781
- bugs 8%
- other 92%
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.