PAGES
← all tools
◆ Web Application Security

proxify

v0.0.16 open-source

Proxify is a proxy tool that intercepts, dumps, filters, and manipulates HTTP/HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. and non-HTTP traffic, with upstream HTTP/SOCKS5SOCKS5A proxy protocol that relays TCP and UDP traffic through an intermediary server without inspecting it, letting cyber tools tunnel connections through firewalls or pivot hosts with minimal overhead. proxy support.

Summary

Proxify is an open-source MIT-licensed HTTP/HTTPS proxy that intercepts, filters, and manipulates traffic, including non-HTTP protocols via plugins for things like XMPP, 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., FTP, and SSH. It runs as a command-line tool, deployed standalone or pointed at from another proxy, with a DSL for matching and rewriting requests in flight, TLS MITM with client/server certificates, full traffic dumps to jsonl or yaml, and a native embedded DNS server. It suits penetration testers and application security engineers who need a scriptable interception layer rather than a full manual testing client; its own README describes replaying captured traffic into Burp Suite by setting proxify as the upstream proxy, so it complements rather than replaces that workflow. First committed in 2020, it has drawn 30 contributors and 28 commits over the past year, though its last release was 357 days ago.

Proxify is a proxy tool that intercepts, dumps, filters, and manipulates HTTP/HTTPS and non-HTTP traffic, with upstream HTTP/SOCKS5 proxy support.

How proxify helps

Which requests and responses actually crossed the wire during this test run?

dumps full traffic to jsonl or yaml, including request bodies alongside headers, so a POST or PUT payload can be checked after the fact rather than reconstructed from memory

Which requests match a pattern I care about, and can I change them before they go out?

evaluates each request/response against a DSL expression and rewrites matching traffic in flight, so filtering and manipulation happen without a manual replay step

Can I point my thick client or CLI tool at this and still see its traffic?

runs as a standalone MITM proxy with client/server TLS certificates and an embedded DNS server, so invisible clients that don't support manual proxy configuration still get intercepted

How do I get this captured traffic into Burp for manual follow-up?

sets itself as the upstream proxy for a replay pass, resending dumped requests with their original domain names so Burp receives them as if seen live

What non-HTTP protocols can I still inspect without writing a parser?

ships plugins that decode specific protocols such as XMPP, SMTP, FTP, and SSH, exposing them in the same traffic dump rather than raw bytes

Can I chain this in front of another proxy I'm already using?

accepts an upstream HTTP or SOCKS5 proxy, so traffic can be forwarded onward after filtering instead of terminating there

all 7 features, with the evidence for each →

Languages

Not documented

Features

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

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

  • Command-line interface2
  • JSON data export1
All capabilities 7 capabilities
HTTP traffic logging verified Captures and stores raw HTTP requests and responses to an output directory, with configurable output format (JSONL or YAML). 9 releases · 6 other sources · first seen Nov 2021

Also counts toward: JSON data export

release 9 total

  • Adds request body logging so intercepted POST/PUT payloads are captured alongside headers in proxify output. v0.0.16 · Aug 2025 · source · release history
  • Adds support for TLSv1.0 in proxy connections v0.0.13 · Feb 2024 · source · release history
  • Adds PROXIFY_EXPORT_FORMAT environment variable to control the export output format (default: jsonl) v0.0.13 · Feb 2024 · source · release history
  • -j, -jsonl support allows writing proxify output in JSON Lines (JSONL) format v0.0.10 · Jul 2023 · source · release history
  • Adds a configurable max request/response size limit for Elastic export v0.0.9 · Mar 2023 · source · release history
  • Allows configuring multiple match / replace DSL rules in one profile v0.0.9 · Mar 2023 · source · release history

command line

  • -store-response — store raw http request / response to output directory (default proxify_logs) v0.0.16 · Aug 2025 · command-line history
  • -store-resposne — store raw http request / response to output directory (default proxify_logs) v0.0.15 · Mar 2024 · command-line history
  • -output-format — output format (jsonl/yaml) (default "jsonl") v0.0.15 · Mar 2024 · command-line history

