> For the complete documentation index, see [llms.txt](https://docs.ipdunar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ipdunar.com/products/overview/endpoints-and-ports.md).

# Endpoints & ports

## Production gateway

| Field                        | Value                           |
| ---------------------------- | ------------------------------- |
| Host                         | `gate.ipdunar.com`              |
| Port (HTTP / HTTPS / SOCKS5) | `7777`                          |
| Authentication port          | same — `7777` for all protocols |

A single host:port handles all three protocols. The protocol is auto-detected from the client handshake.

## Regional gateways (optional)

Latency-sensitive workloads can connect to a regional gateway that's closer to your servers. The pool of upstream IPs is identical; only the **first hop** changes.

| Region                   | Host                  |
| ------------------------ | --------------------- |
| Global anycast (default) | `gate.ipdunar.com`    |
| North America            | `na.gate.ipdunar.com` |
| Europe                   | `eu.gate.ipdunar.com` |
| Asia-Pacific             | `ap.gate.ipdunar.com` |

Use a regional gateway only when you measure a meaningful improvement; for most users the anycast host is faster because it routes to the nearest POP automatically.

## TLS

* Outbound TLS to the target site (HTTPS) is **always** end-to-end — ipdunar does not terminate it.
* Connecting to the gateway over TLS (wrapping the proxy hop itself) is supported on the same port `7777` — the gateway auto-detects plain vs TLS from the client handshake. Use it when your environment requires TLS-only egress.

## Connection limits

| Limit                               | Default   | Raise via              |
| ----------------------------------- | --------- | ---------------------- |
| Concurrent connections per sub-user | 600       | Dashboard plan upgrade |
| Requests per second per sub-user    | 1000      | Dashboard plan upgrade |
| Max request body                    | 100 MB    | Email support          |
| Max response body                   | unlimited | —                      |
| Idle timeout                        | 120 s     | —                      |

Trial accounts are capped at 25 concurrent connections.

## DNS

Resolve `gate.ipdunar.com` via your normal resolver. The record returns both IPv4 and IPv6; the gateway accepts either.

If your network blocks public DNS, the dashboard ships a static A/AAAA reference under **Settings → Network info**.

## Health check

A `GET /healthz` against the gateway returns `200 ok` and does **not** consume traffic credits:

```bash
curl https://gate.ipdunar.com:7777/healthz
```

Use it from monitoring jobs to verify the gateway is reachable without burning bandwidth.


---

# 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.ipdunar.com/products/overview/endpoints-and-ports.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.
