How do I check a website’s HTTP status from Windows?
Use curl.exe explicitly so Windows PowerShell does not interpret curl as another command alias. A header request reveals the HTTP status and response headers, while a separate request may be needed to test actual page content.
Instructions
1. Request HTTPS headers with a time limit
Use the site hostname so TLS hostname checks and virtual-host routing remain meaningful.
curl.exe --head --connect-timeout 10 --max-time 20 https://app.example.com/--head sends a HEAD request. The timeout options bound the diagnostic request. The same command works in CMD.
2. Inspect a redirect chain when needed
A redirect can be expected, but confirm where it leads.
curl.exe --head --location --max-redirs 5 --max-time 20 https://app.example.com/--location follows redirects and displays their headers. Review each target before treating the final response as the intended site.
3. Distinguish status, transport and content
A 200 response does not prove that the page contains the correct application. A 405 response to HEAD may require a normal GET check. Keep TLS verification enabled and investigate certificate errors rather than bypassing them.
Check the result
- TLS verification succeeds for the intended hostname.
- The status and redirect destination match the application’s expected behaviour.
Troubleshooting
- curl parameters are not recognised
- Use curl.exe and confirm that this executable exists in the local environment.
- A HEAD request returns 405
- The application may not support HEAD. Use an authorised GET request and inspect its status and content separately.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.