Proxy Checker
Paste one proxy or a whole list. For each line, a real connection goes through the proxy to a public what-is-my-IP service, and our checker reports the exit IP, city, ISP and ASN the other end sees, plus how long the round trip took. Then export the ones that work.
| # | Proxy | Status | Protocol | Latency | Exit IP | Location | ISP / ASN |
|---|
How the check works
Put http://, https://, socks4:// or socks5:// in front of a line to fix its protocol; lines without a scheme use the menu above, and Auto runs through HTTP CONNECT, SOCKS5 and SOCKS4 in that order. Rather than waiting on every protocol, a line fails immediately when nothing answers on its port at all. A carrier network will read higher than a datacenter by design, since latency here is the full round trip through the proxy: connect, tunnel, TLS and one request to the lookup service.
What a good result looks like
Your mobile line should show AT&T, T-Mobile or Verizon as its ISP and the city of the metro you paid for; a working line on a US carrier is tagged "Working · mobile". The exit IP should stay put across two runs of the list while you hold a sticky session. Your tool simply needs the SOCKS5 port if HTTP fails and SOCKS5 works.
Deeper checks
Pair this checker with IPFighter's free tools to run fingerprint, bot-detection and leak tests on the same connection:
IP score & lookup ↗ Browser fingerprint ↗ Bot detection ↗ DNS leak test ↗ WebRTC leak test ↗
Credentials go toward the check itself and are not logged or stored, ever. Four lines are checked at a time, up to 200 per run, with a limit of 200 checks per address per ten minutes. Private and internal addresses are refused.