What is actually verified?
Three rounds of end-to-end evidence
A published verified link must pass the required test in each of the three rounds. The tester sends an MTProto req_pq_multi request through the proxy and checks that the datacenter response contains the random nonce it sent.
DNS and server identity
Hostnames are resolved before testing. When a hostname resolves to multiple IPv4 addresses, all those addresses must pass; testing only the first IP could mislabel an intermittently failing proxy.
FakeTLS, secure and classic
FakeTLS ee links undergo the additional ServerHello HMAC check. The pipeline handles secure dd and classic secrets with their relevant MTProto connection checks.
More than an open TCP port
A TCP connection or a superficial handshake alone cannot prove Telegram connectivity. The requirement is a valid reply from a real Telegram datacenter.
Verification pipeline
Stages
Collect public candidates → parse secrets using TDLib-compatible rules → resolve DNS → deduplicate targets → test TCP and protocol-specific handshakes → verify MTProto datacenter replies → repeat three rounds → apply history → publish tiers.
What it cannot guarantee
Test runner geography
All speed and reachability measurements apply to the published test-runner location and moment. A proxy that passes from the runner can still be blocked by your country, ISP or firewall.
Operator privacy
A proxy operator can see connection metadata and the IP address from which you connect. The test does not vet proxy operators or guarantee an absence of sponsored channels.
Observed success versus future availability
The index is periodically refreshed; successful prior tests are measurements, not a promise of future service.
How to verify the source independently
Inspect the implementation
The GitHub repository publishes the Python testing code, tests, source list and documented criteria. Read the README and the test suite instead of relying only on this summary.
Inspect machine-readable evidence
The published index.json reports the runner location and verification counts. health.json includes per-source health information and rejection reasons.
Source: documented public repository and its README, criteria, and machine-readable files. Reviewed 27 October 2026. Live values can change every run. Inspect source