Residential Proxy Service with Real Home IPs

A residential proxy routes your traffic through a real home broadband connection, so the target site sees an IP address assigned by an ISP to an ordinary household rather than an IP owned by a data center. IPLight operates a dynamic residential pool aggregated from multiple residential network providers, with country, state and city targeting, per-request rotation or sticky sessions, billed by the gigabyte you actually use.

What makes residential IPs different

Every IP address belongs to an autonomous system. Data-center ranges are registered to hosting providers: the ranges are public, and the same subnets are shared by thousands of crawlers and scanners, so a risk engine can classify them as automation from the ASN alone.

Residential IPs are registered to telecom carriers, cable operators and fiber providers. They sit on real subscriber lines in real neighborhoods. Combined with a large pool and low reuse per IP, requests look like ordinary browsing, which is why residential proxies remain the default choice for e-commerce, social platforms, search engines and travel sites that score traffic aggressively.

How dynamic residential proxies work

You can generate credentials in the console or pull them through the API. The connection string is the standard host:port:username:password, with targeting and session parameters embedded in the username:

# Sticky session: US / New York, same IP for 30 minutes
host:1337:account-country-us-state-ny-city-newyork-sid-AbCdEfGhIjKl-stime-30:password

# Rotating: UK, new IP on every request
host:1337:account-country-gb-sid-AbCdEfGhIjKl:password

Rotating mode is built for high-volume crawling: one IP per request keeps the request count per IP close to zero. Sticky mode is for flows that need continuity such as log in, paginate, add to cart or fill a form. Sticky windows run from 1 to 120 minutes; when the window expires the IP rotates automatically, so rebuild the session before it expires if you need longer continuity.

Capabilities

Common use cases

Residential vs datacenter vs mobile

Rule of thumb: the stricter the target's risk engine, the more you should lean on residential IPs; the more you need one stable identity over time, the more you should use static residential; if throughput is all that matters and the target does not score IP reputation, datacenter is the cheapest option.

Pricing

Getting started in five steps

1. Sign in and open Proxy → Dynamic Residential in the console.
2. Pick country, state and city, choose sticky or rotating, choose protocol and output format.
3. Set the quantity and generate credentials, then copy or export them.
4. Drop them into your scraper, antidetect browser or mobile client.
5. Track usage in the console and top up traffic as needed.

# Verify the exit IP with curl
curl -x "http://account-country-us-sid-AbCdEfGhIjKl-stime-30:password@host:port" https://httpbin.org/ip

# Python requests, rotating per request
import requests
proxy = "http://account-country-gb-sid-ZzYyXxWwVvUu:password@host:port"
r = requests.get("https://httpbin.org/ip",
                 proxies={"http": proxy, "https": proxy}, timeout=30)
print(r.json())

Puppeteer, Playwright, Selenium and Scrapy work the same way through --proxy-server or the proxies argument. The exact gateway host and port are shown in the console; see the dynamic proxy guide for every parameter.

FAQ