Skip to main content
The Checker tab tests your profiles and reports five things about each one. Every field either shows a real answer or says it could not get one — it never fills a gap with a guess.

​
The five fields

Four of these need an outbound request to a third party, so they are off by default. Turn on the ones you want under Settings → Network checks, where each one names the exact host it contacts.
A field you have not enabled shows n/a, not a blank or a zero. Hover it to see the reason.

​
Check versus Measure

Two buttons, two very different operations.

Check

Tests the proxy without touching your current routing. Safe to run on any profile at any time, including all of them at once.

Measure

Switches the browser onto that proxy, times a real request, then switches back. Accurate, but it briefly routes your traffic through the proxy being tested.
Measure exists because a proxy’s true latency cannot be observed from outside it. The extension is explicit about the trade: the button’s tooltip states that it briefly routes all traffic through the proxy and restores afterwards. Only one measure or health check can run at a time — both drive the browser’s single proxy setting, and two at once would fight. A second one reports busy rather than queueing behind the first.

​
Running the whole list

Check all runs every profile in sequence and fills the table as results arrive. Press it again to stop; results already collected stay on screen.

​
Reading a result

  • Reachable, IP changed — the proxy works and traffic is going through it.
  • Reachable, IP unchanged — the proxy answered, but your egress address is the same as without it. Worth investigating.
  • Unreachable — the proxy refused or timed out. If this profile is the active one, a health check with failover would have switched you off it.
  • Field shows an error — that specific lookup failed; hover for the reason. The other fields are still valid.