Loading tool…
Search HTTP status codes and read real-world guidance.
200
OK
The request has succeeded.
301
Moved Permanently
The resource has been permanently moved to a new URL.
302
Found
The resource has been temporarily moved to another URL.
400
Bad Request
The server could not understand the request due to invalid syntax.
401
Unauthorized
Authentication is required to access the resource.
403
Forbidden
The server understands the request but refuses to authorize it.
404
Not Found
The server cannot find the requested resource.
500
Internal Server Error
The server encountered an unexpected condition.
502
Bad Gateway
The server received an invalid response from an upstream server.
503
Service Unavailable
The server is not ready to handle the request.
Look up any HTTP status code and get a plain-English explanation plus real-world usage guidance — no upload to any server and no account required. Search by code number or keyword.
API developers look up status codes to ensure they are returning semantically correct responses. Front-end developers handle API errors by code and need to know what each code means. QA engineers verify that test cases trigger the right status codes.
Translate cron strings into readable schedules and next run times.
Generate a tailored .gitignore file for your project stack.
Convert CSV data to JSON and back for APIs and spreadsheets.
Decode browser, OS, and device details from a UA string.