How to check a proxy: IP, DNS, WebRTC and speed
A proxy can connect just fine and still expose your real IP through WebRTC or DNS. Here's how to check a proxy in about ten minutes: IP and geo, carrier, leaks, speed and rotation.
- Real carrier IPs
- HTTP(S) and SOCKS5
- IP change via link
- 2-hour free test
Recommended proxies
How to check a proxy: external IP and location
Start with the basics: make sure websites see the proxy's IP, not yours. Open any IP check service in a browser that's running through the proxy, then compare the result with your address without the proxy — they should differ.
You can do the same from the command line with curl. Plug in your details and the address of any service that returns your IP:
curl -x http://LOGIN:PASSWORD@HOST:PORT https://IP_CHECK_URL
What to look for:
- the IP is different from your home or office address;
- the country matches what you ordered;
- the city may be off — IP databases often place mobile IPs where the carrier registered the address block, not where the modem actually is. Different services can show different cities for the same IP, and that's normal.
If the IP didn't change, make sure the proxy is enabled in the app you're testing with and that the protocol (HTTP or SOCKS5) is set correctly.
ISP and ASN: does it show a mobile carrier
Every IP belongs to a network — an autonomous system (ASN) registered to an organization. Most IP check services show an ISP, organization or ASN field, which tells you what kind of address you have:
- mobile proxy — the ISP is a mobile carrier, such as T-Mobile, Verizon, AT&T or Megafon;
- residential proxy — a home internet provider;
- datacenter proxy — a hosting company, which is expected for that type.
Some services also show a connection type (mobile, residential, hosting) or flag the IP as a proxy. Each database classifies addresses its own way, so go by the ISP name and ASN rather than a single label.
DNS leaks
Before loading a site, your device looks up its IP with a DNS query. If that query skips the proxy and goes straight to your ISP's DNS servers, the site may see a mismatch: an IP from one country, a resolver from another. That's a DNS leak.
To check, open any DNS leak test through the proxy and run the extended test. Your home ISP's DNS servers shouldn't appear in the list.
What affects the result:
- HTTP proxy — the browser hands the hostname to the proxy, which does the lookup, so browsers usually don't leak DNS here;
- SOCKS5 — depends on the client, which may resolve names itself or pass them to the proxy. In curl, use
socks5h://instead ofsocks5://to resolve through the proxy; - system proxy — apps that ignore it go directly to both DNS and the web.
Antidetect browsers usually have a separate DNS setting. Hide Ninja, LTEBoost's own antidetect browser, runs profiles without DNS leaks.
WebRTC leaks in the browser
WebRTC powers voice and video calls inside the browser. To set up a call, it discovers your device's network addresses and can do so around the proxy, over UDP. The result: a site sees the proxy IP in normal requests but your real IP via WebRTC.
To check, open any WebRTC leak test through the proxy. It lists the addresses your browser exposes. You should see the proxy IP or nothing at all — never your real public IP.
How to fix it:
- in an antidetect browser, pick the WebRTC mode that replaces the address with the proxy IP, or disable WebRTC for the profile;
- in a regular browser, use an extension that restricts WebRTC, or the browser's own setting if it has one.
Speed and latency
Test speed with a speed test service in a browser running through the proxy, or by downloading a file. For latency, curl prints connection time and total response time in seconds:
curl -x http://LOGIN:PASSWORD@HOST:PORT -o /dev/null -s -w "%{time_connect} %{time_total}\n" https://IP_CHECK_URL
Compare the numbers with your plan, not with your home connection:
- shared pool — up to 1.6 Mbit/s per client (Czechia 2, Georgia up to 5). That's the plan limit, not a fault;
- dedicated modem — typical averages are 10–15 Mbit/s in Russia, 20–25 Mbit/s on US Verizon and AT&T, 30–60+ Mbit/s on 5G;
- arbitrage multiport — up to 2 Mbit/s, up to 4 Mbit/s in the USA.
Mobile network speed varies through the day, so measure a few times. Latency depends on distance: a modem on another continent will always respond more slowly than one nearby.
Checking IP rotation
If your plan includes rotation, confirm it behaves the way you expect:
- shared pool — check the IP, wait more than 2 minutes (3 in Kazakhstan) and check again; it should change on its own;
- dedicated modem — open the IP change link, wait 3–6 seconds for the reconnect (8–10 on Verizon) and check the IP. If you set a timer, check after the interval;
- arbitrage multiport — send several requests in parallel; each new connection should get its own IP;
- pay-per-GB — in sticky mode the IP stays the same; in random mode it changes on every request.
Test an LTEBoost proxy on your own task
The surest way to know whether a proxy fits is to try it on real work. Most LTEBoost mobile proxies come with a free 2-hour test through the Telegram bot — run through the checklist above and see the results for yourself.
- Shared US pool and shared Russia pool — 10,000+ carrier IPs, rotating automatically every 2 minutes.
- Dedicated modem — one user per modem, IP change via link or timer, HTTP(S) and SOCKS5.
- Mobile proxies per GB — pay only for traffic, pick a country, sticky or rotating IP. There's no free test, but you can start with a 1 GB package.
If a check fails, message support and we'll help sort out the setup. Everything else is in the proxy catalog.
FAQ
How can I tell if a proxy is really mobile?
Open an IP check service through the proxy and look at the ISP or ASN field — it should name a mobile carrier. Some services also show the connection type.
Why does the IP check show the wrong city?
IP databases often tie mobile IPs to where the carrier registered its addresses, and different services return different cities. Go by the country and carrier.
What if WebRTC shows my real IP?
In an antidetect browser, switch WebRTC to replace the address with the proxy IP or disable it. In a regular browser, use an extension that restricts WebRTC.
Why is a shared proxy slower than a dedicated one?
A shared pool is capped at up to 1.6 Mbit/s per client. A dedicated modem gives you the whole channel, for example 20–25 Mbit/s on average for US Verizon and AT&T lines.
Can I check a proxy before buying?
Yes, mobile proxies have a free 2-hour test via the Telegram bot. Pay-per-GB plans have no test, and the US dedicated modem and 5G USA have a paid 24-hour test.
Start a free 2-hour test and run the checklist: IP, carrier, DNS, WebRTC, speed and rotation.
