> For the complete documentation index, see [llms.txt](https://help.proxidize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.proxidize.com/plans-and-features/https-proxies.md).

# HTTPS Proxies

Connect to Proxidize proxies over HTTPS to encrypt the connection between your tool and the proxy, using the same credentials and ports as HTTP.

Mobile Per Proxy, Mobile Per GB and Residential Per GB proxies all accept HTTPS connections.

HTTPS encrypts the connection between your tool and our proxy, so your proxy username, password and requests stay private on the network you connect from, such as public Wi-Fi or a shared office network.

{% hint style="success" %}
HTTPS uses the same credentials and ports as HTTP, so the only change is writing `https://` instead of `http://`.
{% endhint %}

***

## How HTTPS compares

|                             | HTTP                                 | HTTPS                 |
| --------------------------- | ------------------------------------ | --------------------- |
| **Port**                    | `20000`, or the proxy's dynamic port | The same port as HTTP |
| **Credentials**             | Your usual credentials               | The same credentials  |
| **Connection to the proxy** | Unencrypted                          | Encrypted             |
| **Host**                    | `pg.proxi.es` or the IP              | `pg.proxi.es`         |

HTTPS works whether the website itself uses HTTP or HTTPS.

It also works with every authentication mode, **User / Pass**, **Simple Mode** and **IP Whitelist**, and with both static and dynamic ports.

SOCKS5 keeps its own ports, `20002` or its dynamic port, and UDP still runs over SOCKS5. See [UDP on Mobile Proxies](/plans-and-features/udp-on-mobile-proxies.md).

***

## Use the DNS hostname

The proxy's security certificate is issued for `pg.proxi.es`, so HTTPS connects by hostname.

{% hint style="info" %}
For HTTPS, use the host `pg.proxi.es` rather than an IP address.
{% endhint %}

On Per GB access points and Pooling, choosing **HTTPS Proxy** sets **Hostname** to **DNS Hostname** for you.

On Per Proxy and Session Builder, set the hostname to DNS yourself, as shown below.

***

## Choose HTTPS in the dashboard

{% tabs %}
{% tab title="Per GB access points" %}
{% stepper %}
{% step %}

### Open the access point

Open **Mobile Per GB** or **Residential Per GB**, then select your access point on the **Access Point** tab.

<figure><img src="https://3163533074-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiAQa47xivOtQQ7mQZOnQ%2Fuploads%2FRe9DWZgT3VaWpn1SA0Ei%2F01-access-point-type-https.png?alt=media&amp;token=c38e1105-0989-4eec-89fb-b9587aa9547a" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Set the type

Set **Type** to **HTTPS Proxy**.

**Hostname** switches to **DNS Hostname**, and **IP Hostname** is unavailable while HTTPS is selected.

<figure><img src="https://3163533074-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiAQa47xivOtQQ7mQZOnQ%2Fuploads%2FzWpxjMw7yDIWFzEa10wf%2F02-hostname-ip-disabled.png?alt=media&amp;token=4538dce9-8ad0-4980-a08d-6aa4bb01a8c6" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Copy and test

**Test with cURL** now starts with `https://`, ready to run.

Lines in **Formatted Proxy List** look the same for HTTP and HTTPS, so choose HTTPS in your tool, or pick the `username:password@hostname:port` format and add `https://` in front.
{% endstep %}
{% endstepper %}

When you create an access point, **Proxy Type** offers **HTTP** and **SOCKS5**, so switch **Type** to **HTTPS Proxy** once it is created.
{% endtab %}

{% tab title="Pooling" %}
On **Proxies → Mobile Proxies → Pooling**, set **Type** to **HTTPS Proxy**.

**Hostname** switches to **DNS Hostname**, and **Test with cURL** starts with `https://`.

<figure><img src="https://3163533074-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiAQa47xivOtQQ7mQZOnQ%2Fuploads%2FTPU4QmQ1t2itmnFTltp6%2F03-pooling-https-curl.png?alt=media&amp;token=f3127b26-9e8d-498b-9b46-42efa2ba902d" alt=""><figcaption></figcaption></figure>

See [Per Proxy Pooling](/mobile-per-proxy/per-proxy-pooling.md).
{% endtab %}

{% tab title="Per Proxy" %}
The **HTTP(S) PROXY** column holds one string that connects over HTTP or HTTPS.

1. In **Proxy output**, set **Hostname** to **DNS**. This changes the host for every proxy in your list, so copy your proxies again afterwards.
2. Copy a proxy from the **HTTP(S) PROXY** column, or choose **HTTP(s)** in **Copy Proxies**.
3. Choose HTTPS in your tool, or set **Proxy Format** to **User:Pass\@IP:Port** and add `https://` in front.

See [Proxy Output and Authentication on Per Proxy](/mobile-per-proxy/proxy-output-and-authentication-on-per-proxy.md).
{% endtab %}

{% tab title="Session Builder" %}
**HTTP(s) Proxy** in **Type** covers both HTTP and HTTPS.

1. Set **Type** to **HTTP(s) Proxy** and **Hostname** to **DNS Hostname**.
2. Add your batches and copy the list.
3. Choose HTTPS in your tool, or pick the `username:password@hostname:port` format and add `https://` in front of each line.

See [Per GB Session Builder](/per-gb-proxies/pergb-session-builder.md).
{% endtab %}
{% endtabs %}

***

## Test your connection

Run this in a terminal with your own username and password:

```bash
curl -x "https://USERNAME:PASSWORD@pg.proxi.es:20000" https://ipv4.icanhazip.com
```

It prints the IP your request went out on.

Keep certificate checks turned on in your tool, since the proxy presents a valid certificate for `pg.proxi.es`.

{% hint style="info" %}
If a tool has no HTTPS proxy option, HTTP and SOCKS5 keep working exactly as before with the same credentials.
{% endhint %}

***

## Quick FAQ

<details>

<summary>Do I need new credentials for HTTPS?</summary>

No. Your username, password and port stay the same, and only the scheme changes from `http://` to `https://`.

</details>

<details>

<summary>Can I use HTTPS with websites that use HTTP?</summary>

Yes. HTTPS protects the connection between your tool and the proxy, so it works with HTTP and HTTPS websites alike.

</details>

<details>

<summary>Why can't I choose IP Hostname with HTTPS?</summary>

The proxy's certificate is issued for `pg.proxi.es`, so HTTPS connects by hostname. Access points and Pooling switch to **DNS Hostname** for you when you choose **HTTPS Proxy**.

</details>

<details>

<summary>My tool reports a certificate name mismatch. What should I check?</summary>

Check that the host is `pg.proxi.es` and not an IP address. On Per Proxy, set **Hostname** to **DNS** in **Proxy output** and copy your proxies again.

</details>

<details>

<summary>Does Proxy Analytics show which requests used HTTPS?</summary>

No. **PROTOCOL** describes the request to the website, so a visit to an HTTPS website logs as `HTTPS` whether your connection to the proxy used HTTP or HTTPS. See [Proxy Analytics](/tools/proxy-analytics.md).

</details>

***

## Related articles

* [Per GB Targeting and Sessions](/per-gb-proxies/per-gb-targeting-and-sessions.md)
* [Per Proxy Pooling](/mobile-per-proxy/per-proxy-pooling.md)
* [Proxy Output and Authentication on Per Proxy](/mobile-per-proxy/proxy-output-and-authentication-on-per-proxy.md)
* [Limits and Specs](/reference/limits-and-specs.md)

***

## <mark style="color:$primary;">Need help?</mark>

If you have any questions, concerns, or need further clarification, feel free to reach out to us via live chat or email us directly at <support@proxidize.com>.


---

# 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://help.proxidize.com/plans-and-features/https-proxies.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.