Integrations / Proxy setups / DNS and WebRTC with a proxy
DNS, WebRTC and time, all on the proxy’s side.
A proxy moves a profile’s address. Three things can still give the real one away: DNS lookups from your own network, WebRTC offering your local address, and a clock or language from somewhere else. Browz handles all three from the proxy’s measured exit by default.
{ "dnsMode": "remote-at-proxy" }Setup
Set it up.
DNS: keep it at the proxy
Each proxy resolves site names at the proxy by default (
remote-at-proxy).local-at-clientresolves them on this computer first, which shows your resolver every site the profile visits.Proxy fields{ "dnsMode": "remote-at-proxy" }WebRTC: leave it automatic
In Settings › Network and proxies, derive from the proxy is recommended.
replaceanddisableare there if you need them;realexposes your computer’s IP behind the proxy, and Browz warns about it.Timezone and language: leave them empty
A profile with no timezone or language set follows its proxy’s exit, measured at each check. Set them only when you have a reason, and Browz warns at launch if they contradict the exit.
create.mjsawait browz.profiles.create({ name: 'Research – Tokyo', proxyId }); // no timezone, languages or webrtcModeCheck what the profile reports
The fingerprint command shows each value the profile presents and where it came from.
Shellbrowz fingerprint "Research – Tokyo"
Example
Refuse a launch when the readings disagree.
Turn on Refuse when the exit timezone is disputed in Settings › Network and proxies. When the IP-location sources disagree about the exit’s timezone, Start is refused, so a profile never opens with a timezone that might contradict its address. Pick a proxy that is located consistently, or set the profile’s timezone yourself: an explicit choice clears the refusal.
REFUSING TO LAUNCH profile <id> (Research – Tokyo): the IP-location sources disagree about
this exit’s timezone — …Every refusal starts with REFUSING TO LAUNCH and names the profile. See exit country changed, or IP checkers disagree.
Good to know
Notes and tips.
- Launch warnings for a timezone or WebRTC setting that contradicts the exit are warnings, not refusals, unless you turn on the launch guards.
- Bring proxies from any provider: Browz supports HTTP, HTTPS, SOCKS4, SOCKS5 and SSH.
- A profile whose proxy fails its exit check is refused at Start. It never falls back to your own connection.
- A proxy changes where a profile connects from, not what a site allows. Use each site only as its terms allow; our acceptable use policy applies whatever the exit.
FAQ
DNS and WebRTC with a proxy and Browz.
Is remote DNS slower?
Not noticeably: the proxy resolves the name as part of the same connection.
Should I disable WebRTC?
Usually not: video calls and some sites need it, and a browser with no WebRTC at all is unusual. Derived from the proxy is the default for that reason.
Where do the exit readings come from?
Each check measures the exit over HTTPS through the proxy. You can add a second lookup service, and a local GeoLite2 database, to compare readings.
Get started
Download Browz. Every task, its own browser.
curl -fsSL https://gobrowz.com/agents/install.sh | sh