The time zone is one line of JavaScript: Intl.DateTimeFormat().resolvedOptions().timeZone returns an IANA time zone name, by default the one your system uses. The language list is navigator.languages, an array of your preferred languages, most preferred first, and the Accept-Language header on every HTTP request generally lists the same locales. Some browsers add language-only fallback tags, and Safari and Chrome’s incognito mode may list only one language. WebRTC is the exception to a proxy: RFC 8828 notes that its connectivity checks do not go through one.
The IP side is just as visible. BrowserLeaks’ IP page shows the time zone and local time that belong to your IP next to your browser’s own values, and runs IPv6, WebRTC and DNS leak tests. Anthropic does not say whether Claude compares any of these. The point is that any site can, so a contradiction you did not intend is worth removing.
Pick the supported country you are physically in and use Claude from, and get your address there before anything else. If you already are in that country on your normal connection, you have little to change.
Read what the web sees
With your connection running through the proxy, open the BrowserLeaks IP page and note the time zone it assigns to your IP. Open its JavaScript page in the same browser and note the time zone and languages your browser reports.
Expected result The two time zones usually differ only if your computer is set to another country’s clock.
Set your computer’s time zone to the one reported for the IP: on Windows, Settings → Time & language → Date & time; on macOS, System Settings → General → Date & Time. A phone has its own setting.
Expected result Reload the BrowserLeaks JavaScript page: the browser time zone now equals the IP’s.
Choose languages you actually read
Set the browser and system languages to the ones you read. There is no need to switch everything to the local language: a Chinese or Russian browser on a US address is ordinary among expats and travellers. The contradiction to remove is the accidental one, such as a clock from another continent.
Before continuing Do not fake an identity or a place you are not in. This guide is about removing mistakes, not about presenting a false location.
Check again after every change
Run the same two pages after changing the IP, the browser or the operating system, and keep a note of the date and the result.
Leaks that undo the match
The IP page shows your proxy, but the WebRTC test lists another public address
Check WebRTC’s connectivity checks do not go through the proxy; RFC 8828 warns they can reveal the client’s public address unless the browser routes media through the proxy too.
Fix Use the WebRTC setting of your browser or antidetect browser profile, then repeat the BrowserLeaks WebRTC test.
Stop when If the test still shows an address you do not recognise, stop using that profile for Claude until it is fixed.
The DNS test lists your home provider’s resolvers
Check With a socks5:// proxy your own computer resolves hostnames; socks5h:// or an HTTP proxy resolves them through the proxy.
Fix Use socks5h:// in command-line tools, or an HTTP proxy, and test again.
The IPv6 test shows an address while the proxy is IPv4 only
Check Your computer may be using IPv6 outside the proxy.
Fix Turn IPv6 off for the connection you use, or use a client that routes it, then test again.
Payment: the billing country has to be real and consistent
Anthropic’s card-declined article is specific. The billing address on your payment method must match the address your bank has on file, and even a missing accent or a misspelled street can cause a decline. You should check the list of supported billing locations, and the billing address must match the payment method’s country of origin. The article does not mention VPNs or IP-based checks.
The Usage Policy forbids stolen, fraudulent or unauthorized payment methods, so use your own card, in your own name. Subscriptions bought through an app store follow that store’s terms.
Your phone number belongs to the same picture: sign-up needs a real number from a supported location that can receive texts. VoIP, Google Voice, app-made numbers and landlines are refused, one number verifies at most three accounts, and a verified number cannot be changed.
Does my card need to come from the same country as my IP?
Anthropic requires the billing address to match the bank’s record and the card’s country of origin, and the country to be a supported billing location. It does not say the card country must equal your IP country, but keeping them consistent is the simplest course.
Read on 29 October 2026: navigator.languages returns an array of the user’s preferred languages as BCP 47 tags, most preferred first; the Accept-Language header in every HTTP request generally lists the same locales; some browsers add language-only fallback tags, and for privacy Safari (always) and Chrome’s incognito mode may list only one language.
Read on 29 October 2026: the page lists IP address, country and city, ISP and organization, network (ASN), usage type, the time zone and local time that go with the IP, an IPv6 leak test, a WebRTC leak test, a DNS leak test, TCP/IP, TLS and HTTP/2 fingerprints and the HTTP request headers. Its separate JavaScript page lists the browser’s time zone (Internationalization API) and the language values (locale, language and languages).
WebRTC’s connectivity checks do not go through a configured proxy and can reveal the client’s public IP address unless the browser is told to route media through the proxy as well.
Read on 29 October 2026: use by persons while physically located in an unsupported region is not supported; the policy also covers entities majority-owned or controlled by persons or entities in unsupported regions. The page does not mention VPNs, proxies or IP addresses.
The page shows an effective date of 12 November 2026.
Read on 29 October 2026: the billing address on the payment method must match the address your bank has on file, and even small differences such as a missing accent or a misspelled street name can cause a decline; check the list of supported billing locations; the billing address must match the payment method’s country of origin. The article does not mention VPNs or IP-based location checks.
Read on 29 October 2026: only users physically located in a supported location can create and use Claude accounts; VoIP numbers, Google Voice, numbers created in apps and landlines cannot be used; one number can verify at most three Claude accounts; a verified number cannot be changed.
Read on 29 October 2026, account and platform integrity section: no using a different account, such as a newly created one, to continue after a ban, and no giving access to a person who was banned; no coordinating malicious activity across multiple accounts or creating multiple accounts to avoid detection; no automation in account creation; no stolen, fraudulent or unauthorized payment methods; no reselling, proxying or otherwise providing access to Claude through unauthorized means.
The version on the site shows an effective date of 12 November 2026.
Read on 29 October 2026. Ban reasons listed: repeated violations of the Usage Policy, account creation from an unsupported location, Terms of Service violations. Users are warned when Anthropic believes their prompts break the policy; for API customers the warnings are tied to thresholds across the whole API account. The appeal form opens only after you log in at claude.ai with the banned account; banned Free, Pro and Max users can still export their data (possibly restricted, depending on the violation) or delete the account. The article does not mention VPNs or IP addresses and says response times are longer than normal.
Ready to try it?
Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.