What a proxy connection check tells you
A proxy connection check answers one question: does the connection your browser uses right now work the way you need it to? Switch your proxy on in the browser or profile, open this page, and the check runs on its own.
A working proxy means three things. You can read all three off the results above.
- Your traffic leaves through the proxy's exit IP, in the country and on the kind of network you chose.
- Requests come back quickly and steadily, with none lost on the way.
- The protocols your apps use get through: UDP, HTTP/3 and IPv6 where you need them.
What each station on the rail means
The check shows your exit IP first, with its location, network and IP type. Under it, four stations sit on one line that fills as results land. This is what each one reads.
Exit IP
The address every website sees, looked up by our server. If this fails, nothing else can run.
- Looks right when
- The IP, country and IP type are the ones you expect.
- Fix it when
- The IP is yours, in another country, or marked datacenter or hosting.
Latency
Your browser sends one warm-up request and then 10 timed requests to our server through the proxy. You see the median, the fastest and slowest, the jitter between requests and how many were lost.
- Looks right when
- The median is steady across two runs, jitter is small next to the median, and none are lost.
- Fix it when
- Requests are lost, or the jitter comes close to the median. The link is unstable even if pages still load.
UDP
Your browser sends WebRTC traffic to our server over UDP and TCP, and our server records the address each packet came from.
- Looks right when
- UDP arrives from your exit IP, or from a sibling address on the same carrier.
- Fix it when
- No UDP means the proxy forwards TCP only. A different network means UDP skips the proxy.
HTTP/3 (QUIC)
Our server answers over HTTP/2 and HTTP/3 and reports which one arrived and from which address.
- Looks right when
- HTTP/3 comes from the same address as TCP. Staying on TCP is fine too: sites fall back to it.
- Fix it when
- HTTP/3 over UDP arrives from a different network than TCP.
IPv6
Your browser fetches an address that resolves only over IPv6.
- Looks right when
- No IPv6, or IPv6 on the same network as your exit IP.
- Fix it when
- IPv6 traffic leaves from a different network and goes around an IPv4 proxy.
Fix a proxy that fails the connection check
Find your symptom in the first column.
| What you see | Likely cause | What to do |
|---|---|---|
| The check can't reach our server, or shows no exit IP | Likely causeThe proxy isn't on for this browser, the host, port or login is wrong, or an extension blocks the page. | What to doCheck the proxy fields in the browser or profile. Open this page in a clean profile that has only the proxy set, then run the check again. |
| The exit IP is in another country | Likely causeThe proxy is set to a different location, or this tab doesn't use it. | What to doConfirm the location of the proxy you bought, and the proxy settings of the profile you opened this page in. |
| A high median latency | Likely causeThe proxy is far from you or from our server, or the link is congested. | What to doRun the check twice and compare. If both runs are slow, pick a proxy closer to you or to the sites you use. The figure is latency to our server, not a speed test. |
| Lost requests or high jitter | Likely causeAn unstable link: a weak mobile signal on the proxy side, an overloaded proxy, or a rotation in the middle of the check. | What to doRun the check again. If requests are still lost, rotate the proxy or change its location, and avoid rotating while a job runs. |
| UDP is missing or comes from another network | Likely causeThe proxy forwards TCP only, or WebRTC goes around it. | What to doUse a proxy that carries UDP over SOCKS5. See how SOCKS5 proxies carry UDP. Or block WebRTC traffic that bypasses the proxy. |
| IPv6 leaves from another network | Likely causeYour connection has IPv6 and the proxy carries IPv4 only. | What to doTurn off IPv6 on the device or network adapter, or use a proxy that carries IPv6. |
| The IP type is datacenter | Likely causeThe proxy sits on a hosting network. | What to doSites with strict anti-bot checks distrust hosting networks. A mobile proxy leaves on a carrier network instead. Compare mobile proxy prices. |
Checklist before you launch a profile or a scraping job
Run the proxy connection check from the same browser profile, machine and network the job will use. Then go down this list.
- The exit IP is in the country you chose.
- The IP type is mobile, ISP or business, not datacenter, if the target site is strict.
- The median latency is steady across two runs, and no requests are lost.
- UDP and HTTP/3 come from the exit IP, or you turned them off on purpose.
- IPv6 shows no address on another network.
- You run the check again after any change to the proxy, an extension or a browser flag.
Browser-side check or pasted-list proxy checker?
A proxy checker and a proxy connection check answer different questions. Pick the one that fits the job.
| Aspect | Pasted-list proxy checker | This connection check |
|---|---|---|
| What it tests | Pasted-list proxy checkerEach proxy on a list: alive or dead, response time, sometimes location and ISP. | This connection checkThe one connection your browser uses: exit IP, latency, jitter, lost requests, UDP, HTTP/3 and IPv6. |
| Where it starts | Pasted-list proxy checkerThe checker's server connects to your proxy. | This connection checkYour browser connects through the proxy to our server. |
| Best for | Pasted-list proxy checkerSorting many proxies quickly before you load them. | This connection checkConfirming the setup you are about to log in with. |
| UDP and HTTP/3 | Pasted-list proxy checkerUsually not part of the result. | This connection checkChecked separately, from the packets our server receives. |
| Proxy login | Pasted-list proxy checkerYou paste it into a third-party form. | This connection checkNothing to paste. The proxy is set in your browser. |
For bulk-testing a long list, a list checker is the better tool. For the connection you actually use, this check is. Neither replaces testing against your target site.
UDP and HTTP/3 are checked apart, from our server
A browser reports whatever its profile tells it to. So the UDP station doesn't trust the browser. It sends traffic to our server, and our server records where the packets came from.
HTTP/3 gets its own station. WebRTC can send UDP while the browser stays on TCP for web pages, so the two get separate results. The HTTP/3 address is shown next to the TCP address, with a note when the browser never tried QUIC.
Reading a mobile proxy result
Mobile carriers put many subscribers behind shared public addresses, so UDP can leave from a sibling address on the same carrier. The check calls that a note, not a leak. Latency on a mobile proxy is higher and less even than on a wired line, so judge it by lost requests and by how steady two runs are. With rotating mobile proxies the exit IP changes by design, so run the connection check again after a rotation and compare. For plans and locations, see mobile proxy pricing.
Proxy connection check questions
How do I check if my proxy is working?
Switch the proxy on in your browser or anti-detect profile, then open this page. The check runs on its own and shows your exit IP, location, network and IP type. If the exit IP belongs to the proxy and not to you, the proxy is carrying your traffic. The other stations show how fast and steady it is, and whether UDP, HTTP/3 and IPv6 get through.
How do I test a SOCKS5 proxy?
Set the SOCKS5 proxy in your browser or profile and run this check. The exit IP station confirms TCP works, and the latency station shows how quick and stable it is. The UDP station shows whether the proxy also carries UDP, which SOCKS5 allows but many proxies don't forward.
Can I paste a proxy here to test it?
No. This check tests the connection your browser uses and takes no pasted proxy. Set the proxy in your browser or profile, then open this page. To test a long list, use a list checker.
Why is my proxy not connecting?
The usual causes are a wrong host or port, a wrong login, a proxy that isn't switched on for that browser profile, or a firewall or extension blocking it. If this page can't load its results, your browser can't reach our server through the proxy. Fix the proxy fields, then run the check again.
What is the difference between a proxy checker and a proxy connection check?
A proxy checker usually connects to each proxy on a pasted list and reports whether it is alive and how fast. A proxy connection check looks at the connection your browser already uses and shows what it carries and how well: exit IP, IP type, latency, jitter, lost requests, UDP, HTTP/3 and IPv6.
Does the check test proxy speed or anonymity?
It times 10 requests to our server and shows the median, fastest and slowest round trip, the jitter and any lost requests. That is latency and stability, not a bandwidth test. For leaks such as WebRTC and a timezone that doesn't fit the IP, run the proxy leak test.
Does the check store my IP or proxy details?
No. Results aren't saved or linked to an account. To show the network and location, our server looks up your IP with an IP data provider and keeps that lookup in memory for a few hours.