> For the complete documentation index, see [llms.txt](https://docs.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vectra.ai/operations/detection-specific-guidance/hidden-https-tunnel-detection-showing-proxy-ip-as-target.md).

# Hidden HTTPS Tunnel - detection showing proxy IP as target

Understand why Hidden HTTPS Tunnel detections may show a proxy IP as the target and where to find the destination domain.

When traffic is sent through a proxy, the Vectra platform only sees the connection between the **client** and the **proxy**. The proxy then handles communication with the final destination (i.e. external IP), which is not directly visible to Vectra.

Because of this, detections may show the **proxy IP address** as the **target**. However, for **HTTPS traffic**, Vectra can still extract the **destination domain** from the **CONNECT packet**, allowing you to see the **domain name** even if the IP address belongs to a proxy.

This is normal behavior and does not indicate an issue with detection accuracy. You can refer to below article for more details:

Proxy handling: [Proxy handling in Vectra](/configuration/setup/proxies.md)

Data Smuggler with proxy: [Why would Data Smuggler list an internal IP address as the destination?](https://support.vectra.ai/vectra/article/KB-VS-1205)


---

# 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://docs.vectra.ai/operations/detection-specific-guidance/hidden-https-tunnel-detection-showing-proxy-ip-as-target.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.