Această pagină nu este încă în limba dumneavoastră. Citiți textul în engleză.
Network
The connection check before work
- This computer's own connection
- What it measures
- Address, latency, names, clock, WebRTC
- Rows in the window
- Never
- Through a profile proxy
- 400 ms
- Warn from
Where the check lives
The address chip in the top bar shows the address this computer leaves from, filled in once when the app opens. Press Refresh and it asks again, so you see a changed address when you ask.
Run the sweep when the line has moved: a new office, a hotel network, or a computer that suddenly answers slowly.
- 1
Open the address chip
It sits in the top bar above the profile list and shows the address this machine leaves from.
- 2
Press Run diagnostics
The button is at the foot of that panel: you land in the Network diagnostics window with a sweep already running.
- 3
Read the statuses
You read Pass, Warn, Fail or Info at the end of every row.
- 4
Run it again after a change
Re-run repeats the whole sweep, so you read the new network, not yesterday's.
What the address panel shows
Six fields sit in the panel: the address, the country with its code, the city, the provider, the network number and the time zone.
A field the source did not give you do not see at all: a row here is either a real value or missing. You see the country only when it arrives as a two-letter code, because a profile takes its clock from it.
Where these values come from
The app asks four sources over TLS in turn, until one answers with a country. These services are free and therefore rate limited, so each extra source is an independent quota.
When nothing answered at all, the panel says so rather than leaving yesterday's address on screen.
What each row measures
You read measurements taken at the moment you pressed, and each one carries its own status.
The app measures address, latency and names over the network. The clock reuses the address already fetched, and the WebRTC reading never leaves this machine.
| Row | What it measures | When it is not green |
|---|---|---|
| Public IP and location | The address this computer leaves from, asked over TLS | Fails when no source answers |
| Latency | Time to the first answer, one row for each of two hosts | Warns from 400 ms, fails on silence |
| DNS resolution | One name put through this computer's own resolver | Fails when the name does not resolve |
| System time zone | The machine zone against the zone of its address | Warns when the two disagree |
| WebRTC leak protection | Candidates from the profiles' engine and a STUN server on this computer | Fails when a request goes past the proxy or a real address appears |
It measures this computer
The sweep goes out on the app's own connection. No profile proxy stands in front of it, and that is the point: the address here is worth reading only because it is your real one.
So a green sweep tells you the machine under your profiles is sane, and that is worth knowing before you blame a proxy. It tells you nothing about the profile you are about to open.
One machine, not one profile
The app asks for WebRTC candidates itself
A line that only quoted the setting would read the same on the day it stopped applying. So the row turns red when a request goes past the proxy or a real address comes back.
The app starts the engine your profiles open with on a test profile behind a stand-in proxy, and asks for candidates from a STUN server at this computer's own local network address. The proxy carries no UDP, so a request that reaches that server went past the proxy. The row names the engine it measured.
An address the browser has replaced with a made-up name ending in .local is the protection working, not a leak. The app closes the test browser as soon as the reading ends.
Test fingerprint measures a profile with a proxy the same way, in its own mode and with its extensions.
Not measured is not passed
Pass, Warn and Fail are results. Info is not one: it means the reading never happened.
A reading that could not be taken would mislead you if it were drawn as passed. So you find rows that were never measured under a heading of their own, below the results.
You get no verdict on the clock when either zone is missing: the address lookup failed, or this machine did not name its own.
Where a profile's verdict lives
Each profile opens on its own start page unless it is switched off on the Engine screen, and that page compares the address it came out of with your real one. Equal addresses on a profile that has a proxy mean it is not working, and the page says so in red.
That comparison needs your real address, which the app learns outside any profile proxy and keeps for an hour. When it could not be learned there is no verdict at all.
You measure a single proxy with Test on its library row, which takes the same road a launch takes.
What this does not do
- It is not a check of your profiles. The sweep leaves on the app's own connection with no profile proxy in front of it, so every row describes this computer and the engine installed on it.
- It cannot say where a name was answered. You learn only that a name resolved, and proving where needs a server on the other side of the question.
- A red WebRTC row names the leaked addresses, but no more than five, or says the request went past the proxy.
- Every row green is not a safe account. A leak is one of the ways accounts get tied together, and the rest are not on this screen.
How to check
Every claim above sits in one file, and a stand holds the readings that break quietly.
- Five measurements on the app's own connection, WebRTC among them
- apps/desktop/src/main/main.js
- A home address in the candidates is called a leak, and a hidden one is not
- apps/desktop/src/main/main.js · apps/desktop/test/leak-verdict.js
- No verdict at all when your own address is unknown
- apps/desktop/src/start/start.html · apps/desktop/test/leak-verdict.js
- The address and location come from three or more sources over TLS, tried in turn
- apps/desktop/src/lib/exitGeo.js · apps/desktop/test/exit-geo.js
- A row that was not measured is drawn under its own heading
- apps/desktop/src/manager/renderer.js
- The WebRTC row measures the profiles' engine and turns red on a leak
- apps/desktop/src/lib/проверка-webrtc.js · apps/desktop/test/webrtc-диагностика-живьём.js
Questions
- Does this check the profile I am about to open?
- No. Here you measure this computer's connection, and the verdict for one profile stands on that profile's own start page.
- Why does a row say Info instead of Pass?
- Because it was not measured. You find those rows under Notes, not among the results.
- What does the clock row compare?
- The time zone of this machine against the zone that belongs to its public address. With either zone unknown there is no verdict.
- Does the sweep go out through a proxy?
- No, it uses the app's own connection, which is what makes the address row your real address. A bought proxy you measure with Test on its library row.
- Does the WebRTC reading send anything out?
- No. The STUN server it asks runs on this computer, and the stand-in proxy refuses every connection outward.
See what your connection says
In ARMANOS, open the address chip in the top bar and run the check.