Skip to content

HTTP Status Code Reference

Look up HTTP status codes from 100 to 511 by number or keyword, with a description, details and typical use cases for each.

HTTP Status Code Reference

62 status codesClick a card to expand details

Category reference

1xx

Request received, continuing process

2xx

Request successfully received, understood, and accepted

3xx

Further action needed to complete the request

4xx

Request contains bad syntax or cannot be fulfilled

5xx

Server failed to fulfill a valid request

Updated . Provided as is. Check the output before you rely on it in production.

How to use HTTP Status Code Reference

  1. 1

    Search by status code

    Enter a code (e.g., 404, 500) to see its meaning, description, and common use cases. Quick reference for understanding API errors.

  2. 2

    Search by description

    Search for keywords like 'not found', 'server error', or 'success'. The tool returns matching status codes, letting you pick the right one for your response.

  3. 3

    Browse by category

    Group by status code families: 1xx (informational), 2xx (success), 3xx (redirection), 4xx (client error), 5xx (server error). Understand which category applies to your scenario.

  4. 4

    Use in API error handling

    Reference this tool when implementing error responses. Return 400 for bad requests, 401 for auth failures, 403 for permission denied, 404 for missing resources, 500 for server errors. Use correct codes for proper client error handling.

Questions and answers

What is HTTP Status Code Reference?
HTTP status codes are the three-digit numbers a server returns to say how a request went: 1xx informational, 2xx success, 3xx redirect, 4xx client error, 5xx server error. This reference explains each standard code with details and use cases, searchable by number or keyword.
Does HTTP Status Code Reference store or send my data?
No. All content is rendered entirely in your browser. No data is sent to any server.
What is the difference between 401 and 403 status codes?
401 Unauthorized means the request lacks valid authentication credentials — the client needs to log in. 403 Forbidden means the server understood the request but the authenticated user does not have permission to access the resource.
For AI agents: how to call this tool

Machine-readable contract, endpoints and examples. Humans can ignore this section.

Best Path For Builders

Browser workflow

Runs instantly in the browser with private local processing and copy/export-ready output.

Browser Workflow

This tool is optimized for instant in-browser execution with local data handling. Run it here and copy/export the output directly.

/http-status-codes/

For automation planning, fetch the canonical contract at /api/tool/http-status-codes.json.