HTTP Status Code Dictionary

Searchable reference of every HTTP status code with category, meaning and typical causes.

50 of 50 codes

100
Continue
Server received headers; client should proceed with the body.
101
Switching Protocols
Agreed to switch protocol, e.g. HTTP → WebSocket.
102
Processing
Server is still working on the request.
200
OK
Standard success — GET returned the payload, PUT saved it.
201
Created
Resource created; usually with a Location header.
202
Accepted
Request accepted for processing but not finished yet.
204
No Content
Success with no body (e.g. DELETE).
206
Partial Content
Range request satisfied — partial download in progress.
300
Multiple Choices
Several possible representations; pick one.
301
Moved Permanently
URL permanently moved — update bookmarks (cached forever).
302
Found
Temporary redirect (historically for POST → GET).
303
See Other
Fetch the result elsewhere with GET.
304
Not Modified
Client cache is still valid — no body sent.
307
Temporary Redirect
Temp redirect preserving method and body.
308
Permanent Redirect
Permanent redirect preserving method and body.
400
Bad Request
Malformed syntax, bad parameters or failed validation.
401
Unauthorized
Authentication required or failed (login first).
402
Payment Required
Reserved for monetisation / subscription gates.
403
Forbidden
Server understood but refuses — you lack permission.
404
Not Found
No resource at this URL — most common broken-link code.
405
Method Not Allowed
HTTP verb not supported for this endpoint.
406
Not Acceptable
No representation matches the Accept headers.
407
Proxy Auth Required
Authenticate with the proxy first.
408
Request Timeout
Client took too long to send the request.
409
Conflict
Request conflicts with current state (e.g. duplicate create).
410
Gone
Resource permanently removed — don't retry.
411
Length Required
Content-Length header missing but required.
412
Precondition Failed
If-Match / If-None-Match condition failed.
413
Payload Too Large
Body exceeds server size limits.
414
URI Too Long
URL exceeded the server's length limit.
415
Unsupported Media Type
Content-Type not accepted by this endpoint.
416
Range Not Satisfiable
Requested byte range is outside the file.
417
Expectation Failed
Expect header requirement cannot be met.
418
I'm a Teapot
April Fools' RFC 2324 — refuses to brew coffee.
422
Unprocessable Content
Well-formed JSON but semantic validation errors.
423
Locked
Resource is locked (e.g. WebDAV).
425
Too Early
Request replayed too early — send it again.
426
Upgrade Required
Client must switch protocol (e.g. HTTP/2 or TLS).
428
Precondition Required
Origin server requires conditional request headers.
429
Too Many Requests
Rate limit hit — back off and retry later.
431
Request Header Fields Too Large
Headers exceeded server limits.
451
Unavailable For Legal Reasons
Blocked by legal demand (censorship).
500
Internal Server Error
Unhandled exception on the server — the generic crash.
501
Not Implemented
Server does not support this HTTP method.
502
Bad Gateway
Upstream server returned an invalid response.
503
Service Unavailable
Server down or overloaded — usually temporary.
504
Gateway Timeout
Upstream server didn't respond in time.
505
HTTP Version Not Supported
Requested HTTP version not supported.
507
Insufficient Storage
Not enough storage to complete the request (WebDAV).
511
Network Auth Required
Client must authenticate with the network (captive portal).

About HTTP Status Code Dictionary

Searchable reference of every HTTP status code with category, meaning and typical causes.

HTTP Status Code Dictionary is a searchable reference for every status a server can return. Type a number such as 404 or 503, or search by keyword like rate limit or redirect, and the matching codes appear with their official name, class category, meaning and the typical causes that produce them. The one hundred level informational codes, two hundred level successes, three hundred level redirects, four hundred level client errors and five hundred level server errors are grouped and color coded so patterns are easy to spot. Each entry lists when a client should retry, whether the response is cacheable, and which headers often accompany it, with examples from common web servers and APIs. Results filter as you type, so the dictionary works as a fast lookup during debugging, code review or an incident. HTTP Status Code Dictionary is free, needs no login and loads instantly in your browser.

How to Use HTTP Status Code Dictionary

  1. Paste your code, markup or configuration into the editor.
  2. Choose the output format or options offered.
  3. The formatted result updates live.
  4. Copy or download the finished code.

Key Features

  • Clean, consistently formatted output ready to paste.
  • Supports the common formats used in web development.
  • One-click copy and download — no build step required.

Frequently Asked Questions

What does an HTTP Status Code Dictionary entry include?

Each entry shows the numeric code, its official name, the class it belongs to such as client error or server error, a plain meaning, and the usual causes that trigger it. You also learn whether the response can be cached, when it is safe to retry, which headers typically appear, and a short example drawn from real web server and API behavior, all reachable with a quick search.

Is HTTP Status Code Dictionary free to use?

Yes. HTTP Status Code Dictionary is completely free with unlimited use — no account, download or payment required.

Is my data uploaded to a server?

No. HTTP Status Code Dictionary runs entirely in your browser. Your inputs are never sent to our servers or stored anywhere.

Does HTTP Status Code Dictionary work on mobile?

Yes. The interface is fully responsive and works in any modern browser on Android, iPhone, tablets and desktops.

Related Code Tools

Browse all 47 Code Tools →