Check a proxy before launch

Every entry in the library carries its own button, and the answer lands on that row rather than in a separate window. The list stays a list: you see at a glance which addresses are alive and which are silent.

1. 1

   Open the proxy library

   The Proxies tab in the left column.

2. 2

   Find the row you doubt

   The list on that same tab, one row per address.

3. 3

   Press Test

   The button on the right of that row.

4. 4

   Read the line under the address

   The same row, where the result replaces the previous one.

The exit address, the country it belongs to, and the time to the first response. That is what a site would read, measured through the same connection a profile uses.

A row that did not answer keeps the reason and the time it was last tried, so the list stays readable without testing everything again. The timing itself is shown once, at the press: the row remembers the address, the country and when it was checked, not how fast it answered.

A proxy with a login goes through the same loopback bridge a launch uses, and an SSH entry raises a real tunnel first.

Both are taken down as soon as the answer arrives, so a press of Test leaves nothing listening behind it.

Check all walks the list from top to bottom and says how many answered out of how many were tried. The button itself shows which row is being tried right now.

It goes one at a time on purpose. Fifty probes fired at once look like a scan from the seller's side and spoil every timing reading.

The exit country is what gives a profile its clock and its language list, so the three agree with each other.

Before every launch the app runs this same check. When the proxy answers but its country cannot be worked out, the profile opens with the country confirmed last time for the same proxy, and you are told so; when there is none, the profile does not open, and the reason says why.

When you are signed in and the proxy comes from your account's library, a check that passed is written to the account as well: the exit address, the country, the answer time and when it ran. That holds for the check before a launch and for Test on the row.

In the dashboard on the website, on the Proxies tab, such a row reads Checked in the app with the time. Check in the dashboard tests from our server, and after it the row reads Checked.

The profile window has its own Test proxy button in the Proxy (optional) block, for an address you are typing by hand.

A profile with no proxy at all says so instead of pretending the test passed. A port left unfilled is named separately as well: with it the launch will not go.