Proxy Checker
Paste one proxy or a whole list. Line by line, our checker makes a real connection through the proxy to a public what-is-my-IP service and shows what arrives at the other end: the 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
The protocol for a line comes from its leading scheme (http://, https://, socks4://, socks5://) if it has one, otherwise from the menu above, with Auto going HTTP CONNECT, then SOCKS5, then SOCKS4. No answer at all on the port means the line fails straight away, with no wait on each protocol. What you see as latency is the full trip through the proxy and back: connect, tunnel, TLS and one request to the lookup service, so carrier networks read higher than datacenters by design.
What a good result looks like
Mobile lines should come back with AT&T, T-Mobile or Verizon as the ISP and the city of the metro you bought, and working lines on a US carrier read "Working · mobile". On a sticky session, running the list twice should give you the same exit IP each time. HTTP failing while SOCKS5 works just means your tool should use the SOCKS5 port.
Deeper checks
Alongside this checker, IPFighter's free tools handle fingerprint, bot-detection and leak tests on the same connection:
IP score & lookup ↗ Browser fingerprint ↗ Bot detection ↗ DNS leak test ↗ WebRTC leak test ↗
The check uses your credentials, and they are never logged or stored. Runs top out at 200 lines, checked four at a time, and each address gets up to 200 checks per ten minutes. Private and internal addresses are refused.