IP purity check
Test your IP as soon as the page opens: network type, native or broadcast, the SpamCop blacklist, time zone, language and WebRTC, plus how to read each result.
How to read the time zone your browser reports, compare it with the exit country, and change it in the system or in DevTools.
JavaScript on a page can read the time zone with Intl.DateTimeFormat().resolvedOptions().timeZone. MDN describes the value as an IANA time zone name, and says the default is the runtime's default time zone when none is specified. IANA names use a region and city form, for example Europe/Brussels.
So by default the page sees the time zone your own computer uses, regardless of which country the proxy exit is in. Changing the proxy does not change the time zone.
You do not need to write code. The browser console is enough.
in Chrome press Control+Shift+J (Command+Option+J on a Mac). The Console panel opens by default.
type Intl.DateTimeFormat().resolvedOptions().timeZone, press Enter, and note the name returned, for example Asia/Shanghai.
use the method in how to check a proxy's IP, country and ISP to see which country the exit IP is actually in.
check whether the console value is a normal time zone for that country. Countries that span several time zones, such as the United States, have more than one reasonable answer; pick the one that matches the city you are testing.
open the IP purity check, which puts the IP location next to the browser's time zone, language and WebRTC result.
When the time zone, the language and the exit country point to different places, the visible effects are usually about display:
Wrong times: promotion countdowns, order cut-offs and publish times are converted with your computer's time zone, so they differ by hours from what a local visitor sees.
Dates, language or prices look different from what you expected: many pages combine language and region settings to choose a date format and currency. If the browser language differs from the exit country, you may see one language with another country's currency.
Test results are hard to compare: when you check pages across regions, a setup that differs from the target region's local settings means screenshots and data do not show what users there actually see.
The goal is simple: make the time zone, the language and the exit country describe the same place. How a platform treats these signals is the platform's own decision, and nothing here is a guarantee.
If you use the same exit country every day, the most reliable fix is the system time zone, because the browser uses it by default.
on a Mac, open System Settings, click General, then Date & Time. Apple's help page says that turning on "Set time zone automatically using your current location" makes the Mac choose the zone from where it is; to set one by hand, turn that switch off first. On Windows and other systems, find the equivalent Date and Time setting.
turn automatic time zone off and pick the zone that matches the exit location.
quit it completely and open it again.
run the command from Section 2 again and confirm the returned value has changed.
If you only want to see how a page behaves for a region, use the location presets in DevTools.
press Control+Shift+P (Command+Shift+P on a Mac) to open the Command Menu, type sensors, choose Show Sensors, and the panel opens at the bottom.
in the Geolocation list pick a preset city such as Tokyo, or a custom location with longitude and latitude.
open the Locations tab in Settings, click Add location, and enter a name, latitude, longitude, Timezone ID and Locale (the official example is New York with America/New_York and en-US). Save it and it appears in the Sensors location list.
the official page presents these presets as a way to override geolocation and does not describe in detail how the time zone a page script reads will change, so run the Section 2 command again and trust the value it returns.
These settings apply only to the current DevTools session and do not change your system settings. For a lasting fix, go back to Section 4.
If you keep a separate browser profile for each account, such tools usually have their own time zone, language and WebRTC options. Set the time zone and language to match the exit country of the proxy that profile uses, and follow the tool's own documentation for the exact option names. For connecting the proxy, see browser profile proxy setup; for plain Chrome see Chrome proxy setup.
WebRTC is the other step people overlook. RFC 8828 says WebRTC traffic should not be sent through proxy servers by default; when direct internet access is allowed, WebRTC's STUN checks do not go through the proxy and can reveal the client's public IP; only the mode that forces the proxy sends WebRTC media through it. Use the WebRTC leak test to see whether the browser exposes an address outside the proxy, and test again after changing a setting.
| Item | Where to check | What to change |
|---|---|---|
| Page time is hours off from the target region | Run the time zone command in the console | Set the system time zone to the exit country's, or test temporarily in DevTools |
| Date format, language or prices differ from what you expect | The console value, compared with the exit country | Align the browser language and system time zone with the exit country |
| WebRTC test shows an address outside the proxy | WebRTC leak test | Adjust WebRTC in the browser or profile tool, then test again |
| The exit is not in the country you expected | Check proxy IP location | Re-check that host, port, username and password were entered correctly |
| Time is unchanged after switching proxy | The console value did not change | The time zone does not follow the proxy; change it manually as in Section 4 |
The time zone read comes from MDN, the DevTools steps from Chrome's official documentation, the system setting path from Apple's help page and the WebRTC behavior from RFC 8828.
If you want an exit address that stays fixed for the lease term to go with a fixed time zone and language, see Proxy302's static ISP proxies: the same IP does not change during the lease, so the time zone only needs to be set once.
Proxy302 rents static ISP IPs that stay fixed for the lease term, so you set the time zone and language once for that exit.
Check the exit country with the location guide, set the matching time zone, and confirm it in the console.
Open the product page that fits (static ISP, rotating residential or the ISP for AI subscriptions) and pick the region, traffic or lease term, and quantity. For per-IP products also choose HTTP or SOCKS5.
After the proxy is generated, open My assets and copy HOST, PORT, USERNAME and PASSWORD.
Open https://ipinfo.io/json through the proxy and check that the country and org fields (ASN and organization) are what you expected.
Then compare network type and native or broadcast on the IP purity check page. Two tools disagreeing is normal; go by your actual use.
Rotating residential starts at US$1.50 per GB on the Budget line and US$5 per GB on the Premium line; larger packages are cheaper per GB, and purchased traffic has no expiry. A static ISP IP is US$0.50 for one day or US$7.99 for 30 days, the same in every country, fixed for the lease. A datacenter IP is US$0.25 for one day or US$3.99 for 30 days. Stock changes daily, so go by the order page. The smallest purchase is 1 GB of traffic or one IP for one day. Changing IP does not lift a restriction or raise a limit; what happens to an account is up to the platform.
| Item | Price | Protocols | Locations |
|---|---|---|---|
| Rotating residential | From US$1.50 per GB (Budget line); US$5 per GB (Premium line); lower per GB in larger packages | HTTP, SOCKS5 | 195+ countries and regions; state and major city on lines that support it (small towns and some connections exit at country level; no city level in Russia and Singapore) |
| Static ISP, per IP | US$0.50 for 1 day, US$7.99 for 30 days, the same in every country | HTTP or SOCKS5, chosen per IP | 30 countries on the order form; stock changes daily |
| ISP for AI subscriptions | Per 30 days: Claude 15 PTC, GPT / Grok 10 PTC, Gemini 8 PTC | HTTP or SOCKS5 | Claude: US, UK, DE, JP. GPT / Grok: US, UK, FR, JP, KR. Gemini: US, UK, FR, JP |
| Datacenter, per IP | US$0.25 for 1 day, US$3.99 for 30 days | HTTP or SOCKS5, chosen per IP | 8 countries |
Prices are in PTC, paid from the wallet; 1 PTC = US$1. There is no free trial: the smallest purchase is 1 GB of rotating residential traffic or one IP for one day. Checked on 9 November 2026.
By default the page reads the runtime's default time zone, which is your computer's, not one tied to the proxy exit IP. To make the displayed time match the exit country, change the system time zone or the time zone in your browser profile.
Quit the browser completely and open it again, then run the console command. If the returned value is the target time zone, the change has taken effect.
Not necessarily; the language should suit how you work. But if you are testing how a page looks in a region, setting the language to that region's shows the date format and currency a local visitor would see.
No. It applies only to the current DevTools session. For a lasting change, edit the system time zone.
Both check whether the browser environment agrees with the exit IP. The time zone decides the local time a page shows; WebRTC decides whether the browser exposes another address outside the proxy. Check both together.
Official documentation · Confirmed on:
Read on 9 November 2026: timeZone is an IANA time zone name and the default is the runtime default time zone.
Official documentation · Confirmed on:
Read on 9 November 2026: DevTools opens with Control+Shift+J or Command+Option+J (Mac), the Console opens by default, and the Size column is described as the resource amount transferred over the network.
Official documentation · Confirmed on:
Read on 9 November 2026: the Sensors panel opens from the Command Menu with Show Sensors; the Geolocation list offers preset cities such as Tokyo, a custom location with longitude and latitude, or location unavailable. The page does not cover time zone ID or locale.
Official documentation · Confirmed on:
Read on 9 November 2026: in Settings, Locations tab, Add location takes a name, latitude, longitude, Timezone ID and Locale (example: New York, America/New_York, en-US); the saved preset appears in the Sensors location list. The page does not state how the page-visible time zone changes.
Official documentation · Confirmed on:
Read on 9 November 2026: open System Settings, General, Date & Time; "Set time zone automatically using your current location" makes the Mac choose the zone by its location.
Official documentation · Confirmed on:
Read on 9 November 2026: by default WebRTC traffic should not be sent through proxy servers; when direct internet access is allowed, WebRTC STUN checks do not go through the proxy and can reveal the client public IP; only the force-proxy mode (mode 4) requires WebRTC media to be proxied.
Product observation · Confirmed on:
Product facts file of the site, checked 9 November 2026 against the console, the backend and the price table: products, prices in US$ (1 PTC = US$1), lease terms, protocols and ports, countries, quantity limits, no free trial.
Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.