A mobile ASN on a desktop browser

A mobile ASN on a desktop user agent is a coherence problem. The exit says carrier. The browser says Windows, a mouse, a large screen, and Client Hints with mobile: false. Those two sentences can both be true. They do not add up to a phone. MaskWright is desktop profiles only. This page exists so a carrier line is not treated as a handset.

Proxies in an antidetect browser is the pillar. What mobile proxies are is the definition. The rest of the cluster lives under Proxies. Authorized work only.

What the site can see at once

The IP maps to a mobile carrier ASN. Geo may say a city the tower last reported. Carrier-grade NAT means many subscribers share that address. None of that is a device.

The browser, if you left it honest, reports a desktop UA, desktop Client Hints, a screen like a monitor, max touch points at 0, a plugged-in battery, and a GPU that looks like a PC. Fingerprint presets in this product model Windows, macOS, or Linux. mobile: false is in the Client Hints metadata.

A page that cares will join those rows. Carrier IP plus desktop Chrome is a laptop on a phone hotspot, or a desktop behind a mobile proxy product. Both happen in real life. A page that wants a phone will not be talked out of that want by a UA you painted.

We do not ship Android or iPhone emulation. There is no cloud phone. Mobile proxy versus a cloud phone is the product cut. A rented Android is a different machine. A carrier exit on your tower is a path.

Why operators attach a mobile line anyway

Mobile versus residential is an exit-type choice. Some authorized profiles need a carrier street: a brand that already uses a hotspot, a market where residential pools are exhausted, a provider that only sold you mobile. Those are path reasons.

"Look like the app" is not a path reason. The TikTok or Instagram app is not this browser. A mobile ASN will not make the web surface into the app. It will make the web surface a desktop browser on a carrier IP.

We do not sell the line. We will parse HTTP or SOCKS5, including a mobile product, and we will align timezone and language to the exit when the lookup works. We will not flip mobile: true and a 390-pixel screen because the ASN is T-Mobile. That mismatch is a tell.

What I keep honest

UA, Client Hints, screen, and touch stay desktop if the profile is desktop. Timezone and language follow the carrier exit. Geolocation follows the exit country in a boring way. I do not drop a rooftop pin on a CGNAT address and call that a phone GPS.

WebRTC and IPv6 still matter. A house IPv6 next to a mobile IPv4 is two streets. How websites detect proxies is mechanism, not a hide guide. Carrier ranges get listed too. A mobile SKU is not invisible.

https as a type is still an HTTP forwarder. HTTPS versus an HTTP forwarder does not change because the ASN is mobile.

Credentials live in profiles.json, AES-256-GCM at rest. The per-profile tree is not encrypted. A mobile password is still a password.

When the mismatch is acceptable

It is acceptable when the authorized work is a desktop site and the path happens to be a carrier: a hotspot you own, a mobile proxy you bought for the street, a travel SIM on a USB modem. Laptops on LTE exist. The story is PC on cellular, not iPhone.

It is not acceptable when you promised a client a cloud phone and delivered this app plus a mobile username. It is not acceptable when last week's session was a residential desktop story and this week's is a carrier IP with a painted mobile UA. That is a new device circus.

If the site requires the official app, use the official app on a device you own. Do not ask a Windows profile to be that device.

FAQ

Does a mobile ASN make MaskWright a phone? No. Desktop profiles only. No cloud phone.

Should I spoof a mobile UA on a carrier exit? I do not. Keep the browser a desktop browser if the host is a PC.

Is a laptop on LTE a mismatch? No. That story is coherent: PC on cellular.

Attach a carrier line if the path needs it. Keep the browser a desktop browser. Name the mismatch so nobody on the desk calls it a phone.