Record the exit actually in use
Use an authorized diagnostic endpoint to record the public IP of the proxy connection, then check its country with an IP geolocation source. Record the date and source name. If two databases disagree, do not silently choose the one that suits you: document the difference and test the behavior on the target that matters to you.
Distinguish country, city and coordinates
IP database accuracy varies and may differ from the database used by your target website. Country selection does not certify a city. The browser Geolocation API uses a separate mechanism, with permission and possible sources such as GPS or Wi-Fi. A proxy does not replace those sensors or their settings.
Align language and preferences
The Accept-Language header and browser settings express language preferences. The website may also read a cookie, a signed-in session or a manual market selection. To isolate the effect of the network country, start with a clean test profile and change one variable at a time.
Keep useful evidence
At a minimum, record the UTC time, requested country, observed IP, geolocation source, language, time zone and task outcome. Avoid including credentials or session cookies in shared evidence. If targeting fails, this context helps support distinguish an incorrectly configured gateway from website behavior.
Frequently asked questions
Why does the website still show my previous country?
A cookie, signed-in account, language setting or market selector may take precedence over the IP. Test with a clean profile and check each setting.
Can an IP be assigned to two different cities?
Yes. Geolocation databases can produce different estimates. Do not treat an estimate as proof of a precise physical location.