Tutorials
Benchmark and Leak Test
Measure proxy stability and then filter out candidates with leak signals.
This workflow turns a checked pool into a higher-confidence pool.
1. Benchmark the Pool
- Open Core Tools -> Benchmark Proxies.
- Select Pool input.
- Choose your checked pool.
- Set task name to
Docs benchmark demo. - Set Rounds to
3. - Keep HTTPS check enabled.
- Keep Protocol hint on Auto.
- Start the task.
2. Pick Benchmark Winners
Filter or select rows using:
| Signal | Recommended target |
|---|---|
| Success rate | Prefer 100% for stable pools. |
| Pass count | Must be greater than zero. |
| Average latency | Lower is better for interactive use. |
| Worst latency | Avoid extreme spikes. |
| HTTPS support | Prefer supported. |
3. Send Winners To Leak Test
- Select benchmark winners.
- Use handoff to Test Proxy Leaks.
- Use selected or visible rows depending on your filters.
- Keep the default inspectable target unless you operate your own compatible target.
- Start the leak test.
4. Interpret Leak Results
| Result | Action |
|---|---|
| No leak signals | Good candidate for final pool. |
| Via/Forwarded/X-Forwarded-For | Treat as transparent or lower trust. |
| Proxy-Authorization | Remove from sensitive workflows. |
| Origin mismatch | Inspect with Proxy Viewer before trusting. |
5. Save Final Pool
Create a new pool named Benchmark leak clean and tag entries:
benchmarkedleak-cleanhttps- country or source tags if useful
This pool is a stronger input for the Rotation Engine than a raw scrape or single checker run.