example

  • Export proxify logs as a MultiDoc YAML file for structured parsing. proxify -of yaml -o output.yaml v0.0.15 · Mar 2024 · source
  • Pipe proxify's traffic capture into a downstream log aggregator that expects JSONL. proxify -jsonl v0.0.10 · Jul 2023 · source
  • Enable verbose logging to debug proxy behavior or inspect DSL validation messages. proxify -vv v0.0.8 · Oct 2022 · source
Self-updating capability shipped Allows the cyber tool to update itself to the latest version directly from the command line. 2 releases · 1 other source · first seen May 2021

Also counts toward: Command-line interface

release

  • Adds the -update flag to enable self-updating within the CLI tool v0.0.9 · Mar 2023 · source · release history
  • Adds Match/Replace DSL support with onrequest and onresponse callbacks v0.0.4 · May 2021 · source · release history

example

  • Update the cyber tool to the latest version directly from the command line without manual download. proxify -update v0.0.9 · Mar 2023 · source
Custom configuration directory support shipped Allows locating configuration files in a user-specified directory rather than the default XDG path. 1 release · 1 other source · first seen Aug 2023

Also counts toward: Command-line interface

release

  • -config-directory string overrides the default config path (previously $HOME/.config/proxify) v0.0.12 · Aug 2023 · source · release history

example

  • Run proxify with configuration files located in a custom directory instead of the default XDG path. proxify -config-directory /path/to/custom/config v0.0.12 · Aug 2023 · source
Swagger specs-based API generation shipped Generates API specifications based on Swagger definitions. 2 releases · first seen May 2021

release

  • Adds swagger specs-based API generation capability v0.0.9 · Mar 2023 · source · release history
  • Adds allow and deny flags to list hosts/cidrs to exclude/include from proxy v0.0.4 · May 2021 · source · release history
Request/Response dumping shipped Allows selective dumping of only request or response traffic via specific flags. 1 release · first seen May 2021

release

  • Adds dump-req and dump-resp flags to dump only request or response traffic v0.0.4 · May 2021 · source · release history
Socket-level proxy with TLS inspection shipped Provides a socket-level proxy that inspects TLS traffic and exposes an external socket for HTTP support. 1 release · first seen May 2021

release

  • Adds socket level proxy with TLS inspection & external socket to http support v0.0.4 · May 2021 · source · release history
Upstream certificate validation skipping shipped Allows the cyber tool to skip certificate validation for upstream proxies. 1 release · first seen May 2021

release

  • Adds support to skip certificate validation for upstream proxy v0.0.4 · May 2021 · 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 proxify, 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 proxify 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 →

Commercials

pricing & packaging history · ProjectDiscovery vendor page

23 readings of ProjectDiscovery's pricing page since Feb 2024, with 7 relaunches of its plan lineup and 4 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.

Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.

See plans →

Website history

projectdiscovery.io, every change

ProjectDiscovery's home page and 3 more pages as they looked each month from August 2021 to October 2026: 18 renders, 4 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Releases

10 entries

  1. August 20251
  2. March 20241
  3. February 20241
  4. August 20231
  5. July 20231
  6. March 20231
  7. October 20221
  8. June 20221
  9. November 20211
  10. May 20211

    10 entries

    Project health

    Issue, contributor and maintainer activity in projectdiscovery/proxify, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 0 −5 vs prior 12 months
    2. Maintainers 0 +0 joined · −1 left, last 12 months
    3. Bus factor 0 committers behind half the commits
    4. Community-filed 14% of issues opened, last 12 months
    5. Median time to close 1.1 days first maintainer reply 27 hours
    6. Open backlog 1 of 114 issues ever filed
    1. Issues opened / month 0 · 5 communitymaintainers
    2. Open backlog 1
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 3,073
    Issue themes, last 12 months
    • bugs 43%
    • features 14%
    • other 43%

    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 →