GOST is a proxy and tunneling tool that supports HTTP, SOCKS, forwarding chains, authentication, and a REST API. It is often deployed as infrastructure without a branded website, which makes a generic title search noisy.

ZoomEye count-only queries on November 22, 2026 observed 97,872 matches for app="GOST", 934 for title="GOST", and 21,314 for http.header="gost/3.0". The title count is likely affected by unrelated uses of the name. The proxy-agent header is a more specific lead because it describes a response generated by the proxying software.

Proxy visibility changes the risk model

A forward proxy can expose its listener to a broad network while the actual applications sit elsewhere. Authentication may be optional, based on a static user file, or dynamically managed through the Web API. A configuration that starts as a local development proxy can become an internet-facing egress path.

The official docs describe a proxy mode that can run without encryption or authentication. They also describe API authentication and dynamic authenticator configuration. Those statements define the review boundary: the presence of GOST does not say which mode is active.

Review the listener and the API

For each GOST deployment, record the listening protocols, bind addresses, forwarding chain, authentication provider, and API listener. Test whether the proxy accepts anonymous requests from an untrusted network, then test whether the management API is reachable from the same position. These are separate exposures.

Review upstream trust. A proxy that can reach internal networks or cloud metadata endpoints becomes a pathfinder if it accepts unauthenticated clients. Restrict destinations as well as clients. A valid login does not make an unrestricted forward proxy safe.

Check API tokens and their lifetime. If authentication is loaded from a file or external service, confirm that revoked users lose access and that the proxy does not keep an old authorization decision indefinitely. Rotate credentials after any suspected proxy exposure.

Measurement limits

The selected proxy-agent query used sub_type=all, page 1, pagesize 1. It returned 21,314 index matches. The application and title counts were 97,872 and 934. A header match is stronger evidence of a proxy response than a title match, but it still does not prove an open listener or a vulnerable build.

Use these counts to find candidate networks and compare them with egress inventories. Do not treat a public proxy count as a list of compromised systems. A proxy can be intentionally published for a business use, a lab, or a content distribution path.

References