Network Troubleshooting / IT Support Guides
Use HTTP status codes to route a support incident
A website that returns a deliberate HTTP error is different from one that never accepts a connection. Collect the response without assuming the code alone identifies the root cause.
Environment and inputs: Mixed platforms · each example identifies its shell or required tool
Try the diagnostic command
Use the stated shell and platform. Replace sample domains, addresses, services and paths with values from the system you are authorized to support.
curl -I --connect-timeout 5 --max-time 15 https://example.comHow to read the result
In a shell with curl, -I requests headers with HEAD. Authentication errors, missing routes and upstream failures produce different statuses, though HEAD can differ from the application's normal GET.
What to do next
Record the status, request time and any safe request identifier. Compare with a normal approved request and use proxy or application logs to investigate the failing layer.
Before you make a change
Use curl.exe in Windows PowerShell when needed to avoid aliases. Do not include session cookies, authorization tokens or sensitive query strings in a shared ticket.