2026-06-07 · Sam Okonkwo · 837 words
Match the fingerprint to the exit geo
Geo, timezone, and language should follow the exit. Product does this on start. This how-to is alignment, not a hide-the-mismatch guide. Authorized work only.
Geo, timezone, and language should follow the exit. A Chicago clock on a Frankfurt IP is a story the page can read in one glance. MaskWright updates those fields on profile start from an exit lookup. This how-to is alignment. It is not a hide-the-mismatch guide. Authorized work only.
Proxies in an antidetect browser is the pillar. The rest of the cluster lives under Proxies.
What "follow the exit" means
The site sees an IP. Geo databases map that IP to a country, often a city, and a timezone. The browser also exposes Intl timezone, Date, navigator.language, navigator.languages, and (if you allow it) a geolocation coordinate. Those rows should agree with the exit you attached. They should not agree with the office in another country unless the profile is supposed to be the office.
Alignment is not stealth. It is coherence. A profile that claims to be in one place should not also claim to be in another.
On start, fetchExitGeo(proxy) queries ip-api.com through the proxy, or direct if there is no proxy. Timezone, locale, languages, and geolocation on the fingerprint record update before launch. At CDP apply, the page may probe ip-api.com or geojs.io again and re-align. That traffic leaves the machine. There is no offline country inventor.
If there is no proxy, the house path is the exit. Alignment to a foreign locale in that state is a costume. I do not do that on a login I intend to keep.
What the product writes
| Field | How it is applied | Source when a proxy works |
|---|---|---|
| Timezone | CDP setTimezoneOverride plus TZ on launch | IANA zone from ip-api.com |
| Locale / languages | CDP locale + inject of navigator.language | Boring match to exit country (en-US on a US exit) |
| Geolocation | CDP setGeolocationOverride | Exit country, not rooftop theater |
| WebRTC | Prefs + inject, separate from geo | Filter candidates; cannot paint over a house IP |
Coordinates that sit in the right country are enough for coherence. Precision theater (a rooftop on a CGNAT exit) is not a feature I will sell.
When alignment fails
The lookup failed. Auth was wrong. Proxy username and password formats is the paste page. SOCKS5 versus HTTP is the scheme page. TCP connect can still succeed while geo fails.
The lookup returned the house IP. The browser or the check skipped the line. Check the exit IP before launch is the habit. Do not start the ads profile in that state.
The exit rotated between check and launch. Rotating proxies break logins. Sticky sessions exist so the street stays put. Alignment to yesterday's city on today's IP is a new mismatch.
Windows DNS or IPv6 skipped the proxy for some requests. DNS leaks on Windows is the how-to. Alignment of JS timezone does not fix a resolver that asked the ISP for the name.
I do not "fix" a failed alignment by typing a timezone I saw on a forum. I fix the line or I work without a proxy.
What I do not claim
I do not claim the site will believe the profile. Detection is a site policy plus a stack we do not control. Coherence is the most the launcher can offer.
I do not claim every surface is aligned. Canvas, WebGL, and fonts are seed problems, not geo problems. A US exit with a Japanese font stack is a different mismatch.
I do not claim HTTPS-to-proxy TLS. The https type is an HTTP forwarder. Geo still runs through that forwarder when the line works.
I do not upload the fingerprint. Bring your own proxy: credentials live in encrypted profiles.json (AES-256-GCM). The geo hosts see a lookup. The profile tree stays on disk. Cookie JSON and localStorage JSON are plaintext on that disk.
Operator sequence
- Attach the line to the profile that needs it.
- Check the exit. Read country and timezone.
- Start the profile so alignment can run.
- If you need to confirm, use a public geo page in that profile after launch, not in the personal Chrome.
- If timezone or language still show the office, stop. Do not open the login.
- Keep the same sticky exit for the life of those cookies.
Do not bounce locales on a live session to "look more native." That is a new device story. Do not copy a geolocation from a different brand's profile. Seeds stay with folders.
FAQ
Does alignment hide a listed proxy? No. It makes clock and language agree with the IP. Lists and latency are separate.
What if I have no proxy? The house path is the exit. Do not paint a foreign locale on a house IP for a login you intend to keep.
Can I type a timezone by hand if geo fails? I do not. Fix the line or work without a proxy.
Align the clock and the language to the street you actually came out on. If you cannot name that street, do not open work.