Skip to content
Language: EN
EnglishالعربيةРусский中文Tiếng Việt
Start trialDashboard
Start trial
Free proxy tool No signup

Free proxy checker

Check connectivity, response time and exit location for up to 1,000 proxy endpoints. Paste your list, choose a protocol and target, then review the results as they arrive.

Up to 1,000 endpoints 8 seconds per request attempt HTTP · HTTPS · SOCKS5/H How results are measured

One endpoint per line. Credentials are masked in results.

0/1,000
See accepted formats

Complete the human verification before starting the check.

Format for your browser

Paste one proxy in the list above. Formatting happens on your device. Copied output includes credentials; keep it private. Check proxies uses the existing checker.

Credentials are used for your check and masked in results. Exports and shared summaries omit them. How your data is handled

Check results

Status, diagnostics, cold response time, exit IP, and location appear here.

Your results will appear here

Add your proxy list, choose a protocol and target, then select Check proxies.

Useful signals

The quick check before the real job

A clean result helps you remove dead endpoints and confirm basic routing before you put a proxy into a browser, scraper, or automation workflow.

Check a list at once

Paste or import up to 1,000 endpoints and reconnect to the same queued job after refreshing when session storage is available.

Measure the real route

See whether the request completes and how long the proxy takes to return an exit IP.

Verify the exit

Review the observed public IP, city, country, and network when location data is available.

Keep secrets out of results

Credentials are masked on screen and used only for the check you request.

Four steps

From pasted list to usable shortlist

  1. 1

    Paste your list

    Add one proxy per line or import a plain-text file.

  2. 2

    Choose a transport

    Use bounded Auto mode or explicit HTTP, HTTPS, SOCKS5, or SOCKS5H.

  3. 3

    Run the check

    Review connectivity, cold response time, exit evidence, and optional target headers.

  4. 4

    Use the result

    Copy original working lines or download credential-free CSV or JSON.

Accepted formats

Bring public or authenticated proxies

Domains, IPv4 addresses, and bracketed IPv6 endpoints are supported. Add one endpoint per line.

proxy.example.com:8000
proxy.example.com:8000:user:pass
https://user:pass@proxy.example.com:8443
socks5://user:pass@proxy.example.com:1080
socks5h://user:pass@proxy.example.com:1080

Read results correctly

A working proxy is a starting point

Working means the proxy completed this tool's HTTPS request and returned a public exit IP.

Cold response time covers one small checker-server request after proxy-host DNS resolution. It is not throughput or a prediction of your device's speed.

Location comes from third-party IP geolocation and can be approximate or temporarily unavailable.

Target not accepted means the selected lightweight request returned 4xx or 5xx. It does not prove the exit is banned everywhere.

Target compatibility still needs a direct test against the exact site, URL, account, and client you plan to use.

Convert proxy formats for anti-detect browsers

Paste one endpoint in the checker and choose your browser to copy its documented text formats. Build a Traffic pack username with country, subdivision, city, ASN and session options, or generate up to 200 separate session IDs. MoreLogin lists split at 100 lines and Multilogin lists at 25.

Formatting stays on your device. Checking sends your list through the existing checker. Session IDs request best-effort sessions; different IDs can still return the same exit IP. A supported text layout does not establish IPv6, TLS or bulk-import support in every browser plan.

Browser setup guides and proxy support

Versioned methodology

What the checker measures—and where the evidence stops

The checker resolves a public proxy endpoint, sends a small HTTPS exit-IP request through it, optionally enriches the observed exit with GeoJS, and—when selected—records the first response headers from Google or Wikipedia through a separate proxied request.

Method 2026.07.18

Reviewed

Maintained by TrueProxies Engineering

  1. 1

    Validate and resolve the proxy

    The parser accepts only supported formats and public endpoints. Private, reserved, mixed public/private DNS answers, invalid ports, and malformed credentials fail before any target request.

  2. 2

    Observe one public exit

    A fixed HTTPS request to IPify must return a valid public IP. Cold end-to-end response time starts after proxy-host DNS resolution and ends after the small response body is received and validated.

  3. 3

    Add optional location evidence

    GeoJS receives the observed exit IP directly from the checker for best-effort country, city, and network enrichment. Missing location data does not erase a successful exit observation.

  4. 4

    Check one optional target

    Google or Wikipedia is requested separately through the selected transport. Timing stops when initial response headers arrive; bodies are not downloaded and redirects are not followed.

Interpretation boundaries

  • The 8-second boundary applies to each proxied network request attempt, not an entire endpoint or batch.
  • Exit response time is not bandwidth, throughput, ping, queue time, browser latency, or sustained performance.
  • A 2xx or 3xx initial target response is accepted for this observation. A 4xx or 5xx response is “target not accepted,” not proof of an IP ban.
  • Exit observation and target reachability use separate requests; a rotating endpoint can use different exits for them.
  • SOCKS coverage is TCP-only. The checker does not test UDP, anonymity, headers, reputation, browser fingerprints, stickiness, or universal target access.

