sslstrip
5.0.0 open-sourceThe section your link pointed to isn't on sslstrip's page any more, so we've brought you to the top.
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.
sslstrip doctor sslstrip run --traffic-log --traffic-log-file /tmp/strip-session.log sslstrip run --ca-file /etc/lab/ca-bundle.pem
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
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 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 → 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 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…
Releases
1 entry
No entries match these filters.
- August 20261
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.
- Contributors 2 ±0 vs prior 12 months
- Maintainers 1 +1 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close 2.2 years issues closed, last 12 months
- Open backlog 0 of 2 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 0
- Contributors / month 0
- Commits / month 0
- Stars 25
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.