See which readings Pixelscan and BrowserScan compare, which differences are harmless and which ones mean the proxy is not set up the way you think.
The 3 most common causes of a mismatch
Cause 1: browser values come from your own computer. The time zone a page reads follows your system settings (MDN), and the language list follows the browser's interface language (Accept-Language). A checker compares them with the location of the IP, so a difference is a reading about your device. A traveller without any proxy gets the same difference.
Cause 2: something does not go through the proxy. A WebRTC host or server-reflexive candidate can show your own local or public address, a DNS lookup can go to your own resolver, or the profile you opened simply is not using the proxy. This one is a real setup fault.
Cause 3: the IP itself carries a label. The network may be of type hosting, or the address may be listed as a proxy or on a blacklist. The tool shows that in its Proxy, Anonymous or Blacklist rows, and other checkers may say something different.
IP side: location of the IP. Browser side: your system time zone
Reports your device; it is a fault only if a page shows the wrong time or does not load
Languages and Accept-Language header
The browser's interface and preferred languages
Reports your browser; it does not show a proxy problem
WebRTC and WebRTC STUN
Addresses the browser finds for peer connections
A different public address can mean traffic outside the proxy; see the WebRTC guide
DNS Leak (both tools)
Which resolver answered the lookups
Lookups going to your own resolver mean DNS is not using the proxy path
Proxy, Anonymous, Blacklist
The IP's listing in that tool's data
A flag shows that one database lists the address; check with a second tool
Fingerprint check, authenticity percentage
Many browser readings tested together
The tool's own score; neither tool publishes the rule behind a verdict
Row names read on browserscan.net and the tool list on pixelscan.net on 16 November 2026, with MDN for time zone, Accept-Language and WebRTC. What each tool treats as a warning is not documented on the pages we read.
Step 1: Check the exit before you blame the checker
Run the curl line below and note the IP, country and org (the ASN). Then open the checker in the browser or profile that uses the proxy. The IP it shows must match the curl result; if it shows your own address, fix address, port, protocol and login first.
Write down which row disagrees: IP, time zone, language, WebRTC, DNS, or a Proxy and Blacklist flag. Each has a different cause, so do not treat the whole report as one problem.
Step 3: Fix only the rows that show a real fault
A WebRTC address that is not your exit, or DNS answered by your own resolver, means some traffic skips the proxy. Use the WebRTC guide to see what the browser exposes and where to change it.
Step 4: Leave the device readings alone unless something breaks
Time zone and language describe your computer and browser. Change them only when a page shows the wrong time, loads wrongly or does not open, and then follow the time zone guide.
Step 5: Check the IP on a second tool, then decide
If a Proxy or Blacklist flag appears, compare with the IP purity check. If the IP itself looks wrong for what you bought, open a ticket with the order number. Do not chase a green report: a clean result does not promise any platform will accept the IP.
# Which IP and network does the outside world see through the proxy?
curl -sS -x http://LOGIN:PASSWORD@HOST:PORT https://ipinfo.io/json
# SOCKS5: the h in socks5h also sends the DNS lookup through the proxy
curl -sS -x socks5h://LOGIN:PASSWORD@HOST:PORT https://ipinfo.io/json
Example only: replace LOGIN, PASSWORD, HOST and PORT with the values from My assets. HTTP assets use port 2222, SOCKS5 assets port 3333.
If the warning stays
The checker shows my own IP, not the proxy
Check Check that the browser or profile uses the proxy; check address, port, protocol (HTTP 2222, SOCKS5 3333), login and the system proxy setting
Fix Correct the proxy settings and reload the checker
Stop when Stop and open a ticket with the order number if curl through the proxy does not connect
WebRTC shows a different public address
Check Read the WebRTC guide and see what your browser exposes
Fix Follow the browser or profile setting described there
Stop when Stop if the address stays the same after the change; check that the profile really uses the proxy
Time zone or language rows differ from the IP
Check Check whether any page actually shows the wrong time or fails to load
Fix Fix only a real problem, using the time zone guide
Stop when Stop when pages work; the rows are readings of your own device
Proxy or Blacklist flag appears
Check Check the IP type and run the IP purity check; compare two tools
Fix If the flag stays on a purchased IP, send the order number in a ticket
Stop when Stop after two tools disagree; one database is not a verdict
Two checkers give different results
Check Each uses its own data and scoring
Fix Compare what they agree on: ASN, organization, country
Stop when Stop comparing labels once the network facts match
Using Proxy302 with these checkers
A static ISP IP is a fixed address for the whole lease: 1, 3, 7, 30, 60 or 90 days, US$0.50 for 1 day and US$7.99 for 30 days, the same in every country. You choose HTTP (port 2222) or SOCKS5 (port 3333) at purchase; availability by country is shown on the order page. There is no free trial, so the cheapest test is one IP for one day.
Copy HOST, PORT, USERNAME and PASSWORD from My assets. If the IP does not connect or the network facts look wrong, open a support ticket with the order number and we reissue it. Use one IP per account, never share an account, follow each platform's terms and supported regions, and complete any verification a platform asks for.
What does a proxy mismatch warning on Pixelscan mean?
It means the tool compared readings from your IP with readings from your browser and they point to different places. We found no published rules for Pixelscan, so treat the label as that tool's judgement and find the row that differs.
Not by itself. A time zone or language difference reports your own device. A WebRTC or DNS row that shows another address, or an IP that is your own, does point to traffic outside the proxy.
What is the difference between Pixelscan and BrowserScan?
They are two separate tools with their own rows. BrowserScan lists IP time zone, Accept-Language, WebRTC, DNS leak, Proxy and Blacklist rows plus a fingerprint authenticity percentage; Pixelscan lists a fingerprint check, IP, blacklist, VPN, DNS and WebRTC tools. Their results can differ.
Why does BrowserScan show a time zone different from the IP?
Because the browser time zone follows your system settings, while the IP time zone comes from the IP's location. The difference reports your device; it matters only if a page shows the wrong time or fails.
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.
Read the Pixelscan blog page (pixelscan.net/blog/) on 16 November 2026: it lists Fingerprint Check (verify your browser fingerprint), IP Address Check, IP Blacklist Check, VPN Check, DNS Leak Test, WebRTC Leak Test, Location Info and Bot Verification as its tools. The page does not explain what consistency is tested or how a verdict is reached.
We did not find Pixelscan documentation that states its rules or what its verdict labels require; this guide does not claim to know them.
Read browserscan.net on 16 November 2026: the summary lists Browser, Platform, IP Time Zone, Location, language, Postal Code, ISP, Proxy, Anonymous, Blacklist, DNS Leak, Bot Detection and a Browser fingerprint authenticity percentage; the IP address section lists IP, WebRTC, WebRTC STUN; the software section lists Time Zone Based on IP, Time Zone, Time From IP, Time From Javascript, Languages and Accept-Language header. The page text does not define the values these rows take.
The page text we read did not define the values of its rows.
Read on 16 November 2026: ICE candidates describe network paths a peer can use; a host candidate is the peer's own address, typically a local network address; a server reflexive (srflx) candidate is found through a STUN server and is typically the public address; a relay candidate shows the TURN server's address instead of the peer's.
Read on 16 November 2026: Intl.DateTimeFormat().resolvedOptions().timeZone returns an IANA time zone name; if no time zone is passed in, it is the runtime's default, which follows the current system settings.
Read on 16 November 2026: Accept-Language tells the server which language the client prefers; browsers set it automatically from their user interface language, users can add languages in settings, and it generally lists the same locales as navigator.languages.
Read on 16 November 2026: the as object returns asn, name, domain and type, and type is one of hosting, isp, education, government, business.
Proxy302 product facts and price list
Product observation · Confirmed on:
Product facts file of the site (prices in US$, 1 PTC = US$1, lease terms, protocols and ports, no free trial, failed IPs reissued after a ticket with the order number). Checked on 16 November 2026.
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.