An HTTPS binding tells IIS which certificate to use for a website’s encrypted connections. After installing a suitable certificate, you can bind it to the correct hostname and port.
Check the certificate
You need IIS administrator access and an installed certificate with its private key. It must be valid for the website hostname and include the required trust chain. Record existing bindings before editing them.
Add or edit the binding
- Press Windows + R, enter
inetmgrand press Enter. - Expand Sites and select the website.
- Click Bindings. Add an HTTPS binding or edit the intended existing one.
- Select https, the appropriate IP address and port, normally
443. - Enter the required hostname and select its matching certificate.
- Use Require Server Name Indication when the site’s hostname-based shared-address configuration requires SNI. Review other sites’ bindings to avoid conflicts.
- Click OK and test the exact HTTPS hostname.
A routine IIS restart is not required just to test a saved binding.
Troubleshooting
Check certificate validity, private-key availability, hostname coverage, trust-chain installation, DNS and firewall access. If the certificate is not selectable, check the relevant local-computer certificate store and whether it includes the private key.
Maintain the configuration
Review TLS protocols against the operating system’s supported configuration. TLS 1.3 is not supported by every Windows Server version. Plan HTTP-to-HTTPS redirects separately and check certificate selection after renewal.