Parse, check & extract
Clean up any proxy list, test which proxies are alive and how anonymous they are, and harvest new proxies from text — every option and every result field.
These three tools get you from a raw, unreliable list to a clean, tested set of proxies you can actually use.
Proxy lists arrive in every shape imaginable. Parse reads them and normalizes each entry into a consistent form so the rest of the workbench can work with them.
It understands every common way a single proxy can be written:
host:porthost:port:username:passwordusername:password@host:port- any of the above with an explicit scheme prefix —
http://,https://,socks4://,socks5://
You paste or load the list, one entry per line, and Parse hands back a clean set with the host, port, protocol (explicit or assumed), and any credentials pulled out separately — discarding lines it cannot make sense of rather than guessing.
Check is the workhorse. Give it a list of proxies and it dials each one through a judge endpoint and reports back a full picture of what it found.
What it tests:
| Field | What it tells you |
|---|---|
| Alive | Whether the proxy actually responds. |
| Protocol | Which protocol the proxy really speaks — not always what the list claimed. |
| Latency | How long the check took, in milliseconds. |
| Anonymity | Elite / Anonymous / Transparent / Unknown — how much the judge can tell about you through the proxy. |
| HTTP / HTTPS support | Whether the proxy carries plain and secure traffic. |
| Exit IP | The address a destination actually sees when you go through this proxy. |
| Geo | Country, region, city, postal code — where the exit address is. |
| Network type | Residential, mobile, datacenter, or unknown, with a confidence read. |
| ASN / ISP / organization | The network that owns the exit address. |
| Quality score / band | A single 0–100 read on how well-behaved the proxy is — see below. |
| Auth | Whether the proxy required credentials to use. |
How the quality score is built: every alive proxy starts at a base of 35 points, then:
- Anonymity: Elite
+30· Anonymous+20· Unknown+0· Transparent+8 - Supports HTTPS:
+15 - Latency: under 400ms →
+20· under 900ms →+12· under 1600ms →+6· slower →−8 - Presented credentials:
+4
The total is clamped to 0–100 and banded: High (≥80) · Medium (≥60) · Low (≥35) · Poor (below).
Results land in a sortable table. From there you filter down to the proxies worth keeping and save them to a pool or hand them to another tool.
Extract scans a blob of raw text — pasted, loaded from a file, or pulled from a Cloud source (a curated, licensed proxy source that comes with your ZeroTrace Proxy license; see Licensing) — and pulls out every proxy-shaped candidate it can find.
It looks for three patterns anywhere in the text:
scheme://host:port(with optional credentials)[ipv6]:porthost:port(with optional credentials)
Every candidate is validated through the same parser Parse uses, so nothing that isn't actually a well-formed proxy makes it into the result. Extract then de-duplicates by the normalized form of each entry — the same host and port under two different protocols are kept as two distinct entries, since they may behave differently — and returns them in the order they were first seen.