---
title: "Your app's HTTPS address: the while.sh docs"
url: https://while.sh/en/docs/building-blocks/https-address/
updated: 2026-11-09
---

# HTTPS address

Each public web service gets its HTTPS address, certificate included, as soon as it is deployed.

> You, to your agent: Give me the app's address.

## When to use it

Each public web service has one, without doing anything.

## How it works

Every public web service gets its HTTPS address, certificate included: `https://<project>.while.cloud` for the main service in production, https://`<project>-<service>`.`while.cloud` for the others, and -\<environment> at the end outside production.

## What to know

The main service keeps the project's address, even when another public service arrives. Two addresses that would collide (the project "shop-api" and the api of the project "shop"): the second gets a four-character suffix, and `get_app_status` says so.

The visitor's address: `X-Real-IP`, set by while's edge (a client's own is replaced), or the first entry of `X-Forwarded-For`, which the edge replaces too; the following ones, in varying number, are while's proxies. Forwarded is rebuilt by while from them: a client's own does not arrive.

## Your agent's MCP tools

Your agent handles it with the `get_app_status` tool.

## Guides

- [Put your app on your own domain name, over HTTPS, from your AI agent](/en/guides/custom-domain/)