Proxy test

Test and validate proxies

Check where a proxy really exits, whether it matches the country, ASN and network type you expect, and whether a sticky session holds its IP.

Coming soon. The API contract below is final and already validates requests. Tests will run on isolated workers that never reach private networks. Until then you can check any exit IP with IP Lookup, or route curl -x through your proxy to https://ipcheckhq.com/ip.

Check a proxy today

Send a request through the proxy to the agent endpoint. What you get back describes the proxy’s exit.

Exit check

curl -x http://user:password@proxy.example.com:12345 "https://ipcheckhq.com/api/v1/me?format=agent"

Endpoints

POST /api/v1/proxy/test: Reachability, latency and exit IP, location, ASN, ISP and network type.
POST /api/v1/proxy/validate: Compares the exit with expected country, region, city, ASN, ISP or network type. Built for support agents.
POST /api/v1/proxy/session-test: Up to 20 requests to measure how many distinct exit IPs a sticky session produces.

Validation example

A customer says their US AT&T proxy is not working. The support agent validates it and sees the proxy connects in the right country, but on the wrong network, so it follows the “wrong ISP pool” procedure instead of the “connectivity” one.

Request

curl -X POST https://ipcheckhq.com/api/v1/proxy/validate \
  -H "Content-Type: application/json" \
  -d '{
    "proxy": { "protocol": "http", "host": "proxy.example.com", "port": 12345,
               "username": "user", "password": "password" },
    "expect": { "country": "US", "asn": 7018, "network_type": "residential" }
  }'

Response

{
  "success": true,
  "reachable": true,
  "exit": { "ip": "203.0.113.91", "country": "US", "asn": 174,
            "isp": "Cogent Communications", "network_type": "hosting" },
  "validation": {
    "country":      { "expected": "US",          "actual": "US",      "match": true  },
    "asn":          { "expected": 7018,          "actual": 174,       "match": false },
    "network_type": { "expected": "residential", "actual": "hosting", "match": false }
  }
}

Safety

Proxy passwords are never logged, stored or returned.
Destinations are fixed diagnostic endpoints; you cannot point tests at arbitrary URLs.
Proxy hosts that resolve to private, loopback, link-local, metadata or other internal addresses are refused, and the resolved address is pinned to prevent DNS rebinding.
Strict per-IP rate limits, timeouts and request caps apply.