> 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/mtls-authentication.md).

# mTLS Authentication

Learn how to authenticate with Oxylabs proxies using mutual TLS (mTLS) and client certificates instead of credentials or IP whitelisting.

{% hint style="info" %}
**Want to use mTLS?** mTLS is available for [Datacenter](https://developers.oxylabs.io/products/proxies/datacenter-proxies.md), [ISP](https://developers.oxylabs.io/products/proxies/isp-proxies.md), [Residential](https://developers.oxylabs.io/products/proxies/residential-proxies.md), and [Mobile Proxies](https://developers.oxylabs.io/products/proxies/mobile-proxies.md) and set up on request. Contact your Account Manager or <support@oxylabs.io>, and we will help you enable it for your Oxylabs proxies.
{% endhint %}

**Oxylabs proxies support mTLS (Mutual Transport Layer Security)** – a two-way authentication method that extends standard TLS/HTTPS. Both the client and the server verify each other by exchanging and validating `X.509` digital certificates during the TLS handshake. The connection is established only if both sides successfully validate each other's certificate.

Instead of passing `username` and `password`, the client establishes a TLS connection to the proxy endpoint using its client certificate. Replace `ENDPOINT:PORT` with the mTLS endpoint provided by your Account Manager (e.g. `secure-gateway.oxylabs.io:8443`).

### Why use mTLS

<table><thead><tr><th width="184">Method</th><th>How it works</th></tr></thead><tbody><tr><td><strong>Standard TLS</strong> (one-way)</td><td>Only the client verifies the server's identity using the server's TLS/SSL certificate, for example, when a browser verifies a website.</td></tr><tr><td><strong>Mutual TLS</strong> (two-way)</td><td>The client and the server verify each other's certificates. The client presents a certificate and a private key, and the server accepts the connection only if they are valid.</td></tr></tbody></table>

Compared to `username`/`password` authentication and IP whitelisting, mTLS provides the following:

1. **No shared secrets.** Authentication relies on a certificate and private key pair, so there are no passwords to log, leak, or hardcode in your source code.
2. **No static IP dependency.** Access is not tied to a source IP address, so mTLS suits dynamic environments such as autoscaled Kubernetes clusters or serverless functions, where IP whitelisting is difficult to maintain.
3. **Restricted access.** Only applications holding a valid private key can connect to the proxy entry node.
4. **Compliance.** mTLS can help you meet internal security policies that require mutual certificate verification.

### Things to keep in mind

* **Certificate management.** You are responsible for storing, securing, and rotating your private keys and client certificates before they expire. Store private keys in a secrets manager, such as AWS Secrets Manager, HashiCorp Vault, or Kubernetes Secrets, and never expose them.
* **Client support.** Your HTTP client, scraping framework, or proxy tool (for example, cURL, Python `requests` or `httpx`, Puppeteer, Playwright, or Go `net/http`) must be able to present a client certificate and key when connecting to the proxy.
* **Performance.** The initial TLS handshake takes slightly longer because of the certificate exchange. Subsequent requests over persistent (keep-alive) connections are not affected.

### Need technical assistance?

**Live chat:** Access live chat through your dashboard or on the [**Oxylabs website**](https://oxylabs.io/) for quick questions or bug reports.

**Email:** You can contact us via [**support@oxylabs.io**](mailto:support@oxylabs.io). We recommend this method for less urgent questions or suggestions.


---

# 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/mtls-authentication.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.
