Proxy Checker
Paste one proxy or a whole list. The checker connects through each proxy, for real, to a public what-is-my-IP service and tells you what the other side sees: exit IP, city, ISP and ASN, and 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
When a line opens with http://, https://, socks4:// or socks5://, that scheme sets its protocol; any other line uses the menu above, and on Auto the order is HTTP CONNECT, SOCKS5, then SOCKS4. The line fails at once if the port gives no answer at all, instead of waiting on every protocol. Because latency counts the full round trip through the proxy, from connect and tunnel to TLS and one request to the lookup service, a carrier network reads higher than a datacenter by design.
What a good result looks like
The ISP on a mobile line ought to be AT&T, T-Mobile or Verizon, with the city matching the metro you bought; working US-carrier lines show "Working · mobile". Keep a sticky session going, run the list a second time, and the exit IP should not change. If SOCKS5 works where HTTP fails, point your tool at the SOCKS5 port.
Deeper checks
To test fingerprint, bot detection and leaks on the same connection, IPFighter's free tools make a good partner for this checker:
IP score & lookup ↗ Browser fingerprint ↗ Bot detection ↗ DNS leak test ↗ WebRTC leak test ↗
Any credentials you enter go into the check and are never logged or stored. You can check up to 200 lines per run, four at once, and an address can make up to 200 checks per ten minutes. Private and internal addresses are refused.