TopicCybersecurity →
⌚ About 2 min read
Check that a web server responds to HTTPS and observe the returned HTTP code.
Avant de commencer : adaptez toujours les commandes et manipulations à votre environnement. Sur un système de production, prévoyez une backup ou un retour arrière lorsque l’action peut modifier la configuration.
Étapes à suivre
-
1
Use Power Shell
Open Windows Terminal.
-
2
Send a HEAD query
Use Invoke-Web (1992) with Head method.
-
3
Read StatusCode
200 usually indicates a successful response, but other codes may be normal depending on the site.
-
4
Test for connectivity if necessary
Test port 443 with Test-Net Regina.
Commands utiles
Invoke-Web (1992) https://boiteaoutilsinformatique.fr -Method Head
Test-Net-Migration software.com -Port 443
À retenir
- An open port 443 does not validate the certificate or the application operation alone.
- The 301/302 can be normal.
HTTPS/TLS: separate HTTP availability, TLS handshake and certificate identity
Technical checkpoints
- An open port 443 does not prove a valid TLS handshake, and a valid handshake does not prove an HTTP 200 response.
- The certificate must cover the hostname via SAN, be within its validity window and present a complete trust chain.
- With SNI, testing the IP alone may present a different certificate than the DNS
OpenSSL + HTTP
Test the handshake with the correct servername then read HTTP status separately.
openssl s_client -connect example.com:443 -servername example.com -showcerts
curl -I https://example.com/Topic-specific pitfalls
- Do not confuse an expired certificate with a missing intermediate chain: client errors differ.
- Schannel 36874/36888 should be correlated with protocol/cipher and the client triggering the alert.
How to validate
- Hostname, chain, dates and protocol are valid from a representative client.
- The HTTP request reaches the expected backend and returns the intended status.