BlogGuide8 min read

How to test a proxy before you rely on it

A page that loads only proves the tunnel is up. Confirm the exit IP, watch it for an hour, then try a login you can afford to lose.

A laptop showing an IP check next to a closed notebook
Confirm the public IP is the proxy, then wait an hour, before a real account uses the line.

Three answers before a real account

Before you put the Business Manager you cannot replace on a new proxy, you want three answers. First: is the public IP the proxy, or is the browser still using your home line? Second: does that IP stay the same if you do not request a change? Third: can a login you can afford to lose sit on it without an instant lock?

If the proxy will not connect at all, stop here and follow what to check when a proxy will not connect. If you are not sure the browser is on HTTP, read HTTP or SOCKS5 first. A SOCKS address in a browser will fail the tests below in a confusing way.

  1. Confirm the public IP is the proxy. Turn the proxy off once and reload, so you know the browser was using it.
  2. Leave the line alone for an hour. Do not request a new IP. Write down whether the address moved.
  3. If you need to see that you control the change, request one new IP and wait until the dashboard says it finished.
  4. Sign into a throwaway account. Keep the account you cannot replace off this line until that login is uneventful.

A five-minute version, if you cannot wait an hour

Sometimes you cannot give the check a full hour. You can still catch the worst failures in five minutes. Confirm the exit IP is the proxy, browse a handful of ordinary sites, and check the address again. A short look will not catch a sticky timer that expires at thirty minutes, but it will catch a browser that is not using the proxy at all and a line that changes address every few requests.

Treat the short version as a filter, not a pass. If it looks clean, still run the full hour before you put a login you care about on the line. The hour is what separates “not obviously broken” from “actually yours.”

Confirm the browser is really on the proxy

With the proxy on, open a page that prints your public IP. It must not be your home or office address. Write it down. Turn the proxy off and reload. The address should change back to your normal connection. If it does not change, the browser is not using the proxy, and every later test is wasted. Our free IP and leak checker does this on one page.

The usual cause is the SOCKS5 host pasted into a browser. Browsers need the HTTP endpoint. Fix that before you watch the IP for an hour.

See whether the address stays put

Browse a few ordinary websites for an hour. Do not request a new IP. Check the public IP again. If it changed and you did not ask, the line is rotating or shared. That can be fine for a job that wants a fresh address. It is a bad surprise when a login needed the same mobile address for the whole session.

How to tell a pool from a dedicated modem, including what a sticky timer is, is in how to tell if your mobile proxy is shared.

If the address is still the same, you can request a new IP once and wait until the request finishes, then check again. You want to see that a request you made is what moved it. Checking every thirty seconds, or sending a second request while the first is running, makes the result impossible to read.

Then use a login you can afford to lose

Only after the IP behaves, sign into a test account or a low-value profile. Watch for an instant lock, a challenge you never saw on your normal connection, or a session that dies when the IP changes.

If that login is uneventful, the line is worth using for real work. If the address will not sit still, another day on the same shared pool will not make it dedicated. Buy a dedicated modem, or use the pool only for jobs that expect rotation.

A calm test does not bind the website. The same site can still ask for a check later. What you have ruled out is the cheap failure: the wrong exit, an address that moves under you, or a line so noisy that even a spare login cannot sit on it. On our product, one customer has one EU 4G modem. The address stays until you request a new one from the dashboard. When that address has to stay with one social profile, the product page is social media proxies.

What the test does not prove

A clean test does not mean a website will trust the line forever. Mobile addresses get challenged by sites that challenge everybody, and a login can pass today and ask for a check next month with nothing changed on your side. It also does not prove the line is fast or stable under load — it proves the exit and the address behaviour, nothing more.

It does prove the two things you control: that your traffic really leaves through the proxy, and that the address does not move unless you ask. Those are the failures you can prevent before a real account touches the line, and they are the ones that cost the most to discover late.

Is it enough that a website loads?

No. A loaded page only shows that the tunnel is up. You still need the exit address, whether it moves on its own, and a login you can afford to lose.

How long should I watch the IP?

An hour of ordinary browsing, with no IP request from you. A shorter look can miss a sticky timer that expires at ten or thirty minutes.

Should I test with my main account?

No. Use a spare profile first. If the line is shared, or the address flips mid-session, that is the account that should take the hit.

Do I need a special tool for this?

No. A page that prints your public IP is enough. Write the address down, wait an hour without requesting a change, and check again. The only rule is not to move the line yourself while you are watching it.