Vexta's Intercepting Proxy and Repeater, Built Into the Scanner

An intercepting proxy for pentesting is a tool that sits between your browser or client and a target, so you can see, pause and replay a request before it ever reaches the server. Vexta is VITI Security's agentless, AI-augmented vulnerability scanner and pentest platform, and it ships a full HTTP/HTTPS intercepting proxy with a repeater built in, the same workflow shape bug hunters already know, alongside an always-on history of every request the scanner itself makes while it works.

How does Vexta's intercepting proxy work?

The proxy listens on a configurable port, 8082 by default, and performs full HTTP and HTTPS man-in-the-middle interception by minting a fresh TLS certificate per host, signed by a Vexta certificate authority that installs locally. That CA is auto-generated, and installing it in your browser is what lets HTTPS traffic decrypt cleanly for inspection instead of throwing certificate warnings.

Scope filtering keeps the proxy honest about what it touches: interception is restricted to the target hosts you configure, and any traffic outside that scope tunnels straight through unchanged. That means routing your browser through Vexta's proxy for a specific engagement does not turn every other site you visit into intercepted traffic.

What can you do with a request once it's intercepted?

A live exchange feed, delivered over a WebSocket, shows requests and responses passing through the proxy in real time, with channel-based subscriptions so the dashboard updates as traffic happens rather than on a refresh. A history buffer keeps the exchanges you've seen, 5,000 by default, so you can go back to something you noticed a few requests ago instead of losing it the moment it scrolls past.

From that history, request replay lets you resend a captured exchange, edited or as-is, without hand-crafting a new request from scratch. That single capability, replay a real request the target already accepted once, is most of what makes manual testing of a specific parameter or header fast instead of tedious.

It also means a request never has to be rebuilt from memory. A hunter who notices something odd about a header three requests back does not have to reconstruct it by hand; it is already sitting in the buffer, exactly as it was sent and received the first time.

The repeater: editing and resending a request

Opening an intercepted exchange in the repeater gives you a two-column editor: the request on one side with method, URL, headers and body all editable, and the response on the other, updated the moment you resend. Follow-redirects and skip-TLS-verification toggles handle the two most common friction points when a target's setup does not play nicely with a strict client.

This is the loop a hunter actually lives in when working a specific finding: capture a request, tweak one header or one parameter value, resend it, read the response, and repeat until the behavior confirms or rules out the theory. Having that loop built into the same tool that also ran the automated scan means you are not exporting requests to a second application to do the manual half of the work.

Every scan request gets the same treatment automatically

Separately from the manual proxy, every HTTP request Vexta's own scanner makes is captured automatically into an in-memory ring buffer, up to 10,000 entries with a 1 MB body cap each, with secret headers redacted and gzip or deflate bodies decoded transparently for display.

That history surfaces as a sortable, filterable table, the same shape as the manual proxy's history, where clicking a row opens the exchange directly in the repeater. Programmatic access is available too, through endpoints to list the history, fetch a single entry, resend one through the repeater, or clear the buffer. In practice this means you never have to wonder what exact request produced a given finding; it is sitting in history, ready to open and re-run.

For a hunter reviewing a scan's output, that pairing matters more than it looks. A finding on its own is a claim; the finding plus the exact request that triggered it, one click away in the repeater, is something you can verify or hand to a client without reconstructing anything from a log line.

Where this sits in Vexta's plans

The full intercepting proxy is a Pro-tier capability, bundled with the complete proof-of-exploitation engine, PoC generation and one-click export to HackerOne and Bugcrowd. See the plans on the pricing page for exactly what each tier includes.

Key takeaways

The essentials on Vexta's intercepting proxy and repeater: