> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/products/proxies/dedicated-datacenter-proxies/enterprise/protocols.md).

# Protocols

Enterprise Dedicated Datacenter Proxies support HTTP and SOCKS5 protocols. Contact support to activate SOCKS5 and configure additional ports.

{% hint style="info" %}
Our Customer Support team is available 24/7 - reach out through [**support@oxylabs.io**](mailto:support@oxylabs.io) or via [**live chat**](https://oxylabs.io/). They will assist you in activating SOCKS5 protocol for your account. By default, the HTTP protocol is enabled.
{% endhint %}

#### HTTP

Our documentation includes code examples showcasing how to connect to the proxies using `HTTP` protocol. The protocol is supported by common libraries and third-party software.

#### **SOCKS5**

For using `SOCKS5` protocol, you have to add `socks5h` in your request, for example:

```
curl -x socks5h://1.2.3.4:1180 -U USERNAME:PASSWORD ip.oxylabs.io
```

#### Ports of proxies

The default configuration of proxy ports includes `80` and `443`, which are standard ports designed to accommodate the `HTTP` and `HTTPS` protocols, as outlined in the table below. To access other ports, it is necessary to undergo compliance verification, please contact our [**support**](mailto:support@oxylabs.io).

| Protocol | Port  |
| -------- | ----- |
| `HTTP`   | `80`  |
| `HTTPS`  | `443` |


---

# 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://developers.oxylabs.io/products/proxies/dedicated-datacenter-proxies/enterprise/protocols.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.