A Cloudflare-based ProxyIP checker with single or batch target resolution, availability validation, and egress details.
Workspace
Start a check
Enter a single IP, IPv6 address, domain, or an entire list. Single mode keeps a local history; batch mode is ideal for pasting multiple targets.
Live resolution and validation
Single mode supports quick history fill; press Enter to start a check immediately.
Batch check
Single / single target
Results
Check results
Results, egress IPs, and the map will appear here as the check progresses.
Idle
Waiting to start
After you enter a target, results, egress details, and the map will be shown here.
Filter
Region
Export
No check results match the current filter.
Guide
What is a ProxyIP?
A practical explanation of what a ProxyIP is, what it does, and how to evaluate one in real deployments.
Cloudflare Workers / TCP
Concept
A ProxyIP is a verifiable relay endpoint
In the context of Cloudflare Workers, a ProxyIP usually refers to a third-party IP that can successfully proxy traffic to Cloudflare services. It is not an access address officially assigned to you by Cloudflare, but an external node that can forward traffic on your behalf.
Why the limit exists
Why many use cases specifically look for a ProxyIP
Cloudflare Workers' TCP sockets documentation explicitly states that outbound TCP connections to Cloudflare IP ranges are blocked. In other words, some paths that rely on connecting directly to Cloudflare IPs cannot be established directly inside Workers.
Outbound TCP sockets to Cloudflare IP ranges are blocked.
Cloudflare WorkersSend a request to reach the target service
→
ProxyIP nodeLocated on a third-party network, handling relay and reverse proxying
→
Cloudflare serviceThe site, edge service, or CDN target ultimately being accessed
In practice: Workers first connect to a third-party node, which then forwards the traffic to Cloudflare on your behalf, bypassing the restriction on direct connections to Cloudflare IPs.
Use cases
Why projects like edgetunnel and epeius use it
When the target website itself is served through the Cloudflare CDN or Cloudflare edge network, a project that needs to open a direct TCP connection to the target address may fail because of the restriction above. With a working ProxyIP configured, such projects can continue to reach the target through the relay node.
What makes one work
A working ProxyIP usually meets at least these conditions
Can successfully establish a proxied TCP connection to the specified port (usually 443)
Can reverse proxy HTTPS traffic to Cloudflare IP ranges
Why this page checks: This tool does more than static resolution — it simulates the real path as closely as possible to verify whether a target actually works, helping you quickly rule out candidate IPs that "look online but cannot act as a proxy."
Finder
Find more ProxyIPs
Discover candidate ProxyIPs by port and region from an internet-measurement database, then bring them back here to check availability.