What to test in Afghanistan
Start with a local question. Keep the network, language, and delivery settings separate so the result tells you something useful.
Test each supported right-to-left journey
For Afghanistan localization, run the site's Persian and Pashto versions separately where available. Check navigation, mixed-script identifiers, and error messages as well as body text. Save the selected language; a country match cannot establish whether the intended translation or direction is displayed.
Keep Kabul address handling separate from routing
Use an Afghanistan test address your own service supports and inspect how city, area, and contact fields persist through the form. Do not infer delivery eligibility from a successful homepage request. The application may reject a destination even when the proxy connection is working.
Locate the failed connection step
For an Afghanistan route test, capture gateway authentication, DNS, connection time, and the final HTTP outcome separately. Begin with a permitted diagnostic endpoint before your target. Keep a refusal or missing route visible; a neighbouring country's working connection is not evidence of Afghanistan availability.