Proxy Checker
Paste one proxy or a whole list. On each line, our checker opens a real connection through the proxy to a public what-is-my-IP service and reports what that service sees, namely the exit IP, city, ISP and ASN, and the round-trip time. Then export the ones that work.
| # | Proxy | Status | Protocol | Latency | Exit IP | Location | ISP / ASN |
|---|
How the check works
A line's protocol is the scheme it starts with (http://, https://, socks4://, socks5://), or the menu above if it has none; Auto tries HTTP CONNECT, then SOCKS5, then SOCKS4. If there is no answer at all on the port, the line fails at once rather than waiting on each protocol. Latency here means the full round trip through the proxy, including the connect, the tunnel, TLS and one request to the lookup service, so a carrier network reads higher than a datacenter by design.
What a good result looks like
The ISP for a mobile line should be AT&T, T-Mobile or Verizon and its city should be the metro you bought; working lines on a US carrier carry "Working · mobile". If you hold a sticky session and run the list twice, the exit IP should be the same on both runs. If a line works over SOCKS5 but not HTTP, your tool simply needs the SOCKS5 port.
Deeper checks
IPFighter's free tools work well next to this checker for fingerprint, bot-detection and leak tests over the same connection:
IP score & lookup ↗ Browser fingerprint ↗ Bot detection ↗ DNS leak test ↗ WebRTC leak test ↗
Credentials entered here are used for the check, and none are logged or stored. A run accepts up to 200 lines, checked four at a time, and one address can make up to 200 checks per ten minutes. Private and internal addresses are refused.