Lebanon Proxies

Run a documented cold request, one immediate repeat, and one request after the chosen wait interval. Keep query strings and headers fixed unless the planned step changes exactly one cache key, and label rather than discard cache misses. The LBN worksheet needs a direct-control identifier, proxy configuration hash, observed country, exit IP, connection identifier, status or error class, safe content marker, and UTC timestamp. Store rejected outcomes instead of repeating until a preferred response appears. Use only an endpoint permitted for the Lebanon test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

Separate local resolver errors, proxy-side lookup failures, connection timeouts, and destination responses. A country-targeted exit does not by itself establish the resolver path, and a successful lookup does not prove the requested exit country. The Asia record immediately on either side of Lebanon is represented by Kyrgyzstan at 11,613 and Bhutan at 10,153. This is a historical-count comparison. It is not a recommendation to substitute countries or a measurement of current service. Keep LBN comparator rows labelled and diagnose the requested Lebanon route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Choose the route for browser QA only when a second clean run reproduces the accepted observation and the exit country is independently verified. Retain the profile recipe so another reviewer can repeat it. The Lebanon decision is ready only when LBN evidence covers country verification, application compatibility, session behavior, response classification, usage, and stop conditions. A pilot that changes endpoints or acceptance rules midway must be rerun or labelled inconclusive. Reject any Lebanon conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat LBN verification after a material configuration change.