HTTP status code table
Developer tools
This dictionary is a local reference for common HTTP status codes; it does not connect to the network. A specific service may define additional codes or different error details.
All processing for this tool happens in your browser. Your input is not sent to a server.
About this tool
Use this reference to interpret HTTP responses in browser developer tools, API clients and server logs. Search matches the code, English reason phrase and the meaning in the current language. Filter by 1xx information, 2xx success, 3xx redirection, 4xx client errors or 5xx server errors, then select a code to copy its definition.
Common uses
- Look up a response code from an API request or an access log.
- Compare authentication failures, permission failures and missing resources before debugging.
- Copy a code, its category and its explanation into a bug report.
How to use it
- 1.Enter a code such as 404, an English phrase such as Gateway, or a word from a definition.
- 2.Choose a category to narrow the results. Text search and category filtering apply together.
- 3.Select a result card to show its detail and copy button. Clear resets the search, category and selection.
Response examples
Create a resource
POST /items HTTP/1.1
HTTP/1.1 201 Created Location: /items/42
A successful creation can return 201 with a Location header identifying the created resource.
Temporary redirect, same method
POST /old-endpoint HTTP/1.1
HTTP/1.1 307 Temporary Redirect Location: /new-endpoint
Follow the Location using POST for a 307. This illustrates semantics; the tool does not send the request.
Common interpretation mistakes
- Treating 304 as a redirect to a new URL: it relates to conditional requests and reuse of a cached representation.
- Confusing 502 and 504: 502 concerns an invalid upstream response; 504 concerns an upstream response that did not arrive in time.
- Assuming every redirect preserves the request method: 307 and 308 preserve it, while 301 and 302 can change POST to GET.
Limits and notes
- This is a curated reference, not a complete or continuously synchronized IANA registry; some extension or vendor codes are absent.
- The tool does not request a URL, inspect live headers, test an endpoint or diagnose the cause of an outage.
- A code alone may not explain a failure. Inspect the response headers, body, request method and server logs. The search field accepts up to 80 characters.
Frequently asked questions
What is the difference between 401 and 403?
401 indicates missing or invalid authentication credentials. 403 means the server refuses the request; providing credentials again may not help.
Does 202 mean the job is finished?
No. It means processing was accepted. Check the service’s documented job-status endpoint or completion signal.
Why are there no results for a code?
Clear the active category first. If it is still absent, consult the IANA registry or your service documentation; this table is not exhaustive.