Online proxy checker

When a collection job fails, rule out the proxy first. Paste a batch and see which ones work, how slow they are and which country and network they exit from.

$ kimi tools ip --probe socks5Developer tools
One per line, up to 10 per run
Protocol

Test results appear here

  • 01Protocol auto-detect

    Without a scheme, the checker tries a SOCKS5 handshake first and falls back to HTTP CONNECT.

  • 02Exit and ASN

    The exit IP is resolved to country, city and ASN so you can tell residential from data-center networks.

  • 03Actionable errors

    Timeouts, refusals, auth failures and tunnel failures are reported separately, separating network issues from account issues.

Workflow

From paste to result in three steps

  1. step_1

    Paste proxies

    Up to 10 per run, with socks5:// or http:// prefixes supported.

  2. step_2

    Choose a protocol

    Auto-detect, or force SOCKS5 or HTTP.

  3. step_3

    Read the results

    Review status and latency; failed rows show the reason.

How the check works

Our server opens a TCP connection to the proxy, completes the SOCKS5 or HTTP CONNECT handshake and authentication, then reaches a public IP echo service over TLS through the tunnel. The address the echo service sees is the proxy's exit IP, which is then resolved to location and network data by rotating IP databases.

IP location lookup

Switch to IP lookup to see your browser's public IP, or enter any IP or domain for country, region, city, timezone, ISP and ASN. Data comes from ipinfo, ipwho.is, ipapi.co, ip-api and FreeIPAPI, and you can pick a source to cross-check.

Frequently asked questions

The connection starts from the test server, so the result measures its route to your proxy. Check your computer’s firewall and client routing rules locally.