Buying a proxy is only half the job. Before you trust an account to it, the proxy must be checked: it can easily be given away by the wrong ASN type, a high fraud score, DNS and WebRTC leaks, or a mismatch between geolocation and timezone. In this article — a practical checklist of metrics and tests that distinguish a working proxy from one that will burn an account on the very first login.

ASN type and proxy class

The first thing any antifraud system checks is who owns the IP. The ASN determines the address class.

  • Hosting/Datacenter ASN — clouds and data centers. Practically unusable for social networks and ad platforms: a legitimate user does not go online from a data center.
  • Residential ASN — home providers. More neutral, but pools accumulate in databases.
  • Mobile ASN — mobile carriers. The most trusted class: CGNAT and a real mass of subscribers stand behind it.

You can check the type via ASN/ISP lookup services. For a mobile proxy the correct result is mobile and a telecom carrier ASN, not hosting.

Fraud score (IP risk score)

Specialized services rate the "risk" of an IP on a scale (often 0–100). The score is affected by ASN type, the address's history, proxy/VPN markers, and blacklist hits.

  • Low score — the IP looks like an ordinary user and passes checks calmly.
  • High score — the address is flagged as risky: extra captchas, registration denials, shadow restrictions.

Thanks to CGNAT and a trusted ASN, mobile IPs get a low fraud score by default — that is their key advantage. Data-center addresses are almost always "red."

Speed, ping, and stability

Channel quality is measured by three values.

  • Ping (latency) — the delay to the target host. The lower, the more responsive the sessions. On mobile channels ping is higher than on a data center — that is normal.
  • Throughput (speed) — bandwidth. Modest values are enough for account work; for scraping and media it matters more.
  • Uptime and stability — the percentage of successful connections and absence of drops. An unstable proxy breaks sessions and triggers re-verification.

Leak tests: DNS leak and WebRTC

Even a "clean" IP is useless if the real address leaks alongside it. Two mandatory tests before launching an account.

DNS leak test

Checks whose DNS resolves your domains. If the results show your real provider's DNS, queries are going outside the tunnel and your geolocation and ISP are exposed. DNS must go through the proxy (remote DNS) or a consistent server.

WebRTC leak test

WebRTC over UDP can reveal local and public IPs bypassing the proxy. The test should show only the proxy IP. If the real address is visible, WebRTC in the browser/antidetect must be disabled or spoofed.

Geolocation and timezone match

Antifraud checks the consistency of parameters. Common anomalies:

  • IP and timezone do not match — for example, an IP from one country with a system timezone from another. A clear proxy signal.
  • IP geolocation contradicts the browser's language/locale.
  • DNS exit in a different country than the IP itself.

A quality proxy provides a stable geo-binding that is easy to align with the profile's timezone and locale.

A practical verification checklist

  • ASN type — mobile, a telecom carrier ASN, not hosting.
  • Fraud score — low.
  • IP geolocation matches the declared country.
  • DNS leak test — passed, the proxy's DNS is shown.
  • WebRTC leak test — passed, only the proxy IP is visible.
  • Profile timezone synchronized with the IP geolocation.
  • Ping and stability acceptable for the task.
  • SOCKS5 tunnel works, authentication succeeds.

turbon.rent infrastructure

turbon.rent mobile proxies pass these checks out of the box: physical SIM cards of real carriers in GoIP/Simpool gateways, 17 countries, a mobile ASN and CGNAT (low fraud score), IP change on demand via API, and SOCKS5 for a clean tunnel with correct DNS.

Frequently asked questions

What fraud score is considered acceptable?

The lower, the better; aim for the lower part of the scale. Thanks to a trusted ASN and CGNAT, mobile IPs usually show low risk, unlike data-center addresses.

Why does a mobile proxy have higher ping than a data center?

It is a feature of the radio channel and routing through the carrier network. For account work such ping is not critical — ASN trust and the absence of leaks matter more.

Is it enough to check only the IP and fraud score?

No. Without DNS leak and WebRTC tests and without checking the timezone, even a "clean" IP can give you away. Go through the whole checklist before launching an account.

Bottom line: proxy quality is a combination of ASN type, a low fraud score, a stable channel, the absence of leaks, and a consistent geolocation. Connect turbon.rent mobile proxies on physical SIMs in 17 countries with SOCKS5 and IP rotation via API, and for registration on clean numbers use turbon.rent OTP activations.