Dominica Proxies

Keep the destination, proxy route, and protocol constant while changing only the documented DNS mode. Save the apparent exit, resolver evidence, resolved address set, client version, and UTC time, then repeat once to rule out a transient lookup. A reproducible DMA run records the source and permission, client and version, route syntax, network, protocol, session choice, observed exit, target outcome, and timestamp. Label timeouts, blocks, challenges, and missing evidence rather than suppressing them with retries. Use only an endpoint permitted for the Dominica test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

Compare each stage with the single-request baseline. Rising timeouts or denials may reflect target controls, client pooling, gateway behavior, or upstream conditions, so lower pressure and isolate the layer before assigning a cause. The nearest North America count references are Grenada with 7,180 and Antigua and Barbuda with 6,982. They help locate Dominica in the historical catalogue; they cannot validate today's route or replace country-specific testing. Keep DMA comparator rows labelled and diagnose the requested Dominica route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Purchase only for a documented use that remains within source permissions and operational controls. Technical reachability is not an acceptance criterion by itself. DMA decision review should answer whether the Dominica pilot met product support, country observation, protocol, session, valid-response, usage, and evidence requirements. If a necessary field is absent or the success rule moved, do not approve volume. Reject any Dominica conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat DMA verification after a material configuration change.