Windows Server / Services, IIS & Secure Operations
Find an IIS hostname or port binding mismatch
A site can work locally by one address but route external users to another site because its binding differs.
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-WebBinding -Name 'AppSite'Read the result
The query lists bindings for the selected IIS site, including protocol and binding information. SNI, certificates, reverse proxies and DNS add related routing layers.
Resolve and verify
Compare the real client hostname and port with intended bindings and proxy configuration. Correct the specific managed mapping and retest from the affected client path.
Before changing production
Do not add wildcard bindings or remove another site's binding merely to make the test URL work.