misc · May 16, 2026 · 2 min read
My VPN Wasn't Enough
I was browsing a website with ProtonVPN enabled when I noticed something strange. The phone number field was already filled with my real country’s calling code, even though my VPN was connected to the Netherlands.
I was using Brave with WebRTC disabled, so my first thought was an IP or DNS leak.
I checked both. My public IP matched the ProtonVPN exit node, DNS requests were going through the VPN, and WebRTC wasn’t exposing my real IP. Everything looked fine.
Then I opened the same website in Mullvad Browser, without changing anything on the network side. This time, the phone number field showed the Netherlands.
Same VPN, same connection, different browser.
That made me suspect something in Brave’s browser fingerprint rather than the VPN tunnel.
I went to BrowserLeaks and started checking what my browser was exposing. The IP and WebRTC results looked normal. Then I noticed the timezone reported by JavaScript.
The timezone
Any website can read the timezone exposed by your browser using the Intl API:
Intl.DateTimeFormat().resolvedOptions().timeZone// "Africa/Redacted"There it was. My real timezone, even though my IP address was in the Netherlands.
A VPN changes your apparent public IP address, but it doesn’t automatically change the timezone your browser reports. That mismatch can provide another clue about your location.
It doesn’t reveal your exact location, and several countries can share the same timezone. Still, combined with other browser information, it’s a useful fingerprinting signal.
I wanted to check whether changing it would affect the website’s behavior.
I launched the browser with a timezone matching my VPN exit node. When I returned to the website, the phone number field showed the VPN country’s calling code instead of my real one.
That was the result I was looking for.
Rather than changing my system timezone every time I switch VPN servers, I now use a small wrapper that retrieves the exit node’s timezone from ipinfo.io and launches the browser with the TZ environment variable set accordingly. My system timezone stays untouched.
This worked in my setup, although it doesn’t prove that the website relied exclusively on the timezone to select the country code.
What surprised me was how easy it was to overlook. I’d checked the usual VPN leak tests, and they all looked fine. But my browser was still exposing information that didn’t match the location I was connecting from.
Hiding your IP doesn’t mean the rest of your browser fingerprint follows it.