> For the complete documentation index, see [llms.txt](https://docs.ipdunar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ipdunar.com/products/overview.md).

# Residential proxies

Residential proxies route your requests through real consumer devices on ISP networks worldwide. Target sites see them as ordinary household traffic, making them the most resilient choice against anti-bot defenses.

## At a glance

|                    |                                                    |
| ------------------ | -------------------------------------------------- |
| **Type code**      | `res`                                              |
| **Delivery**       | Gateway, username-encoded                          |
| **Endpoint**       | `gate.ipdunar.com:7777`                            |
| **Billing**        | Pay per GB                                         |
| **Pool size**      | 100M+ IPs                                          |
| **Geo targeting**  | Country, state, city, ASN                          |
| **Session length** | Rotating (per connection) or sticky (up to 30 min) |
| **Protocols**      | HTTP, HTTPS, SOCKS5                                |
| **Authentication** | User+password or IP whitelist                      |

## When to use residential

* Sites with strong anti-bot defenses (e-commerce, ticketing, social platforms)
* Geo-restricted content that requires a real consumer IP in a specific country
* Ad verification and SERP tracking that must blend with real user traffic
* LLM data pipelines that need fresh, unblocked web pages

If your target is unprotected, [Datacenter proxies](https://docs.ipdunar.com/products/overview-3.md) (coming soon) are cheaper. If you need the same IP for hours or days, [ISP proxies](https://docs.ipdunar.com/products/overview-2.md) are a better fit.

## Username grammar

```
ipdunar_{username}-type-res-region-{region}[-state-{state}][-city-{city}][-asn-{asn}][-session-{session_id}-sesstime-{ttl}]
```

Full reference: [Username format](https://docs.ipdunar.com/getting-started/username-format.md).

## Five-second example

```bash
curl -x http://ipdunar_s1a2b3c4d5e-type-res-region-us:PASSWORD@gate.ipdunar.com:7777 \
     https://ipv4.icanhazip.com
```

## On this page

* [Quick start](https://docs.ipdunar.com/products/overview/quick-start.md) — first request in five minutes
* [Authentication](https://docs.ipdunar.com/products/overview/authentication.md) — password vs IP whitelist
* [Endpoints & ports](https://docs.ipdunar.com/products/overview/endpoints-and-ports.md) — host, port, TLS
* [Locations](https://docs.ipdunar.com/products/overview/locations.md) — countries, states, cities
* [Protocols](https://docs.ipdunar.com/products/overview/protocols.md) — HTTP / HTTPS / SOCKS5
* [Sessions & rotation](https://docs.ipdunar.com/products/overview/sessions-and-rotation.md) — sticky vs rotating
* [ASN targeting](https://docs.ipdunar.com/products/overview/asn-targeting.md) — pin a specific ISP
* [Restricted targets](https://docs.ipdunar.com/products/overview/restricted-targets.md) — sites we don't route to
* [Error definitions](https://docs.ipdunar.com/products/overview/error-definitions.md) — what each status code means
* [Statistics](https://docs.ipdunar.com/products/overview/statistics.md) — dashboards and the traffic API


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ipdunar.com/products/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
