IP Tools
My IP中文
Local test ready · production pending

Proxy Checker

Create one bounded network job and inspect only validated worker evidence.

Method:
Same-origin API → isolated network worker; explicit create, refresh and cancel only
Status:
idle

Input

Result

Ready

No job has been created. Complete the bounded form to begin.

One target and one bounded operation per job. No URL fetch, port range, custom resolver or browser-side probe is available.

Tool guide

Clear input, result, and evidence boundaries

Connect through one HTTP, HTTPS, or SOCKS5 proxy and verify whether it can forward to the fixed echo target.

01

Input and method

One protocol, public host, port, and optional credentials used only in memory for this run.

02

Reading the result

Resolution, connection, authentication, forwarding, latency, and observed exit IP stages remain separate.

03

Boundary and privacy

The worker is restricted to one public proxy and a fixed echo target; credentials are never echoed or persisted, and this is not an open proxy service.

FAQ

Frequently asked questions

What does Proxy Checker check?

Connect through one HTTP, HTTPS, or SOCKS5 proxy and verify whether it can forward to the fixed echo target.

What input does Proxy Checker accept?

One protocol, public host, port, and optional credentials used only in memory for this run.

How should I interpret Proxy Checker results?

Resolution, connection, authentication, forwarding, latency, and observed exit IP stages remain separate.

What can Proxy Checker not prove?

The worker is restricted to one public proxy and a fixed echo target; credentials are never echoed or persisted, and this is not an open proxy service.

How does Proxy Checker handle input and results?

Input is used only for this explicit check. The worker is restricted to one public proxy and a fixed echo target; credentials are never echoed or persisted, and this is not an open proxy service.

When should I run Proxy Checker again?

Run it again after the relevant network, address, browser environment, or target changes. Resolution, connection, authentication, forwarding, latency, and observed exit IP stages remain separate.

Continue checking
Egress IP CheckAvailable

Verify the public exit IP presented by a browser, server, container, cloud function, or CLI request.

Open tool
Port CheckerLocal test ready · production pending

Check whether one public TCP port can be reached from the selected probe region.

Open tool
Ping TestLocal test ready · production pending

Measure latency, packet loss, and individual replies to one public target from a clearly identified probe.

Open tool