goldeneye
open-sourceThe section your link pointed to isn't on goldeneye's page any more, so we've brought you to the top.
GoldenEye Layer 7 (KeepAlive+NoCache) DoS Test Tool - jseidl/GoldenEye
Summary
goldeneye is an open-source command-line tool, licensed under GPLv3, that generates HTTP-layer denial-of-service load against a target URL by exploiting HTTP Keep Alive and NoCache to hold connections open. It runs as a Python 3 script with worker and socket counts, HTTP method, user-agent list and SSLSSLA cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination.-check options set as flags, which makes it a stress-testing utility for penetration testers and red teamers checking whether a web server or application survives a layer-7 flood rather than a network-layer one. The README itself states the project is no longer maintained, and our records confirm that: first committed in 2012, seven contributors, one tracked release, and no commits in the past year, so treat it as a fixed historical tool rather than an actively developed one.
GoldenEye Layer 7 (KeepAlive+NoCache) DoS Test Tool - jseidl/GoldenEye
How goldeneye helps
Does a target web server stay responsive under a sustained layer-7 connection flood?
opens many concurrent HTTP connections against the URL and holds them open using Keep Alive and NoCache so the server must keep resources allocated, revealing whether it degrades or falls over under load rather than a raw bandwidth flood
Can a target be overwhelmed using ordinary-looking GET or POST traffic instead of malformed packets?
issues real GET, POST, or randomly-chosen HTTP requests through many workers and sockets, so the load looks like legitimate application traffic rather than a network-layer attack
Would varying client fingerprints slip past request filtering aimed at a single user-agent or referer?
draws from a supplied or randomly generated user-agent list so each connection presents a different client identity, showing whether simple user-agent-based filtering would catch or miss the flood
Can an HTTPS endpoint be load-tested without a valid or trusted certificate getting in the way?
offers a flag-free description in practice: an SSL-check option lets connections proceed against a target whose certificate would otherwise block the test, so certificate issues do not stop the assessment
How much concurrent load is actually needed to strain a given server?
exposes the worker and socket counts driving the flood, so a tester can raise or lower concurrency and observe at what level the target's response time or availability starts to suffer
Languages
Command line
| 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.
Release-note detail over time
See how much detail goldeneye 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
Nothing shipped since we started watching. Releases and docs updates land here as they happen.
Project health
Issue, contributor and maintainer activity in jseidl/GoldenEye, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 0 ±0 vs prior 12 months
- Maintainers 0 +0 joined · −0 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog not measured open issues today
- Issues opened / month not measured
- Open backlog not measured
- Contributors / month 0
- Commits / month 0
- Stars 1,471
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.
Choose a badge style and copy the code →