> ## Documentation Index
> Fetch the complete documentation index at: https://docs.protectorplus.cloudsine.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Network Prerequisites

> Ports, protocols, and DNS for a Protector Plus deployment.

## Ports

| Service | TCP port | Purpose                                          |
| ------- | -------- | ------------------------------------------------ |
| SSH     | 22       | Vendor maintenance access. Restrict source CIDR. |
| HTTPS   | 443      | Prompt inspection and administrative dashboard.  |

## DNS — Forwarding mode

Forwarding mode requires each GenAI application to be assigned a **unique FQDN** that resolves to the Protector Plus instance (AMI) or Ingress (Kubernetes). The FQDN is the application identifier — Protector Plus applies the bound security profile based on the FQDN of the incoming request.

Example assignment:

| FQDN                       | Protector Plus action    | Origin                 |
| -------------------------- | ------------------------ | ---------------------- |
| `app1.protect.example.com` | Apply Security Profile 1 | LLM endpoint for App 1 |
| `app2.protect.example.com` | Apply Security Profile 2 | LLM endpoint for App 2 |

## DNS — Non-forwarding mode

Non-forwarding mode does **not** require an FQDN. The application calls the Protector Plus API directly with an API key and App ID. The profile pseudo-URL (e.g., `app1.pseudo.local`) is used internally for configuration, not a resolvable DNS name.