Test proxies & auto timezone
Once you’ve attached a proxy to a profile, Santiago can test it to find the real exit IP — the public address the world sees when the profile is online. That exit IP does more than confirm the proxy works: it powers WebRTC fake mode and auto-matches the profile’s timezone and language so everything lines up with the proxy’s location.
Test a proxy
Section titled “Test a proxy”The proxy test checks that Santiago can connect through your proxy and reports back the exit IP — the address that websites will see. Run it from the proxy section of the profile form (where you enter the proxy host, port, and credentials).
A successful test tells you three things:
- The proxy is reachable and your credentials are accepted.
- The exit IP, so you can confirm the proxy lands in the country you expect.
- The data Santiago needs to align the rest of the fingerprint with that location.
If the test fails, the proxy is unreachable or the credentials are wrong. Double-check the host, port, username, and password, then test again. See Configure proxies for the supported proxy types and how to fill in the connection details.
What the exit IP is used for
Section titled “What the exit IP is used for”The exit IP detected during the test (and again automatically when you launch the profile) feeds two parts of the profile so the browser presents a consistent location.
| Feature | What the exit IP does |
|---|---|
| WebRTC fake mode | Makes WebRTC report the proxy’s IP instead of your real IP |
| GeoIP auto-match | Sets the profile’s timezone, location, and language to match the exit IP |
Both happen behind the scenes when the profile launches. You only need to make sure a proxy is attached and the relevant options are turned on.
WebRTC fake mode
Section titled “WebRTC fake mode”WebRTC is a browser technology that can leak your real IP address even when you’re behind a proxy. Santiago offers three WebRTC modes:
| Mode | Behavior |
|---|---|
real | WebRTC works normally and reports your actual connection |
fake | WebRTC reports the proxy’s exit IP, so it matches the rest of your setup |
disabled | WebRTC is fully blocked |
When you set WebRTC to fake, Santiago looks up the proxy’s exit IP and makes every page in the profile report that IP through WebRTC. The result: your real IP stays hidden and the WebRTC address matches the proxy you’re using. This is why a working proxy matters — fake mode needs the exit IP to do its job.
You can read more about how this fits into the wider fingerprint on How fingerprinting works and Fingerprint parameters.
GeoIP auto-match (timezone & language)
Section titled “GeoIP auto-match (timezone & language)”A common giveaway is a mismatch between your proxy’s country and your browser’s timezone or language. A US proxy paired with a European timezone looks suspicious. GeoIP auto-match removes that mismatch automatically.
When auto-match from proxy is enabled on a profile, launching it with a working proxy makes Santiago:
- Set the timezone to the proxy’s region (so
Dateand clock-based checks match). - Set the location (latitude/longitude) used for geolocation requests.
- Set the browser language to the locale for that region — unless you’ve set a language manually, in which case your choice is kept.
The lookup happens at launch using the exit IP detected at that moment, so the location data is always based on the proxy that’s actually in use. You can fine-tune or override any of these values yourself — see Geolocation.
When the proxy fails
Section titled “When the proxy fails”Santiago is built to degrade gracefully, so a flaky proxy never leaves a profile in a broken state:
- No proxy attached — the location lookup is skipped entirely. The profile uses the timezone and language you set by hand.
- Proxy lookup fails at launch — the browser still opens, just without the auto-matched location override. This is logged as a warning and the profile keeps working with its existing settings.
- Proxy unreachable — the test reports a failure so you can fix the connection details before launching.
In short, a proxy problem degrades the location matching but never blocks you from opening the profile.
Recommended setup
Section titled “Recommended setup”For the most consistent profile, combine all three:
- Attach a proxy and test it to confirm the exit IP and country.
- Set WebRTC to
fakeso the WebRTC IP matches the proxy. - Enable GeoIP auto-match so timezone and language follow the proxy automatically.
With this combination, your IP, WebRTC address, timezone, and language all point to the same place every time you launch.
Related pages
Section titled “Related pages”- Configure proxies — supported proxy types and connection settings
- Geolocation — manual timezone, location, and language overrides
- Fingerprint parameters — all the fields that make up a profile
- Create & edit profiles — where these options live in the profile form
- Common errors — fixes for proxy and launch problems