Use this free proxy checker to test up to 10 HTTP, HTTPS, SOCKS4, or SOCKS5 proxies. Check proxy connectivity, latency, exit IP, location, anonymity signals, and whether each proxy can complete a real HTTPS request.
Check proxy availability in bulk
Check 1–10 endpoints. Credentials are sent only to the checker and never stored in history or exports.
How to use
Check proxies in four steps
No installation or account is required. Paste a proxy list to check connectivity, latency, exit IP, and anonymity.
01
Paste proxy endpoints
Enter one proxy per line. host:port, host:port:username:password, and proxy URLs with a protocol are supported, up to 10 at once.
02
Choose protocol and timeout
Use Auto when the protocol is unknown, or select HTTP, HTTPS, SOCKS4, or SOCKS5 and set a timeout for your network conditions.
03
Run the check
Select “Check proxies.” MiyaIP asks each proxy to complete a fixed HTTPS request, testing real availability rather than only whether its port opens.
04
Review and export results
Review status, latency, exit IP, location, and anonymity together. Export live proxies as CSV or save the full result as JSON.
Supported input formats
Paste proxies without reformatting
IP and hostname endpoints are accepted, including authenticated proxies and URLs with a protocol prefix. Separate entries with a new line, space, comma, or semicolon.
1.2.3.4:8080Proxy without authentication
1.2.3.4:8080:user:passwordUsername and password authentication
socks5://user:password@proxy.example.com:1080Proxy URL with protocol
Credentials are used only for the current check and stay hidden in displayed, copied, saved, and exported results.
Reading results
What each result tells you
Status
Shows whether the proxy is live, dead, timed out, or blocked.
Protocol & HTTP
Reports the proxy protocol and status code returned by the fixed HTTPS probe.
Latency
Measures request time; lower is generally better when compared from the same node and period.
Exit IP & location
Shows the proxy exit observed by the target and its approximate location.
Network
Identifies the ASN, network organization, or ISP associated with the exit IP.
Anonymity & notes
Summarizes anonymity and exceptions from forwarding-header and source-IP signals.
How to Test Proxies and Read Proxy Status
A live proxy status means the endpoint completed the fixed HTTPS request during this check, not merely that a socket opened. Read connectivity together with response time, exit IP, approximate location, and the observed forwarding-header or source-IP evidence.
Each result is a point-in-time observation from the current MiyaIP test service. Routing, load, rate limits, proxy lifecycle, and test-node location can change later, so availability does not equal long-term stability and anonymity does not equal security.
Choose HTTP, HTTPS, SOCKS4, or SOCKS5
HTTP is suitable for common web requests, while HTTPS targets require CONNECT tunnelling support. SOCKS4 is an older general TCP protocol with limited authentication support; SOCKS5 supports a broader range of TCP traffic and authentication.
Enter one endpoint per line, choose automatic detection or a specific protocol, and test up to ten proxies at once. An explicit URI scheme takes precedence, duplicate normalized endpoints are removed, and changing the input marks the existing result as stale.
Handle proxy credentials safely
Credentials are used only for the active backend connection. They are not returned in results, placed in URLs, logs, analytics, exports, local history, or browser storage; copied and exported endpoints are always redacted.
A fixed public HTTPS target keeps results comparable and prevents requests to private networks, cloud metadata, or arbitrary destinations. Public proxies remain untrusted and should never carry sensitive accounts, payments, or private business data.
Understand failures and retry checks
A timeout, authentication failure, connection refusal, or unsupported protocol points to a different problem. Review the reported reason before changing the endpoint, credentials, protocol, or timeout.
Temporary network congestion and proxy rate limits can also cause failed checks. Retry once under the same settings; repeated failures are stronger evidence that the proxy is unavailable or incorrectly configured.
The Complete Proxy Checking Path
After parsing each line, the checker normalizes the endpoint, removes exact duplicates, validates a public proxy host and port, and applies an explicit scheme when supplied. In automatic mode it attempts supported protocols under bounded timeouts rather than assuming that an open port identifies the application protocol. A fixed public HTTPS request then verifies that traffic can pass through the proxy to a real external target.
The service records whether that request completed, elapsed time, the observed exit IP, network and approximate location data when available, plus forwarding-header and source-address evidence. These dimensions stay separate because a fast TCP connection can still fail the HTTPS request, and a live response can still reveal proxy traces. Editing input makes previous results stale so an old result is not silently presented as a new endpoint check.
Parse and validateRead up to ten lines, normalize supported formats, reject private or unsafe destinations, and remove exact duplicate endpoints.
Select the protocolHonor an explicit URI scheme or try supported protocols in automatic mode within the check limits.
Connect and authenticateOpen the proxy connection and use supplied credentials only for this active server-side request.
Request the fixed HTTPS targetRequire an end-to-end response through the proxy rather than declaring success from an open socket.
Report independent evidenceShow status, latency, protocol, exit, location, network, anonymity signals, and any warning or failure reason.
Diagnose a Failed Proxy Check
Start with the reported failure instead of changing every setting. A second run under the same conditions can distinguish a transient route from a repeatable configuration error.
Proxy failure diagnosis
Observed result
Likely causes
What to check next
Invalid input
Malformed URI, missing host or port, unsupported scheme, invalid port, or ambiguous compact format.
Compare the line with the supported examples and bracket an IPv6 literal.
Connection refused
Nothing accepts the connection, an ACL blocks the test node, or the service moved.
Confirm host and port with the provider and check source allow-list rules.
Timeout
Endpoint is offline, congested, filtered, routed poorly, or the timeout is too short.
Retry once, then compare from the intended deployment region and ask whether access is restricted.
Authentication failed
Username, password, account status, authentication method, or IP authorization is wrong.
Re-enter credentials, check account expiry, and confirm whether the provider expects credentials or source-IP allow-listing.
Protocol or tunnel error
The selected scheme does not match the service or HTTPS CONNECT is unavailable.
Use the provider-declared protocol; automatic detection is a convenience, not protocol negotiation.
Blocked or target failure
The proxy cannot reach the fixed target or its policy blocks the request.
A live result for another site would not invalidate this observation; verify destination policy with the provider.
HTTP, HTTPS, SOCKS4, and SOCKS5 Proxy Differences
The scheme describes how the client communicates with the proxy, not whether every destination is encrypted. HTTPS websites remain protected by their own TLS when an HTTP proxy establishes a CONNECT tunnel.
Supported proxy protocols
Protocol
Typical capability
Authentication and addressing
When to choose it
HTTP
Forwards HTTP and commonly tunnels HTTPS with CONNECT.
Commonly supports basic proxy credentials; behavior depends on the server.
Web requests when the provider explicitly supplies an HTTP endpoint.
HTTPS proxy
Uses TLS between client and proxy before forwarding or tunnelling.
Can protect proxy credentials on that first hop when correctly configured.
When the provider explicitly supports an HTTPS proxy listener.
SOCKS4
General TCP forwarding with an older protocol.
Limited addressing and no standard username/password authentication comparable to SOCKS5.
Legacy endpoints and clients that explicitly require SOCKS4.
SOCKS5
General proxying with broader address and authentication support.
Can ask the proxy to resolve domain names and can support username/password authentication.
Applications that support SOCKS and need capabilities beyond ordinary web proxying.
Proxy Checker, Speed Test, or Anonymity Checker?
Run the smallest test that answers the current question. A proxy can be live yet too slow for a workload, or live and fast while still adding recognizable forwarding headers.
Does the proxy expose the test-node source or known HTTP proxy headers?
Direct baseline, exit address, seven header states, and elite, anonymous, transparent, or unknown classification.
Batch Checks, Credentials, and Point-in-Time Limits
Batch input is capped at ten endpoints so each result can remain reviewable and the public service is not turned into an unrestricted scanner. Results can finish at different times and one failure does not cancel the other valid lines. Exported or copied endpoints are redacted, and credentials never appear in the result. Protect the original list because it may still contain working secrets in your browser input.
A successful check only states that the test node reached the fixed target through that endpoint during this run. It cannot guarantee future uptime, access to another destination, compatibility from your deployment region, throughput under load, operator trust, or account safety. For important work, test from the actual environment, repeat over the relevant period, and monitor failures with your application’s own timeout and retry policy.
FAQ
Frequently asked questions
How do I check whether an HTTP, HTTPS, SOCKS4, or SOCKS5 proxy is working?
Enter one proxy per line, choose automatic detection or a specific protocol, and start the check. MiyaIP can test up to ten proxies in one batch. A live result means the endpoint completed the fixed HTTPS request during that check.
Does a live proxy status mean the proxy will remain stable?
No. Proxy status records only whether the endpoint completed the fixed HTTPS probe at that moment. Routing, load, rate limits, and the proxy lifecycle can change later, so repeat important checks.
What anonymity signals does the proxy checker report?
The result separates exit IP, forwarding-header evidence, and source-IP exposure into elite, anonymous, transparent, or unknown observations. These signals do not replace a security or trust assessment.
Why is there no composite trust score?
A single score can hide the basis for a conclusion. MiyaIP presents connectivity, protocol, response time, exit IP, location, and anonymity evidence separately so each item can be reviewed.
Can the proxy checker test proxies that require a username and password?
Yes. Supported input includes host-and-port forms with credentials and standard proxy URLs. Credentials are used for the current backend connection and are not returned in results, exports, or local history.
Why does MiyaIP use a fixed HTTPS probe instead of a custom test URL?
A fixed public probe keeps checks comparable and prevents the tool from being directed to private networks, cloud metadata, or arbitrary destinations. It confirms a real HTTPS request without promising broader access.
Why can an open proxy port still fail the proxy check?
An open TCP port proves only that something accepted a connection. The selected proxy protocol, authentication, tunnel setup, routing, and fixed HTTPS request must also succeed before MiyaIP reports the endpoint live.
Should I use automatic protocol detection?
Use it when the list has no reliable scheme. If the provider specifies HTTP, HTTPS, SOCKS4, or SOCKS5, choose that protocol directly because an explicit service declaration is more reliable than trial detection.
Can I use this result as an uptime monitor?
Not by itself. It is a manual point-in-time observation from one MiyaIP node. Long-term monitoring needs scheduled checks from relevant regions, retained timestamps, and alert thresholds matched to the workload.
