# Dedicated IPs (Beta)

DIP is currently in **beta** and is available only after approval from NetNut Support.

To request access, contact: [**support@netnut.io**](mailto:support@netnut.io)

### Overview

DIP is a proxy feature designed to reduce IP collisions when multiple users access the same destination domain through the same proxy IP.

With DIP, customers purchase a pool of daily unique IPs dedicated to a specific target domain. Based on the purchased daily volume, NetNut allocates a concurrent IP pool that supports sticky sessions with reduced overlap for that domain.

DIP is currently available for **US residential traffic only**.

### Sticky Session Behavior

Each number in the customer’s assigned DIP range maps to a sticky peer position.

For example, if the customer uses:

```
dip-57
```

NetNut routes the request through the sticky peer position associated with number `57`.

If the underlying residential peer disconnects, NetNut automatically replaces it with another available peer while keeping the same DIP range position active.

This means the DIP session number remains valid, but the actual underlying peer IP may change if the original peer becomes unavailable

### Proxy Integration 

When using DIP, the proxy string must include the `dip` trigger.

This feature supports http, https and socks5

#### Format

```
{proxy_username}-res-us-dip-{number_within_range}
```

#### Components

| Component               | Description                                                                 |
| ----------------------- | --------------------------------------------------------------------------- |
| `{proxy_username}`      | The customer’s proxy username                                               |
| `res`                   | Residential proxy product identifier                                        |
| `us`                    | <p>Country code. </p><p><strong>DIP currently supports US only</strong></p> |
| `dip`                   | Required trigger that activates DIP routing                                 |
| `{number_within_range}` | A number from the customer’s assigned DIP range                             |

### Gateway Requirement

DIP requires the dedicated DIP gateway:

```
gw-dip.netnut.net
```

The required port is:

```
5959
```

Using the standard gateway **will not activate DIP behavior**.

### cURL Integration Example

#### Generic Format

```bash
curl -x {proxy_username}-res-us-dip-{number_within_range}:{password}@gw-dip.netnut.net:5959 https://www.walmart.com -v
```

#### Example With Placeholder Values

```bash
curl -x customer123-res-us-dip-57:password123@gw-dip.netnut.net:5959 https://www.walmart.com -v
```

### Behavior When Using a Number Outside the Assigned Range

If a customer sends a DIP number outside their assigned range, We **redirect** the request to a valid peer within the customer’s assigned range.

#### Example

Assigned DIP range:

```
1-1000
```

Requested DIP value:

```
1500
```

Expected behavior:

```
The request is redirected to a valid peer within the assigned DIP range.
```

For best performance and predictability, customers should use numbers within their assigned DIP range.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.netnut.io/netnut-documentation/netnut-proxies/residential-proxies/dedicated-ips-beta.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.