Check proxies and see where they exit

A check asks the proxy itself where it comes out. LoginDeck sends one small request through the proxy and records the address, the city, the region, the country, the network and the timezone, plus how long the round trip took.

📍 Check saved proxies#

In the left sidebar, click Proxies.
For one proxy: ⋯ → Check now. The toast reports "{address} — {city}, {country} · {network} · {timezone}".
For several: tick the rows and click Check now in the dock at the bottom.

Several proxies are checked one at a time, with a progress bar and a tally. Stop ends the run — the check already in flight finishes, and nothing new starts. At the end you get a summary: how many were reachable, how many failed, how many were not reached.

Checking two saved proxies, then reading the Last check and Speed columns.

Only one check run happens at a time. Starting a second says "A proxy check is already running".

📊 What the columns mean#

Column	Reading
Last check	never if it has not been checked. A green pill with the city and country, plus how long ago, when it answered. A red failed pill when it did not — hover it to read the exact error.
Speed	The round trip of that check through this proxy, not bandwidth. Under 600 ms is fast ("answers immediately"), under 1.5 s is ok ("pages will feel a beat behind"), above that is slow ("expect timeouts on heavy sites").
Auth	user / pass if the proxy has credentials, none if not.
Used by	How many profiles point at this saved entry.

Results are stored, so reopening the page does not spend another request. Every check costs traffic on your proxy plan.

🔄 Check a profile's exit#

In All profiles, the Proxy & Location cell has two small buttons:

↻ — Refresh IP: ask the exit what address it is on now. The toast names the profile, the address and the city.
⇄ — call the proxy's Change IP link, or tell a bound phone to cycle its mobile data. See Change a proxy's IP.

The ↻ button in the top app bar refreshes the whole list and re-checks every distinct proxy your profiles use, a few at a time, showing progress in its tooltip.

Inside the profile editor's Proxy tab, Check (saved proxy) and Check proxy (one-off) do the same thing — and those two also match the profile's language and clock to the exit.

🛟 What a failure means#

The message is the diagnosis. The ones you will actually see:

Message	What to do
the proxy's hostname would not resolve	The host is wrong, or the gateway name has changed at your provider.
nothing accepted a connection on that proxy's port — it may be blocked on this machine or by the network	Wrong port, or a firewall on this computer.
it timed out after 20s	The proxy is overloaded or unreachable. Try again, then try another exit.
the proxy rejected the credentials (407)	Login or password is wrong, or your plan needs this computer's address on its allowlist.
the proxy refused to open a tunnel (405) / the proxy refused to open the tunnel	The proxy will not carry this kind of connection. Check the type — HTTP versus SOCKS 5.
the TLS handshake through that proxy failed	Often a transparent proxy or filtering in the way.
the proxy accepted the connection and then said nothing	Usually a wrong type, for example a SOCKS proxy saved as HTTP.
no internet connection — this machine cannot reach anything even without the proxy	The problem is on this computer, not the proxy.
curl is missing from this machine — LoginDeck uses it for the lookup	Restore or reinstall `curl`.

When this computer is offline, LoginDeck keeps the proxy's last good result rather than marking it failed.

More detail, including what to do about each: A proxy won't connect.

ℹ️ Good to know#

A check through a phone that is mid-rotation will not answer — the tunnel is down while the radio cycles. Wait a few seconds.
Speed is measured once, at the last check. It is a snapshot, not a monitor.
Proxies added by Import are checked automatically; a proxy added with + Add proxy is not.
To see what the browser reports through the proxy — including whether it is using the proxy at all — run a fingerprint check on a profile that uses it.