Pixelscan Checks With a Mobile Carrier Line

Pixelscan is a free checker that loads in a browser and reports whether that browser looks internally consistent. It compares the network location with the browser's time zone and language, looks for signs that fingerprint values have been altered, and reports whether it thinks a proxy is in use. People who manage several legitimate browser profiles, such as agencies with separate client workspaces, use it as a quick health check. When one of those profiles runs through a SpoofProxies line, the page gives a readable summary of whether the profile and the network agree. Here is how to interpret it.

The two halves of the report

Pixelscan splits its answer into the network side and the browser side. On the network side it shows the address, the provider, a location and whether the address looks like a proxy. On the browser side it shows the user agent, operating system, screen, graphics details, fonts and whether the fingerprint appears natural or masked. The headline verdict is about whether the two halves line up.

On a carrier line the provider should be AT&T, T-Mobile or Verizon and the location should be in the metro region of the line. If the provider reads as a hosting company, stop and fix the proxy settings before reading anything else, because the browser is not using the line.

Consistency is the whole game

The checks that most often fail are the simple ones. The browser's time zone is compared with the time zone expected for the address. The browser's language list is compared with the country. The WebRTC check looks for a local or public address exposed outside the proxy. Each of these is a contradiction a real phone user in that city would not produce. Fixing them is ordinary configuration: set the profile's time zone to the line's metro, choose a US English locale, and make sure WebRTC either uses the proxy or does not leak a second address.

When you move a line to a different metro from the dashboard, update the profile at the same time. A profile that says Phoenix while the line now exits in Miami will show up as inconsistent immediately.

About the proxy line on the report

Pixelscan's proxy verdict relies on address databases and, depending on the version, on connection timing hints. On a carrier address the database part can come back positive because the address is shared across many devices through carrier-grade NAT, and some of them may have been proxies at some point. That describes the pool address. It is worth reading next to the provider line, which on our lines names a real carrier, and the connection type, which should be mobile.

It is also worth knowing that Pixelscan is not any particular website. A proxy verdict on Pixelscan does not mean a platform you use has made the same judgement, and a clean verdict does not mean a platform will not ask you to verify.

Masked fingerprints and what we do not cover

The browser half of the report often flags masked or inconsistent fingerprints when a profile has been heavily modified. That part has nothing to do with the network and nothing to do with us. Our lines supply a genuine US mobile route; they do not change canvas, graphics, fonts or any browser property. We also do not advise on altering fingerprints to impersonate other devices. For legitimate profile management, the calm approach is the least modified one: a normal browser, a normal device, a matching time zone and language, and the line.

A good habit for teams

Run Pixelscan once when a profile is created and once after any change to its line or metro. Record the provider, location and the consistency verdict with the date. Then leave it alone. Checking before every session produces noise, because the carrier pool address changes when you rotate and some pool addresses carry labels. For signed-in work keep a sticky session and a single metro per profile. Our plans come with unlimited data and unlimited rotations, so the occasional diagnostic rotation is free, but stability is what keeps a signed-in profile calm.

Setting up a Pixelscan proxy on SpoofProxies

1. Add a line in the metro you need and copy its credentials.
2. Open the browser profile you will use and set its time zone and language to that metro.
3. Configure the profile with the line's host, port, username and password.
4. Visit Pixelscan and confirm the provider names the carrier and the location matches the metro.
5. Resolve any time zone, language or WebRTC inconsistency the report lists.
6. Record the result and recheck only after a change to the line or profile.

Pixelscan proxy questions