utilities.dev

HTTP Status Codes Reference

Look up HTTP status codes by number or phrase and browse by category.

Lookup runs locally in your browser. This is reference guidance only, not protocol enforcement or validation.

Search
Search by status code (e.g. 404) or phrase (e.g. not found)
Category:1xx Informational2xx Success3xx Redirection4xx Client Error5xx Server Error
1xx - Informational
4 codes in this category
100
1xx
Continue
Server received request headers; client should send body.
101
1xx
Switching Protocols
Server agrees to switch protocol per Upgrade header.
102
1xx
Processing
Server is processing request; prevents client timeout.
103
1xx
Early Hints
Server sends preliminary headers before final response.
2xx - Success
10 codes in this category
200
2xx
OK
Request succeeded; response body contains result.
201
2xx
Created
Resource created; Location header often points to new resource.
202
2xx
Accepted
Request accepted for processing; may complete later.
203
2xx
Non-Authoritative Information
Transformed response from proxy; may differ from origin.
204
2xx
No Content
Success with no response body; common for DELETE or PUT.
205
2xx
Reset Content
Client should reset document view that sent the request.
206
2xx
Partial Content
Range request fulfilled; body contains requested byte range.
207
2xx
Multi-Status
WebDAV; body contains multiple status codes.
208
2xx
Already Reported
WebDAV; members already enumerated in prior response.
226
2xx
IM Used
Server fulfilled GET with instance-manipulation.
3xx - Redirection
7 codes in this category
300
3xx
Multiple Choices
Multiple representations; client or server chooses one.
301
3xx
Moved Permanently
Resource moved permanently; use new URI in Location.
302
3xx
Found
Temporary redirect; method may change to GET.
303
3xx
See Other
Redirect to different URI via GET.
304
3xx
Not Modified
Cached response still valid; no body returned.
307
3xx
Temporary Redirect
Temporary redirect; method and body preserved.
308
3xx
Permanent Redirect
Permanent redirect; method and body preserved.
4xx - Client Error
16 codes in this category
400
4xx
Bad Request
Request malformed or invalid; client should fix and retry.
401
4xx
Unauthorized
Authentication required; include credentials.
402
4xx
Payment Required
Reserved for future use; payment systems.
403
4xx
Forbidden
Server understood request but refuses to authorize.
404
4xx
Not Found
Resource not found at requested URI.
405
4xx
Method Not Allowed
Method not allowed for this resource; Allow header lists valid methods.
406
4xx
Not Acceptable
No representation matches Accept headers.
408
4xx
Request Timeout
Server timed out waiting for request.
409
4xx
Conflict
Request conflicts with current server state.
410
4xx
Gone
Resource no longer available; no forwarding address.
413
4xx
Payload Too Large
Request body exceeds server limits.
414
4xx
URI Too Long
Request URI exceeds server limits.
415
4xx
Unsupported Media Type
Content-Type not supported by server.
422
4xx
Unprocessable Entity
Syntax valid but semantic errors; often validation failures.
429
4xx
Too Many Requests
Rate limit exceeded; Retry-After may indicate when to retry.
431
4xx
Request Header Fields Too Large
Request headers exceed server limits.
5xx - Server Error
6 codes in this category
500
5xx
Internal Server Error
Unexpected server error; generic fallback.
501
5xx
Not Implemented
Server does not support the request method.
502
5xx
Bad Gateway
Invalid response from upstream server.
503
5xx
Service Unavailable
Server temporarily overloaded or down.
504
5xx
Gateway Timeout
Upstream server did not respond in time.
505
5xx
HTTP Version Not Supported
HTTP version not supported by server.

How to use this tool

  1. Type a status code (e.g. 404) or phrase (e.g. not found) in the search box.
  2. Use category chips to filter by 1xx, 2xx, 3xx, 4xx, or 5xx.
  3. Copy codes and descriptions for API docs, error handling, or debugging.

About HTTP Status Codes Reference

This utility helps you quickly find HTTP status code meanings when debugging APIs, writing error handlers, or documenting endpoints. It covers common codes; RFCs define the authoritative semantics.

Common use cases

  • Looking up status codes while debugging API responses
  • Choosing appropriate codes for REST endpoint design
  • Writing error messages or client handling logic

FAQ

What does this HTTP status codes tool do?
It lets you search and browse HTTP status codes by number or keyword, grouped by category (1xx through 5xx). Use it for quick reference during API work.
Does this tool validate or enforce HTTP protocol?
No. It is a local reference lookup only. It does not validate requests, responses, or enforce any protocol rules.
Are all HTTP status codes included?
The tool includes common codes developers encounter. The IANA registry and RFC 9110 define the full official set.
How do I search by phrase vs by code?
Type a number to match by code (exact or prefix). Type words to match the status name or description. Both are case-insensitive.

Related tools