Skip to content

elsi-ernier/proxy-test

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

1 Commit
Β 
Β 

Repository files navigation

Proxy Test Scraper

This tool evaluates how different proxies perform when accessing a predefined set of URLs. It measures response behavior using either HTTP requests or a full browser environment. The scraper helps developers benchmark proxies, identify failures, and validate routing performance with clear, structured outputs.

Bitbash Banner

Telegram Β  WhatsApp Β  Gmail Β  Website

Created by Bitbash, built to showcase our approach to Scraping and Automation!
If you are looking for Proxy Test you've just found your team β€” Let’s Chat. πŸ‘†πŸ‘†

Introduction

The Proxy Test Scraper runs connectivity tests across multiple proxy URLs or proxy groups. It returns detailed results, including optional screenshots when browser mode is selected. This project is ideal for developers, QA teams, and automation engineers who need to confirm whether their proxies are behaving correctly and reliably.

How Proxy Testing Works

  • Executes requests through selected proxy endpoints for each provided URL.
  • Supports two modes: lightweight HTTP requests or full Chromium browser tests.
  • Produces structured output, including success status, timing metrics, and optional screenshots.
  • Stores final results in a consistent output format for further analysis.

Features

Feature Description
Multi-URL Testing Validate any number of URLs through different proxy endpoints.
HTTP or Browser Mode Choose between fast HTTP testing or full-page rendering in Chromium.
Screenshot Capture Browser mode includes visual snapshots for debugging blocked or failed pages.
Live Result Preview View interim results instantly during test execution.
Structured Output Storage Final aggregated results are saved for easy retrieval and processing.

What Data This Scraper Extracts

Field Name Field Description
url The target URL being tested.
proxy The proxy endpoint or group used for the request.
status Connection status or HTTP response code.
loadTime Time taken to load the page or complete the request.
screenshotUrl Link to the saved screenshot (browser mode only).
error Error message when a request fails.

Example Output

[
  {
    "url": "https://example.com",
    "proxy": "proxy1.example:8000",
    "status": 200,
    "loadTime": 1420,
    "screenshotUrl": "key-value-store://OUTPUT/screenshot-1.png",
    "error": null
  }
]

Directory Structure Tree

Proxy Test/
β”œβ”€β”€ src/
β”‚   β”œβ”€β”€ runner.js
β”‚   β”œβ”€β”€ modes/
β”‚   β”‚   β”œβ”€β”€ httpTester.js
β”‚   β”‚   └── browserTester.js
β”‚   β”œβ”€β”€ utils/
β”‚   β”‚   β”œβ”€β”€ proxyManager.js
β”‚   β”‚   └── resultFormatter.js
β”‚   β”œβ”€β”€ outputs/
β”‚   β”‚   └── reporter.js
β”‚   └── config/
β”‚       └── settings.example.json
β”œβ”€β”€ data/
β”‚   β”œβ”€β”€ urls.sample.txt
β”‚   └── proxies.sample.txt
β”œβ”€β”€ requirements.txt
└── README.md

Use Cases

  • Network engineers test routing reliability across large proxy lists to ensure stable request performance.
  • Automation developers verify proxy pools before running high-volume scraping or bot workflows.
  • QA teams confirm that regional proxies correctly access geo-restricted URLs.
  • Security teams validate anonymity layers by checking how different endpoints load sensitive or high-risk pages.

FAQs

Q: Can this scraper handle large proxy lists? Yes, it processes lists of any size, and results stream progressively so you can monitor tests in real time.

Q: When should I use browser mode instead of HTTP mode? Browser mode is ideal when you need to detect JavaScript-dependent blocks, visual errors, or CAPTCHAs that plain HTTP cannot capture.

Q: Does it support mixed proxy types? You may combine datacenter, residential, or rotating proxies as long as they accept standard authentication formats.

Q: What happens if a proxy fails during testing? Failures are logged with the associated error message, and testing continues for the remaining proxy/URL combinations.


Performance Benchmarks and Results

Primary Metric: Average test time per URL–proxy pair typically ranges from 300–1500 ms in HTTP mode and 1.5–3.0 seconds in browser mode, depending on proxy quality.

Reliability Metric: Successful completion rate reaches 97%+ with stable proxies; unstable or rotating endpoints may show 10–25% variance.

Efficiency Metric: Lightweight mode can process hundreds of combinations per minute with minimal resource usage.

Quality Metric: Browser screenshots and structured logs ensure high diagnostic precision, making it easy to pinpoint failures or regional restrictions.

Book a Call Watch on YouTube

Review 1

"Bitbash is a top-tier automation partner, innovative, reliable, and dedicated to delivering real results every time."

Nathan Pennington
Marketer
β˜…β˜…β˜…β˜…β˜…

Review 2

"Bitbash delivers outstanding quality, speed, and professionalism, truly a team you can rely on."

Eliza
SEO Affiliate Expert
β˜…β˜…β˜…β˜…β˜…

Review 3

"Exceptional results, clear communication, and flawless delivery.
Bitbash nailed it."

Syed
Digital Strategist
β˜…β˜…β˜…β˜…β˜…

Releases

No releases published

Packages

No packages published