Proxy checker

What the checker tests

For each proxy, the checker opens a real connection through it and loads Cloudflare's trace page, the same way your browser or bot would. That one request tells you four things.

• Working or dead: the proxy accepted the connection and passed traffic.
• Protocol: whether it speaks HTTP or SOCKS5. If you don't say which, it tries HTTP first, then SOCKS5.
• Exit IP: the address sites will see, which isn't always the IP you connected to.
• Speed and IP type: how long the round trip took, and whether the exit IP is mobile, residential or datacenter.

Supported formats

One proxy per line, in any of these layouts. The proxy format converter reads the same ones if you need to switch between them.

• ip:port and ip:port:user:pass
• user:pass@ip:port and user:pass:ip:port
• http://user:pass@ip:port and socks5://user:pass@ip:port

What the errors mean

• Timed out: nothing answered within 10 seconds. The proxy's down, overloaded, or a firewall is dropping us.
• Wrong username or password: the proxy is up and rejected the credentials. A stray space at the end of the line is the usual cause.
• Connection refused: nothing is listening on that port.
• Not an HTTP or SOCKS5 proxy: something answered, but in neither protocol.
• Proxy refused the request: it's up but wouldn't connect out, often because the plan's out of data or it only accepts whitelisted IPs.

Why the speed here isn't your speed

Speed is measured from our server in the US, through your proxy, out to Cloudflare. If you're in Brazil and the proxy's in Vietnam, your numbers will differ. Use it to compare proxies against each other, not as an absolute.

Proxies on private networks (10.x, 192.168.x and the like) are refused, since there's no way to reach them from the internet anyway. Want to see what a proxy looks like from your own browser instead? Connect through it and open the IP checker.