Runs locally
$ devdesk http-status--local
Security & network

HTTP status code lookup and troubleshooting

Look up HTTP response codes by number or English/Chinese keywords. Distinguish success, redirects, client errors and server errors with troubleshooting tips.

Loading local tool…

How to use

Filter by code or English/Chinese keywords. 1xx informational, 2xx success, 3xx redirection, 4xx client error, 5xx server error.

Your input stays yours

Step by step

  1. Enter a code or keyword such as 404, 未找到 or Unauthorized.
  2. Read the matching meaning; clear the search to restore the list.
  3. Use response headers, body and service logs to identify the actual cause.

Look up 404

404

The result should show Not Found. A status code describes response semantics but does not identify which configuration layer caused it.

Frequently asked questions

How do 401 and 403 differ?

401 indicates missing valid authentication credentials; 403 means the server understands the request but refuses it. Systems may obscure resource details with different responses; check authentication and authorization logs.

How should I investigate 502 and 504?

502 concerns an invalid upstream response at a gateway; 504 concerns an upstream timeout. Correlate gateway and upstream logs at the same time instead of relying on a page refresh alone.

Does 200 always mean business success?

Not necessarily. It indicates HTTP-level success, while an application may report business failure in the body. Check the application status and response structure too.