Windows Server / Services, IIS & Secure Operations
Distinguish a stopped IIS site from an application failure
An IIS application can be unreachable because the site is stopped, its bindings differ or the application fails after routing.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-Website | Select-Object Name, State, PhysicalPath, ApplicationPoolRead the result
With the WebAdministration module on the intended IIS server, the query lists sites and their main mappings. Running state does not validate backend dependencies.
Resolve and verify
Compare the intended site, pool and path with deployment records, then inspect the actual HTTP error and site logs. Repair the failing layer and verify a real request.
Before changing production
Do not restart all IIS sites to repair one application or point the site at an unreviewed directory.