Proxy Checker
Paste one proxy or a whole list. Each line gets a real connection through the proxy to a public what-is-my-IP service, and the checker reports what the far end sees: the exit IP, city, ISP and ASN, plus the round-trip time. Then export the ones that work.
| # | Proxy | Status | Protocol | Latency | Exit IP | Location | ISP / ASN |
|---|
How the check works
Each line follows its own scheme if it begins with one (http://, https://, socks4://, socks5://); lines without a scheme follow the menu above, where Auto attempts HTTP CONNECT, then SOCKS5, and last SOCKS4. A port with no answer at all makes the line fail immediately, without waiting through every protocol. Latency measures the complete round trip through the proxy (connect, tunnel, TLS and one request to the lookup service), which is why a carrier network will by design read higher than a datacenter.
What a good result looks like
A mobile line should list AT&T, T-Mobile or Verizon as the ISP and a city matching the metro you purchased, and working lines on a US carrier are labeled "Working · mobile". With a sticky session held, two runs of the list should return the same exit IP. A line that fails on HTTP but works on SOCKS5 simply means your tool needs the SOCKS5 port.
Deeper checks
This checker pairs well with IPFighter's free tools when you want fingerprint, bot-detection and leak tests on the same connection:
IP score & lookup ↗ Browser fingerprint ↗ Bot detection ↗ DNS leak test ↗ WebRTC leak test ↗
Your credentials serve the check and are never logged or kept on file. A run takes up to 200 lines, four at a time, and each address is limited to 200 checks per ten minutes. Private and internal addresses are refused.