Proxy Checker
Paste one proxy or a whole list. For every line, the checker opens a real connection over the proxy to a public what-is-my-IP service and measures what the other end sees: 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
Schemes at the start of a line (http://, https://, socks4://, socks5://) override the menu above for that line; without one the menu applies, and Auto tries HTTP CONNECT, then SOCKS5, then SOCKS4. A port that gives no answer at all fails the line instantly instead of waiting on each protocol. Latency is timed end to end through the proxy, from connect through tunnel and TLS to one request to the lookup service, so a carrier network reads higher than a datacenter by design.
What a good result looks like
A mobile line ought to report AT&T, T-Mobile or Verizon for ISP and the metro you bought for city, and working lines on a US carrier get labeled "Working · mobile". Across two runs of the list on a held sticky session, the exit IP should stay identical. Fails on HTTP, works on SOCKS5: your tool just needs the SOCKS5 port.
Deeper checks
IPFighter's free tools sit well beside this checker for fingerprint, bot-detection and leak testing on the same connection:
IP score & lookup ↗ Browser fingerprint ↗ Bot detection ↗ DNS leak test ↗ WebRTC leak test ↗
Credentials are used to perform the check and are never logged and never stored. Four lines run in parallel, up to 200 per run, and an address is limited to 200 checks in ten minutes. Private and internal addresses are refused.