# 19-Jul-2026 — Environment Management — show live hostname health so a broken web address is visible [ref #319](https://github.com/nbarrett/ngx-ramblers/issues/319)

## [build 780](https://github.com/nbarrett/ngx-ramblers/actions/runs/29680933358) — [commit 2abae87](https://github.com/nbarrett/ngx-ramblers/commit/2abae8781d21d98885dab94d55bc428815962544)

_____

## What's new

On `admin/platform/environment-management/health`,  a site's web address could stop working without anything on the admin screens showing it. The environment screen only ever checked one internal hostname, so a site served on its own domain could have a dead address indefinitely and still look completely healthy — the problem was only ever found by someone happening to type the address without the www. Environment Management now checks every hostname a site actually answers on, live, and says plainly which are serving, which are redirecting and which are broken.

## At a glance

- A new Hostname health panel shows every hostname for the selected environment, with its DNS record, redirect target and HTTPS response
- Anything needing attention is called out in a warning above the table rather than left for someone to notice
- The Environments Monitoring grid gains a Hostnames column, so a broken address is visible across every environment at once instead of only when that environment is selected
- A misconfigured redirect that would return a 522 timeout is identified as exactly that, rather than failing silently when someone visits
- Selections on the setup page (mode, environment, action) are held in the URL, so a view can be linked to or restored on refresh