Proxy Checker
Paste one proxy or a whole list. For each line, our checker connects through the proxy to a public what-is-my-IP service with a real connection and shows what the other side sees: exit IP, city, ISP and ASN, and round-trip time. Then export the ones that work.
| # | Proxy | Status | Protocol | Latency | Exit IP | Location | ISP / ASN |
|---|
How the check works
A line with a scheme at the start (http://, https://, socks4://, socks5://) uses that protocol, a line with no scheme uses the menu above, and Auto tries HTTP CONNECT first, SOCKS5 second, SOCKS4 third. If the port does not answer at all, the line fails at once and does not wait for each protocol. Latency is the time for the full round trip through the proxy, with connect, tunnel, TLS and one request to the lookup service, so a carrier network is higher than a datacenter by design.
What a good result looks like
A mobile line should have AT&T, T-Mobile or Verizon as ISP and the same city as the metro you bought, and a working line on a US carrier is marked "Working · mobile". When you keep a sticky session and run the list two times, the exit IP should be the same. When HTTP does not work but SOCKS5 works, your tool needs to use the SOCKS5 port.
Deeper checks
To do fingerprint, bot-detection and leak tests on the same connection, use IPFighter's free tools together with this checker:
IP score & lookup ↗ Browser fingerprint ↗ Bot detection ↗ DNS leak test ↗ WebRTC leak test ↗
We use the credentials for the check, and we do not log or store them. One run can have up to 200 lines, it checks four at a time, and one address can do up to 200 checks in ten minutes. Private and internal addresses are refused.