// the find
cmliu/CF-Workers-CheckProxyIP
部署在 Cloudflare Workers 上的轻量级 ProxyIP 验证工具。它能够快速、准确地检测代理IP的可用性，帮助用户筛选出有效的代理服务器。
A single-file Cloudflare Worker that's both a web UI and an API for testing whether candidate IPs/domains work as 'ProxyIP' relays for CDN-fronted proxy setups — checking raw TCP/TLS reachability, IPv4/IPv6 egress capability, and geolocation. It's for people running CDN-fronted relay/proxy services (the V2Ray/Xray crowd) who need to vet a batch of candidate IPs before dropping them into a config.
Zero-infrastructure deploy story: paste _worker.js into the Cloudflare dashboard and you have a working tool, no build step or wrangler.toml required. The input-resolution pipeline is genuinely well thought out — IPv4, bracketed IPv6, domains with an embedded port override (.tpPORT.), and batched DoH TXT/A/AAAA lookups capped at 15 per request to respect Workers' subrequest limits. It uses cloudflare:sockets directly for the TCP/TLS probe instead of faking reachability with fetch(), so a 'success' reflects an actual raw socket connection, and candidates get deduped both before and after resolution so the 32-way concurrent check doesn't burn subrequests on duplicates.
Every check's correctness hinges on two third-party domains (ipv4.090227.xyz, ipv6.090227.xyz) the project doesn't control and has no fallback for — if those probes go down or change behavior, results go silently wrong. There's no auth or rate limiting beyond Cloudflare's own subrequest ceiling, so anyone who finds your deployed Worker gets a free anonymous TCP port scanner against arbitrary hosts. There are no tests and no CI; the whole workflow is manually pasting one file into a dashboard, so there's no repeatable way to catch a regression before it ships. The frontend also pulls Leaflet, Google Fonts, OpenStreetMap tiles, and a flag CDN from third parties at runtime, which is a real risk given this tool's likely audience often sits behind restrictive networks.