# Protocols

PlainProxies Residential Proxies support two connection protocols: **HTTP/S** and **SOCKS5**.\
You can choose the protocol directly in your dashboard when generating your entry point.

#### **HTTP**

Residential Proxies can be used with the **HTTP** protocol, which is widely supported by most scraping tools, libraries, and browsers.

**Example:**

```
res-v2.pr.plainproxies.com:8080:USER:PASSWORD
```

### **HTTP/2**

Our Residential Proxies support HTTP/2, which includes benefits such as multiplexing, header compression, and lower latency.\
Most modern clients will automatically use HTTP/2 when supported.

**Example:**

```
res-v2.pr.plainproxies.com:8080:USER:PASSWORD
```

### **SOCKS5**

SOCKS5 is fully supported and ideal for applications that require TCP-level tunneling or non-HTTP traffic.\
All location targeting parameters (country, state, city) work normally with SOCKS5.

**Example with location targeting:**

```
res-v2.pr.plainproxies.com:1080:USER:PASSWORD
```

### **HTTP/3 (QUIC)**

HTTP/3 is based on QUIC, which runs over UDP, not TCP.  Because of this, HTTP/3 is supported only when using the SOCKS5 protocol.<br>

**Example:**

```
res-v2.pr.plainproxies.com:1080:USER:PASSWORD
```


---

# 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://docs.plainproxies.com/proxies/residential-proxies/protocols.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.