> For the complete documentation index, see [llms.txt](https://dinproxy.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dinproxy.gitbook.io/docs/guides/residential-proxies/connect.md).

# Connect & sign in

Address, port, protocols, and signing in with a proxy user or from a whitelisted IP.

| Setting   | Value                                                                                                                                                                            |
| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Host      | `proxy.dinproxy.com`                                                                                                                                                             |
| Port      | `7777`                                                                                                                                                                           |
| Protocols | HTTP, HTTPS and SOCKS5, all on the same port. Write the proxy as `http://` or `socks5h://`                                                                                       |
| Username  | Your connection username, e.g. `1024~myuser`, plus optional [location and session options](https://dinproxy.gitbook.io/docs/guides/residential-proxies/location-and-sessions.md) |
| Password  | The proxy user's password                                                                                                                                                        |

## Signing in

There are two ways:

* **Proxy user**: the full **connection username** from **Tools → Users** (account number, `~`, name) and its password. Always include the account number. See [Proxy users](https://dinproxy.gitbook.io/docs/getting-started/proxy-users.md).
* **Whitelisted IP**: from a server whose IP you added under **Tools → Whitelist**, no password is needed. See [IP whitelist](https://dinproxy.gitbook.io/docs/getting-started/ip-whitelist.md).

Keep the password in your tools up to date: repeated [wrong passwords](https://dinproxy.gitbook.io/docs/getting-started/proxy-users.md#too-many-wrong-passwords) pause sign-ins for a while.

The same proxy users and whitelist work for mobile proxies on port `7779`.

## HTTP and HTTPS

Write the proxy as `http://` for both HTTP and HTTPS sites. For HTTPS sites your client opens an encrypted tunnel, so we never see the page contents.

```bash
curl --proxy 'http://proxy.dinproxy.com:7777' \
  --proxy-user '1024~myuser:YOUR_PASSWORD' \
  'https://httpbin.org/ip'
```

## SOCKS5

Use the same host, port, username and password, written as `socks5h://` (SOCKS5 with remote DNS: the proxy looks up the site's name):

```bash
curl --proxy 'socks5h://proxy.dinproxy.com:7777' \
  --proxy-user '1024~myuser:YOUR_PASSWORD' \
  'https://httpbin.org/ip'
```

## Proxy URLs

Many tools take one URL such as `http://USERNAME:PASSWORD@proxy.dinproxy.com:7777`. Inside a URL, characters like `@` in the username or symbols in the password must be **percent-encoded** (for example `@` becomes `%40`). The dashboard's **User:Pass\@IP:Port** format gives this part already encoded; add `http://` or `socks5h://` in front ([output formats](https://dinproxy.gitbook.io/docs/guides/residential-proxies/endpoints-and-testing.md#output-formats)).

## What you can reach

* Target sites on ports **80** and **443** (normal web traffic).
* Public internet addresses only.

Other ports and private networks are refused with `403 TARGET_NOT_ALLOWED`.

## Limits

* Each account can keep up to 100 connections open at once, residential and mobile together. Beyond that you get `429 TOO_MANY_CONNECTIONS`.
* Close connections you no longer need. Reuse HTTPS and SOCKS5 connections (keep-alive); each plain HTTP request uses its own connection.
* A connection with no traffic for 60 seconds is closed.
* When your residential traffic runs out, new connections to port `7777` get `402 QUOTA_EXHAUSTED` until you buy more, and open ones stop. Mobile traffic is a separate balance and is not used.
* A proxy user's traffic limit, if you set one, covers residential and mobile traffic together.
