PAGES
← all tools
◆ Exploitation & C2

sslstrip

5.0.0 open-source

sslstrip is a Linux proxy that implements Moxie Marlinspike's HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. stripping attacks for authorized testing only.

Summary

sslstrip is an open-source command-line MITM proxy, free to use, that implements Moxie Marlinspike's SSL stripping attacks by rewriting HTTPS links to HTTP so a man-in-the-middled victim stays on plaintext while believing the connection is secure. It is run from a Linux host via subcommands (run, doctor, cleanup), paired with IP forwarding, nftables rules, and arpspoof to redirect target traffic, which makes it a fit for red teamers and penetration testers doing authorized lab engagements rather than anyone needing a production defensive tool. Originally a Python 2 tool ported to Python 3, it now requires Python 3.14+, and with 7 contributors, 25 commits in the past year, and a release just 36 days ago, it remains actively maintained.

sslstrip is a Linux proxy that implements Moxie Marlinspike's HTTPS stripping attacks for authorized testing only.

How sslstrip helps

What is actually happening to my target's traffic while I have them on my network?

intercepts their HTTP requests and rewrites the HTTPS links inside those pages to plain HTTP, so their browser never upgrades and every subsequent request stays visible to the tool

Did my target ever send credentials or session data in the clear during this session?

can capture the unredacted traffic to a file for the duration of a strip session, giving a record to review afterward for anything sent in plain text

Is my intercept setup actually positioned to catch the target's traffic before I start?

runs a read-only pre-flight check that verifies forwarding, firewall rules, and the listener are correctly wired before a session launches

Will my machine still pass traffic normally once I stop the attack?

tracks its own firewall and forwarding changes under a managed session and restores the original state on cleanup, including recovering a session left in a stale state

Can I strip traffic aimed at servers on a private internal PKI rather than the public web?

accepts a supplied lab certificate authority bundle so its internal TLS client can verify and reach upstream servers that use non-public certificates

Why did some requests in this session fail instead of getting stripped?

returns distinct error responses for cases like a missing host header, a CONNECT request, a protocol upgrade, or an upstream failure, so a failed request can be traced to a specific cause rather than looking like a silent drop

all 4 features, with the evidence for each →

Languages

Not documented

Features

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

Built from sslstrip'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 sslstrip offers you

  • Command-line interface1
All capabilities 4 capabilities
Operational diagnostics and maintenance verified Provides dedicated subcommands for environment validation, session recovery, and version reporting to aid in lab management. 3 releases · 4 other sources · first seen Aug 2026

Also counts toward: Command-line interface

release

  • Adds sslstrip run, sslstrip doctor, sslstrip cleanup, and sslstrip --version subcommands. 5.0.0 · Aug 2026 · source · release history
  • Adds sslstrip run, sslstrip doctor, sslstrip cleanup, and sslstrip --version subcommands replacing the old monolithic entry point. 5.0.0 · Aug 2026 · source · release history
  • Adds --ca-file for extra lab certificate authorities. 5.0.0 · Aug 2026 · source · release history

command line

example

  • Run a pre-flight check to verify the environment is correctly configured before launching a strip session. sslstrip doctor 5.0.0 · Aug 2026 · source
Gated traffic logging shipped Allows capturing unredacted HTTP traffic to a file during a session for post-analysis, controlled by explicit flags. 2 releases · 1 other source · first seen Aug 2026

release

  • Adds --traffic-log and --traffic-log-file flags for gated, unredacted traffic logging (both flags required to enable). 5.0.0 · Aug 2026 · source · release history
  • Adds gated unredacted traffic logs via --traffic-log plus --traffic-log-file. 5.0.0 · Aug 2026 · source · release history

example

  • Capture unredacted HTTP traffic to a file during a strip session — useful for post-session credential review in a lab. sslstrip run --traffic-log --traffic-log-file /tmp/strip-session.log 5.0.0 · Aug 2026 · source
Secure link store limits shipped Enforces TTL and LRU bounds on the store used to manage secure links during stripping sessions. 1 release · first seen Aug 2026

release

  • Adds TTL (30-minute) and LRU (10,000-entry) bounds on the secure-link store. 5.0.0 · Aug 2026 · source · release history
Structured error responses shipped Returns specific HTTP status codes for common proxy errors such as missing headers, protocol violations, and upstream failures. 1 release · first seen Aug 2026

release

  • Adds structured HTTP error responses: missing Host header → 400, CONNECT → 405, protocol upgrades → 426, upstream/DNS/TLS failures → 502, timeouts → 504. 5.0.0 · Aug 2026 · 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 sslstrip, 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 sslstrip 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

1 entry

  1. August 20261
    Show

    1 entry

    Project health

    Issue, contributor and maintainer activity in L1ghtn1ng/sslstrip, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 2 ±0 vs prior 12 months
    2. Maintainers 1 +1 joined · −1 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed not measured of issues opened, last 12 months
    5. Median time to close 2.2 years issues closed, last 12 months
    6. Open backlog 0 of 2 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 0
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 25
    Issue themes, last 12 months not measured

    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 →