Proxy Checker

Paste a list, press Check. Every format parsed as you type, then a real request through each line — live or dead, in milliseconds.

Proxy checker3 of 4 live
104.28.41.7:8080Residential · Comcast112 msLive
88.99.14.2:1080Datacenter · Hetzner38 msLive
51.75.22.9:8080ISP · BT Group74 msLive
177.54.8.31:1080Timed outDead
Try it

Paste a list and check it

Every format, parsed as you type. Press Check and each usable line gets a real request through it.

Proxy checker0 of 0 usable
Total0
Usable0
Issues0
Live rate
Your list
0 / 200 proxies
Parsed in your browser. Check sends the list to our server once, never stored.

Paste a list above and it is parsed as you type.

Checked lines are used once and never stored.

Get proxies that pass
What's included

Everything in the checker

01Any providerNothing here is tied to our network. Bring a list from anywhere — it is the same parse either way.
02Four formats, one parserhost:port, host:port:user:pass, user:pass@host:port and scheme:// prefixes, mixed together in the same paste.
03The reason, not just a crossA rejected line says what is wrong with it — the port, the host, the credentials — rather than failing silently and leaving you to guess.
04Private addresses caughtLoopback, RFC-1918 and link-local get flagged. A list full of those usually means an export from a local config nobody else can reach.
05Duplicates droppedThe same host and port twice is one entry in the clean list, however differently the two lines were written.
06Latency and exit IPThe two things a parse cannot know: how long the round trip took through that proxy, and the address it actually came out of.

Questions, answered

That the request did not complete through that proxy — refused, reset, timed out, or the proxy rejected the credentials; the row says which. It does not always mean the proxy is dead: one can be alive and still be blocked by the endpoint we test against.

Yes, and there is no account behind it. It is useful to us as a tool people find us through, so it stays open.

No. Parsing happens in your browser and never touches us at all. Pressing Check does send those lines to our server, because a browser cannot make a request through a proxy — but they are used for one request each and dropped. Nothing is logged or kept.

The usable lines only, deduplicated, written as scheme://host:port. Paste that straight into whatever you were configuring.

SerpProxies is for teams that move.Make your move.