Machine-readable method contract

The JSON contract records transports, providers, timing boundaries, accepted target statuses, data handling, error codes, and limitations from the same version shown here.

Open methodology JSON

Stable citation

Cite the checker method

Canonical URL
https://trueproxies.com/tools/proxy-checker/
Method version
2026.07.18
Last reviewed

Suggested citation

TrueProxies Proxy Checker. Method 2026.07.18. Reviewed July 18, 2026. Server-side point-in-time proxy connectivity and cold response-time diagnostic. https://trueproxies.com/tools/proxy-checker/

This citation identifies the maintained method and canonical tool. It is not a throughput result, controlled benchmark, provider ranking, independent audit, or claim about future availability.

Review the machine-readable methodology

Focused proxy diagnostics

Proxy Checker Error Codes

Start with the exact error code, selected transport, selected target, and a credential-free endpoint label. Format and private-address failures happen before a proxied request. DNS, authentication, connection, TLS, timeout, and response failures happen at different network stages. A target response outside the accepted range means that one lightweight request was not accepted; it does not prove the exit IP is universally blocked.

Read guide

Proxy Latency vs Speed

Exit response time begins immediately before the checker opens the proxied request and ends after the small IPify JSON body is received and validated. Target response time ends when the selected target's response headers arrive; the target body is not downloaded. Proxy-host DNS resolution, queue time, GeoJS enrichment, rendering, and download throughput are outside those timers. Compare repeated results from the same runner and target, then report a median and sample count instead of calling one low value the fastest proxy.

Read guide

HTTP, HTTPS & SOCKS5 Testing

Use http:// for a plain HTTP proxy transport that tunnels HTTPS targets with CONNECT. Use https:// when the connection from the checker to the proxy itself must be protected by TLS with hostname verification and SNI. Use socks5:// for SOCKS5 TCP with checker-side target DNS, or socks5h:// for SOCKS5 TCP with proxy-side target DNS. Auto makes only bounded HTTP/SOCKS5 attempts and never silently upgrades to HTTPS or changes to SOCKS5H. The checker does not test UDP ASSOCIATE.

Read guide

Proxy Target Reachability

The checker first requests IPify through the proxy and validates the public exit IP. If Google or Wikipedia is selected, it then starts a second proxied HTTPS request and stops timing when the first response headers arrive; it does not download the target body. A 2xx or 3xx response is reported as accepted. A 4xx or 5xx response is reported as not accepted with its HTTP status. Neither result proves universal access, a destination-wide block, browser compatibility, or anonymity.

Read guide

Privacy and data handling

Which services receive data during a check

The route depends on the selected transport and target. These are the services involved and the bounded purpose for each.

1

Browser and Turnstile

Your browser sends the proxy line, selected protocol and target, and a Turnstile token to TrueProxies over HTTPS. Cloudflare processes the verification challenge.

2

Isolated checker

Queues submitted lines in expiring process memory, deletes each raw line after processing or cancellation, and keeps credentials out of results, exports, analytics, shares, and logs.

3

Proxy endpoint

Receives its own connection credentials and carries the HTTPS requests to the selected test endpoints.

4

Test providers

IPify observes the proxy-routed exit request. GeoJS receives the exit IP directly for location lookup. Google or Wikipedia receives a proxied request only when selected.

The private job capability stays in page memory and, when session storage is available, is stored there so this tab can reconnect after a refresh; it contains no submitted proxy lines. Rate limiting uses a pseudonymous hash of the client IP. CSV and JSON exports are generated locally without credentials or exit metadata. “Copy working” deliberately reproduces the original working lines and can include the credentials you pasted.

FAQ

Proxy checker questions

What does this proxy checker test?

It sends a small HTTPS request through each endpoint and reports whether the route completed, which transport worked, cold end-to-end response time, the observed public exit IP, optional location data, and one optional target response.

Which proxy formats are supported?

Use host:port, host:port:username:password, username:password@host:port, or an explicit http://, https://, socks5://, or socks5h:// URL. Put one endpoint on each line.

Are my proxy credentials saved?

Credentials travel over HTTPS to an isolated TrueProxies checker service and remain only in its expiring in-memory queue. Each raw line is deleted after processing or cancellation. Credentials are excluded from results, shares, analytics, logs, and CSV/JSON exports.

Why can a connected proxy still fail on my target website?

Connectivity proves that one server-side request returned a public exit IP. A target can return another status or behave differently for browsers, accounts, URLs, regions, TLS fingerprints, cookies, or later requests.

Does a successful result prove anonymity or speed?

No. It confirms point-in-time server-side connectivity and reports cold response time for a small request. It does not measure throughput, anonymity, browser leaks, reputation, or future availability.

Go one layer deeper

Check what your browser can still expose

After confirming the proxy works, compare browser-visible IPv4, IPv6, WebRTC, and DNS signals with the IP Leak Test.

Checking an ad campaign? Preflight the exit here, then verify ads from a residential IP with the evidence templates.

Run IP Leak Test View proxy plans

More free tools

See all tools