What to test in Belarus
Start with a local question. Keep the network, language, and delivery settings separate so the result tells you something useful.
Compare Belarusian and Russian presentation
For Belarus localization, use the site's supported Belarusian and Russian interfaces as separate test paths. Retain query text, selected language, and any redirected URL. A shared Cyrillic script is not enough to identify the language, and the exit country does not choose it for you.
Classify the first failed step
On a Belarus route, distinguish gateway authentication, DNS resolution, connection timeout, HTTP refusal, and an application message. Save timing for the first failed step. A destination's refusal is not proof that the proxy connected through another country, nor a reason to keep retrying indefinitely.
Build a consistent regional comparison
If your own service operates in Belarus and nearby markets, compare the same public page with Lithuania or Poland using fixed account and language settings. Document any regional availability message as it appears. Do not interpret a working neighbouring route as evidence of Belarus service availability.