Claude VPN Detection
Does a VPN hide Claude or Codex region signals?
A VPN changes the network layer, but it does not automatically change the browser profile. ClaudeSignal helps you see whether IP country and browser-visible regional signals agree.
Direct answer
No. A VPN can move IP geolocation, but timezone, browser language, Intl locale, fonts, date format, number format, WebGL/GPU renderer, keyboard layout, screen DPI, and emoji rendering may still expose regional context.
That mismatch is exactly why ClaudeSignal combines client-side signals with server-side IP geolocation instead of treating IP as the only answer. A VPN changes where your traffic appears to originate, but it does not rewrite your browser's fingerprint.
What a VPN actually changes
A VPN operates at the network layer. It encrypts your traffic and routes it through a remote server, so the destination sees the VPN server's IP instead of your real IP. This effectively changes your apparent geographic location at the network level.
However, a VPN does not interact with your browser's JavaScript environment, operating system settings, installed fonts, hardware information, or rendering stack. These layers continue to operate exactly as they did before the VPN connection was established.
In technical terms, a VPN changes the src IP in your network packets but leaves the following untouched: Intl.DateTimeFormat output, navigator.language, Canvas font detection results, WEBGL_debug_renderer_info output, Intl.NumberFormat patterns, Intl.DateTimeFormat date patterns, and window.devicePixelRatio.
Common mismatch pattern
The most common pattern ClaudeSignal detects is this:
- IP country points to the United States, Singapore, Japan, or Germany (where many VPN servers are located).
- Browser timezone still points to Asia/Shanghai, Asia/Hong_Kong, or another local region.
- Browser language still set to zh-CN with Chinese as the primary language.
- Regional fonts like PingFang SC or Microsoft YaHei are still installed and detected.
- Date format still follows YMD pattern instead of MDY (US) or DMY (Europe).
This pattern is so common that ClaudeSignal specifically looks for it as an indicator of VPN usage. The combination of "foreign IP + local browser fingerprint" is a strong signal that the user is routing traffic through a VPN while their actual environment remains unchanged.
Why this matters for Claude Code
Claude Code runs in a terminal environment, not in a browser. It can read system-level information like timezone, hostname, and network configuration directly from the operating system. A VPN that changes your IP does not change these system-level signals.
When Claude Code connects through a VPN endpoint, the server sees the VPN's IP address but may still receive system-level signals (like timezone) from the actual operating system. This creates a potential mismatch between what the network layer says and what the system layer says.
ClaudeSignal's web-based scanner approximates what Claude Code might see by checking the same Intl.DateTimeFormat API. While web browsers cannot access all the system information Claude Code can, the key timezone and locale signals are consistent between the two environments.
Signal-by-signal VPN analysis
Timezone: Unchanged by VPN. The OS timezone remains whatever was configured during installation.
Browser language: Unchanged by VPN. Language preferences are stored in browser settings, independent of network configuration.
Regional fonts: Unchanged by VPN. Fonts are installed at the OS level and detected through Canvas rendering.
WebGL/GPU: Unchanged by VPN. GPU information comes from hardware drivers, not network configuration.
Number and date formats: Unchanged by VPN. These follow the OS locale settings.
Keyboard layout: Unchanged by VPN. Physical keyboard layout is a hardware property.
Screen DPI: Unchanged by VPN. Display hardware properties are not affected by network routing.
Emoji rendering: Unchanged by VPN. Emoji style depends on the OS version and installed font stack.
Use ClaudeSignal as a checklist
The scanner is not an official account outcome predictor and should not be used as a service rules violation guide. It is a transparent checklist for understanding the signals your browser exposes before and after VPN use.
Run the live Claude / Codex region profile scanner
Related reading:
Practical considerations
When evaluating your regional exposure, it is important to consider the full picture rather than focusing on any single signal. ClaudeSignal combines 14 independent signals precisely because no individual signal provides a complete view. The strength of the analysis comes from the convergence of multiple independent data points.
Start by running the scanner to see your current profile, then consider which signals are most relevant to your specific situation. Some users may be primarily concerned about IP-level detection, while others may need to address browser-level signals as well. The key is understanding what is exposed and making informed decisions based on that knowledge.
For a complete view of your regional profile, run the ClaudeSignal scanner and review each signal category. Pay particular attention to any mismatches between your IP-based signals and your browser-based signals, as these inconsistencies are the most informative part of the analysis.