# Proxy Checker & Anonymity Tester (`devyjones/apify-proxy-checker`) Actor

Bulk-check HTTP, HTTPS, SOCKS4 & SOCKS5 proxies: alive, latency, exit IP, country/city and anonymity level (elite/anonymous/transparent). Paste a list or point it at a URL.

- **URL**: https://apify.com/devyjones/apify-proxy-checker.md
- **Developed by:** [Anton](https://apify.com/devyjones) (community)
- **Categories:** Automation, Other, Developer tools
- **Stats:** 4 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Proxy Checker & Anonymity Tester

Bulk-check a list of **HTTP, HTTPS, SOCKS4 and SOCKS5 proxies** and get, for each one:

- ✅ **alive / dead** and **latency** (ms)
- 🌐 **exit IP** and **country / city**
- 🕵️ **anonymity level** — `elite` (nothing leaked), `anonymous` (proxy headers present, your IP hidden) or `transparent` (leaks your real IP)
- 🔌 **protocol**

Paste a list, or point it at a URL of proxies — the actor checks them concurrently and writes a clean, exportable table (JSON, CSV, Excel).

### Why

Free and scraped proxy lists rot fast — most are dead, slow, or transparent (they leak your real IP, which defeats the point). This actor tells you in seconds which ones actually work and how anonymous they are, so you don't waste a scrape on a dead pool.

### Input

| Field | Description |
|---|---|
| `proxies` | List of proxies, one per line. `host:port`, `host:port:user:pass`, or `scheme://user:pass@host:port`. Scheme defaults to `http`; use `socks5://…` for SOCKS. |
| `proxyListUrl` | …or fetch the list from a URL (a raw `.txt`, one proxy per line). |
| `testUrl` | URL fetched through each proxy (default `https://httpbin.org/get`, which echoes IP + headers). |
| `timeout` | Per-proxy timeout in seconds (default 10). |
| `concurrency` | Proxies checked in parallel (default 50). |
| `checkGeo` | Look up country/city of each live proxy (default on). |
| `keepDead` | Keep dead proxies in the output (default on). |

### Output

One dataset row per proxy:

```json
{
  "proxy": "103.155.167.82:8082",
  "alive": true,
  "latency_ms": 2919,
  "exit_ip": "103.155.167.82",
  "country": "ID",
  "city": "Jakarta",
  "anonymity": "elite",
  "protocol": "http"
}
```

### Tip: need proxies that don't rot?

Checking a free list usually shows most of it is already dead. If you're tired of babysitting free proxies, get reliable **rotating, residential, datacenter and mobile proxies** (HTTP/SOCKS5, per-GB or unlimited) from **[GProxy](https://gproxy.net/?utm_source=apify\&utm_medium=actor\&utm_campaign=proxy-checker)** — and feed them back into this actor to verify.

You can also point `proxyListUrl` at a free list to test it, e.g. GProxy's open, auto-updated one:
`https://raw.githubusercontent.com/gproxynet/free-proxy-list/main/http.txt`

### Notes

- Anonymity is judged from the headers/IP the `testUrl` echoes back; keep the default httpbin-style endpoint for accurate results.
- SOCKS checks require the actor's built-in SOCKS support (included) — no extra setup.

# Actor input Schema

## `proxies` (type: `array`):

Proxies to check, one per line. Formats: host:port, host:port:user:pass, scheme://user:pass@host:port. Scheme defaults to http; use socks5://… for SOCKS.

## `proxyListUrl` (type: `string`):

Fetch the list from a URL instead (one proxy per line). Example: a raw .txt of proxies.

## `testUrl` (type: `string`):

URL fetched through each proxy. Must echo the caller IP + headers (default httpbin).

## `timeout` (type: `integer`):

Per-proxy request timeout.

## `concurrency` (type: `integer`):

How many proxies to check in parallel.

## `checkGeo` (type: `boolean`):

Look up geolocation of each working proxy's exit IP (one extra request per live proxy).

## `keepDead` (type: `boolean`):

If off, only working proxies are written to the dataset.

## Actor input object example

```json
{
  "proxies": [
    "1.2.3.4:8080",
    "socks5://5.6.7.8:1080"
  ],
  "testUrl": "https://httpbin.org/get",
  "timeout": 10,
  "concurrency": 50,
  "checkGeo": true,
  "keepDead": true
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "proxies": [
        "1.2.3.4:8080",
        "socks5://5.6.7.8:1080"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("devyjones/apify-proxy-checker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "proxies": [
        "1.2.3.4:8080",
        "socks5://5.6.7.8:1080",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("devyjones/apify-proxy-checker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "proxies": [
    "1.2.3.4:8080",
    "socks5://5.6.7.8:1080"
  ]
}' |
apify call devyjones/apify-proxy-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=devyjones/apify-proxy-checker",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/HL35aRMZc3bUu348e/builds/9o2deYah2YhCC1dcT/openapi.json