IP2World

The product pages distinguish residential, mobile, and ISP proxies, with mobile targeting by country and carrier. The vendor says its residential proxies cover more than 50 countries; its homepage gives country targeting for residential lines.

IP2World describes its residential proxies as suited to use cases that check whether visitors appear to be real households. That is the vendor’s stated use case, not independent validation of proxy sourcing or performance. Residential, mobile, and ISP SOCKS5 with sticky sessions are also advertised across 10+ networks, though the SOCKS5 guide limits the service to TCP connections.

Rotating residential traffic is billed by the gigabyte, while static and per-IP products are billed by address, according to IP2World’s FAQ, checked 2026-10-31. The vendor says proxy lines and sessions are not billed separately.

The provider gives different figures for the minimum purchase and balance top-up; these are distinct terms in its pages, not interchangeable amounts. The homepage lists a minimum starting purchase of one gigabyte for $2. The FAQ describes the smallest purchase as one gigabyte or a $5 balance top-up. The pricing page says balance top-ups start at $5.

IP2World’s pricing page states that traffic does not expire, while its Terms describe allowances as non-subscription purchases that do not renew automatically. The Terms also say cards are not accepted.

For payment, the homepage says cryptocurrency is processed instantly and card payments are not yet available; the FAQ lists USDT, BTC, ETH, and LTC, with cards unavailable. The residential page displays an order example charging $40.00 for 20 GB, a listed example rather than a general rate.

A residential line receives a new address on each request unless the user selects a sticky session. The FAQ says a sticky session holds the address for the length of that session; without a session identifier, rotation resumes on every request. Country targeting can be set through the username and session settings, according to the FAQ.

IP2World says users can authenticate through IP whitelisting or a username and password, and that residential traffic supports HTTP(S) and SOCKS5 with the same credentials. Proxy lines are generated in the dashboard; the vendor says its dashboard and API can retrieve proxy lists.

The Terms say metering counts network traffic, including protocol overhead, rather than only traffic measured by the customer’s own client. Check how the application’s traffic accounting compares with that network-level meter.

Before relying on a SOCKS5 connection, ask which traffic types the service relays and whether the intended application requires UDP. The setup page describes SOCKS5 as capable of TCP and UDP routing, but the guide says IP2World’s service handles TCP only and does not relay UDP; the FAQ likewise says it refuses UDP ASSOCIATE requests.

Also check how the application uses a proxy and which authentication method its configuration supports. In general, a provider’s protocol label does not by itself establish compatibility with every application or traffic type.

The guide says iOS built-in Wi-Fi proxy settings accept HTTP proxies only, and it notes native SOCKS5 support in Telegram on iOS. For Windows, the guide recommends per-app proxying or a local SOCKS forwarder. Confirm the application’s requirements against the stated TCP-only service condition before setting up a workflow.

The refund policy says customers who change their minds without consuming traffic may receive a full refund within 7 days. Consumed traffic is not refundable, and accounts closed for Acceptable Use Policy breaches are ineligible.

The residential plan excludes city and ASN targeting. The policy also excludes website proxy detection, customer misconfiguration, slower-than-home speeds, and expectations of city or ISP-level targeting as service failures. It further says a site blocking proxies is not grounds for refunding a large allowance bought without testing.

Cryptocurrency refunds are sent as a new outbound payment in the same asset, with network fees deducted; the policy says the refund returns the same amount of cryptocurrency, not the same dollar value. The policy also states that cryptocurrency payments have no chargeback mechanism. Several details are missing; they are listed under What we could not confirm.

IP2World’s product pages describe controls that matter when a workflow needs country selection, persistent sessions, or different authentication methods.

• Residential lines can be set to a country, and sticky sessions hold an address for the session length.
• Authentication options are IP whitelisting or username and password; residential HTTP(S) and SOCKS5 use the same credentials.
• Proxy lines are generated in the dashboard, and the vendor says its dashboard and API retrieve proxy lists.
• Static ISP, mobile 4G/5G, and datacentre products draw from the same balance, according to the pricing page.

IP2World’s stated residential controls fit workflows that need country targeting and request-by-request rotation or sticky sessions.

Mobile lines add country and carrier targeting, while the residential plan excludes city and ASN targeting. Buyers should also account for the policy’s exclusions around proxy detection and slower-than-home speeds.

If the application needs UDP, the FAQ’s TCP-only SOCKS5 condition is a material constraint. Check the required location, protocol, and session behavior against the product terms before relying on a route.

In general, compare proxy type and billing unit first, then check targeting granularity, session behavior, supported protocols, authentication, refund terms, API access, and support arrangements. The useful comparison is the fit between those terms and the intended application, not a proxy label alone.

Which payment methods does IP2World list?

IP2World lists cryptocurrency options including BTC, USDT, ETH, and LTC; the residential page marks card payment as coming soon. The homepage separately says cryptocurrency payments are processed instantly and that cards are not yet available.

How does rotation behave without a session identifier?

Without a session identifier, IP2World says residential rotation resumes on every request, assigning a new address each time. Selecting a sticky session holds an address for the session length; this is the stated distinction between request-based rotation and session persistence.

Which authentication options does IP2World state?

IP2World lists IP whitelisting and username-and-password authentication. The FAQ says residential HTTP(S) and SOCKS5 traffic use the same credentials, so check which option the application can supply before configuring its proxy connection.

How are proxy lines retrieved?

The vendor says proxy lines are generated in the dashboard and that proxy lists can be retrieved through the dashboard and API. It also says delivery to the dashboard follows on-chain payment confirmation; if the balance has not appeared within one hour, customers can contact support.

What does the refund process require?

IP2World says customers can email refund requests with an order reference and, for service failures, a description of what happened. The vendor states that it responds within 3 business days and pays approved refunds within 7. Its policy separately sets eligibility conditions, including the rule that consumed traffic is not refundable.

Which company operates IP2World?

IP2World’s Terms identify HONGKONG LINGYUN NETWORK MDT INFOTECH LIMITED, registered in Hong Kong, as the operator. The homepage says the current service operates under new ownership. These are statements on the vendor’s own pages, rather than independent verification of the company’s operating arrangements.

Fits if per-gigabyte rotating traffic, country-level targeting, and the available session controls match the intended workflow.

Probably not if city or ASN targeting is essential, or if the application requires UDP relay.

Main risk… assuming protocol compatibility or refund eligibility without checking the stated TCP-only limit and policy conditions.