本文へスキップ

このページはまだお使いの言語では用意されていません。英語の文章をご覧いただいています。

Glossary

Mobile proxy

It is bought for one property above all others: the address changes on demand, and it is shared with strangers while you hold it. Both halves of that are the point and the price.

A mobile proxy is an exit address from a carrier network, shared at the same moment with the real phones on that same tower.

Where the address sits

Carriers hand one public address to many subscribers at once, so a single mobile address stands in front of a crowd of ordinary phones.

That crowd is why blocking such an address is expensive for a platform. It is also why the address is never yours alone.

  • Shared while you use it

    Real people browse from the same address at the same time, and nothing they do is under your control.

  • Short lived by nature

    A modem reconnects and the carrier hands out a different address, sometimes without anybody asking.

  • Priced by traffic

    Like a household line, the meter counts bytes, and a shared channel is slower than a rack.

Why it changes so often

Sellers deliver a link along with the address: fetch it and the modem drops its connection and comes back with a new one.

The link is the whole mechanism. Without one, a mobile address changes when the carrier decides and not when you do.

How a change is made here

The link is kept on the saved entry instead of in a chat with the seller, and it is fetched over your own connection rather than through the channel being restarted.

  1. 1

    By hand

    The address is measured before the command and again after, so you read what happened rather than what was asked.

  2. 2

    Before a launch

    A profile can ask for a fresh address every time it opens, and it does not open if the change fails.

  3. 3

    On a schedule

    An address changes on its own while the profile works, counted from the moment that profile opened.

  4. 4

    Across a pool

    Many profiles take different addresses from one list instead of crowding onto the first entry.

When a change cannot be confirmed

The app asks the address again a few seconds after the command, and a modem still reconnecting answers nothing. That state is reported as it is, because claiming a change nobody measured would be a claim we cannot back up.

The address the library already knew is kept rather than erased, and the entry is not marked dead. A record is updated only when a check actually answers.

Often confused with

  • Residential proxy

    A fixed household line. It changes rarely, and it is not shared with a crowd on a tower.

  • ISP proxy

    A static address with a consumer registration, bought for exactly the opposite reason.

  • A phone shaped profile

    A device identity: screen, touch points, platform. That is what the browser reports, not where it leaves from.

  • A rotating residential pool

    Rotation done by the seller's pool rather than by a modem, with a new address per request.

What this does not do

  • It cannot force a modem to take a new address. The command belongs to the seller, and a seller enforcing its own rate limit answers and changes nothing.
  • It does not confirm what it could not measure. A change the app could not read back is reported as unconfirmed rather than as success.
  • It does not clean the address for you. The crowd behind it includes people whose behaviour you never see, and their history arrives with the address.
  • We do not sell proxies. The provider directory inside the app records an intent, takes no payment, and puts nothing into your library by itself.

Check it

Everything said above about the product is held by a file and by a stand you can run.

Who changes address and when it is due
apps/desktop/src/lib/proxyRotate.js · apps/desktop/test/proxy-round-robin.js
The seller link is walked and the result is measured before and after
apps/desktop/src/main/main.js · apps/desktop/test/proxy-rotation.js
The link and the login live on the saved entry
apps/desktop/src/lib/proxies.js · apps/desktop/test/proxy-library.js
The exit country is asked through the address itself
apps/desktop/src/lib/exitGeo.js · apps/desktop/test/exit-geo.js

Questions

Why is a mobile address harder to block?
Because it stands in front of many real subscribers at once. Blocking it costs a platform genuine customers, so the bar for doing it is higher.
Should the address change while I am signed in?
Usually not. An account that jumps to another city mid session is the pattern a platform looks for, so a schedule is for work between sessions rather than during one.
What happens if the seller link is missing?
The entry simply has nothing to call, and the app says so instead of pretending. You can add the link to the saved row at any time.
Does the clock follow the new address?
The remembered exit country is dropped when the address changes, so the next launch asks again through the address itself.

Keep the seller link on the address

Save the entry with its change link, and read the address before and after every change.