Santekno/tools
CategoriesTutorials

HTTP Status Codes

Searchable reference of all HTTP status codes with descriptions and RFC links.

Processed in your browserUpdated · Jan 2026
HTTP Status Codes61
100
Continue
The client should continue with its request.
RFC 9110
101
Switching Protocols
The server is switching protocols as requested by the client.
RFC 9110
102
Processing
WebDAV: server has accepted the request and is processing it.
RFC 2518
103
Early Hints
Used to return some response headers before final response.
RFC 8297
200
OK
The request succeeded.
RFC 9110
201
Created
The request has been fulfilled and a new resource was created.
RFC 9110
202
Accepted
The request has been accepted for processing, but processing is not complete.
RFC 9110
203
Non-Authoritative Information
The returned metadata is from a transformed proxy, not the origin server.
RFC 9110
204
No Content
The request succeeded but there is no content to return.
RFC 9110
205
Reset Content
The client should reset the document view.
RFC 9110
206
Partial Content
The server has fulfilled a partial GET request (range header).
RFC 9110
207
Multi-Status
WebDAV: multiple resource statuses in a single response.
RFC 4918
208
Already Reported
WebDAV: members of a DAV binding already enumerated.
RFC 5842
226
IM Used
Server has fulfilled GET request and response is a representation of instance-manipulation results.
RFC 3229
300
Multiple Choices
The request has more than one possible response.
RFC 9110
301
Moved Permanently
The URL of the requested resource has been permanently changed.
RFC 9110
302
Found
The URI of the requested resource has been temporarily changed.
RFC 9110
303
See Other
The server is redirecting to a different URI, accessible via GET.
RFC 9110
304
Not Modified
The resource has not been modified since the last request.
RFC 9110
307
Temporary Redirect
Like 302 but the HTTP method must not be changed.
RFC 9110
308
Permanent Redirect
Like 301 but the HTTP method must not be changed.
RFC 9110
400
Bad Request
The server cannot process the request due to client error (e.g., malformed syntax).
RFC 9110
401
Unauthorized
Authentication is required and has failed or has not been provided.
RFC 9110
402
Payment Required
Reserved for future use (originally intended for digital payment systems).
RFC 9110
403
Forbidden
The client does not have access rights to the content.
RFC 9110
404
Not Found
The server cannot find the requested resource.
RFC 9110
405
Method Not Allowed
The request method is not supported for the requested resource.
RFC 9110
406
Not Acceptable
The server cannot produce a response matching the Accept headers.
RFC 9110
407
Proxy Authentication Required
The client must first authenticate with the proxy.
RFC 9110
408
Request Timeout
The server timed out waiting for the request.
RFC 9110
409
Conflict
The request conflicts with the current state of the server.
RFC 9110
410
Gone
The requested resource has been permanently removed.
RFC 9110
411
Length Required
The server requires the Content-Length header.
RFC 9110
412
Precondition Failed
Preconditions in the request headers evaluated to false.
RFC 9110
413
Payload Too Large
The request entity is larger than the server is willing to process.
RFC 9110
414
URI Too Long
The URI requested is longer than the server is willing to interpret.
RFC 9110
415
Unsupported Media Type
The media format of the request is not supported.
RFC 9110
416
Range Not Satisfiable
The range specified by the Range header cannot be fulfilled.
RFC 9110
417
Expectation Failed
The expectation in the Expect header cannot be met.
RFC 9110
418
I'm a teapot
April Fools joke: the server is a teapot and cannot brew coffee.
RFC 2324
421
Misdirected Request
The request was directed at a server unable to produce a response.
RFC 9110
422
Unprocessable Entity
The request is well-formed but contains semantic errors.
RFC 9110
423
Locked
WebDAV: the resource is locked.
RFC 4918
424
Failed Dependency
WebDAV: request failed due to a previous request failing.
RFC 4918
425
Too Early
The server is unwilling to risk processing a request that might be replayed.
RFC 8470
426
Upgrade Required
The client should switch to a different protocol.
RFC 9110
428
Precondition Required
The server requires the request to be conditional.
RFC 6585
429
Too Many Requests
The user has sent too many requests in a given amount of time (rate limit).
RFC 6585
431
Request Header Fields Too Large
The server is unwilling to process the request because its header fields are too large.
RFC 6585
451
Unavailable For Legal Reasons
The resource is unavailable due to legal reasons.
RFC 7725
500
Internal Server Error
The server encountered an unexpected condition.
RFC 9110
501
Not Implemented
The server does not support the functionality required.
RFC 9110
502
Bad Gateway
The server, acting as a gateway, received an invalid response.
RFC 9110
503
Service Unavailable
The server is not ready to handle the request (overloaded or down for maintenance).
RFC 9110
504
Gateway Timeout
The server, acting as a gateway, did not receive a timely response.
RFC 9110
505
HTTP Version Not Supported
The HTTP version used in the request is not supported.
RFC 9110
506
Variant Also Negotiates
Transparent content negotiation results in a circular reference.
RFC 2295
507
Insufficient Storage
WebDAV: the server cannot store the representation needed to complete the request.
RFC 4918
508
Loop Detected
WebDAV: the server detected an infinite loop while processing.
RFC 5842
510
Not Extended
Further extensions to the request are required for the server to fulfill it.
RFC 2774
511
Network Authentication Required
The client needs to authenticate to gain network access (e.g., captive portal).
RFC 6585
61 of 61 codesSource: RFC 9110, RFC 4918, RFC 6585

How to use HTTP Status Codes

Paste your input on the left, choose the options you want, and the output appears instantly on the right. Everything runs in your browser — none of your data is sent to a server.

  • Paste or type your input in the INPUT panel
  • The output regenerates automatically as you type
  • Use Copy to put the result in your clipboard
  • Click Sample to load a working example

What is HTTP Status Codes?

Complete reference of HTTP status codes from RFC 9110 and related specs. Search by code (e.g. "404"), name ("not found"), category ("4xx"), or any keyword. Each entry shows the description in English and Indonesian, plus the source RFC. Perfect for API debugging and design. This tool is part of santekno's developer toolbox — a curated collection of utilities built for engineers who care about speed, privacy, and simplicity.

Common use cases

  • Debugging API payloads and integration issues
  • Inspecting tokens, hashes, or encoded strings during development
  • Generating fixtures and sample data for tests
  • Sharing readable output with teammates in code reviews

FAQ

401 means "not authenticated" — the user needs to log in. 403 means "not authorized" — the user is logged in but lacks permission.