Devkitrdevkitr

HTTP Status Codes Reference

Complete HTTP status codes reference — search all HTTP response codes (1xx–5xx) with descriptions, meanings, and usage guides for every status code.

100% Private Instant Results
100
Continue
The server has received the request headers and the client should proceed to send the request body.
101
Switching Protocols
The server is switching protocols as requested by the client.
200
OK
The request has succeeded. Standard response for successful HTTP requests.
201
Created
The request has been fulfilled and a new resource has been created.
202
Accepted
The request has been accepted for processing, but processing is not complete.
204
No Content
The server has fulfilled the request but there is no content to return.
206
Partial Content
The server is delivering only part of the resource due to a range header.
301
Moved Permanently
The resource has been permanently moved to a new URL.
302
Found
The resource is temporarily located at a different URL.
304
Not Modified
The resource has not been modified since the last request.
307
Temporary Redirect
The request should be repeated with another URL, preserving the HTTP method.
308
Permanent Redirect
The resource has permanently moved, preserving the HTTP method.
400
Bad Request
The server cannot process the request due to malformed syntax.
401
Unauthorized
Authentication is required and has failed or not been provided.
403
Forbidden
The server understood the request but refuses to authorize it.
404
Not Found
The requested resource could not be found on the server.
405
Method Not Allowed
The HTTP method is not allowed for the requested resource.
408
Request Timeout
The server timed out waiting for the request.
409
Conflict
The request conflicts with the current state of the resource.
410
Gone
The resource is no longer available and will not be available again.
413
Payload Too Large
The request entity is larger than the server is willing to process.
415
Unsupported Media Type
The media type of the request data is not supported by the server.
422
Unprocessable Entity
The request was well-formed but could not be followed due to semantic errors.
429
Too Many Requests
The user has sent too many requests in a given amount of time.
500
Internal Server Error
The server encountered an unexpected condition that prevented it from fulfilling the request.
501
Not Implemented
The server does not support the functionality required to fulfill the request.
502
Bad Gateway
The server received an invalid response from the upstream server.
503
Service Unavailable
The server is currently unavailable (overloaded or down for maintenance).
504
Gateway Timeout
The upstream server failed to respond in time.
29 of 29 codes shown

About HTTP Status Codes Reference

A comprehensive, searchable reference of all HTTP status codes and HTTP response codes. Browse every status code organized by class — 1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error, and 5xx Server Error. Each HTTP status code includes a clear description, common use cases, related headers, and troubleshooting tips. Quickly look up what any HTTP response code means — from 200 OK and 301 Redirect to 403 Forbidden (not allowed), 404 Not Found, and 500 Internal Server Error. Use the search to filter by code number, name, or description. Essential for debugging HTTP errors, understanding API responses, and building web applications.

Key Features

  • Process and analyze data entirely in your browser — nothing is sent to any server
  • Handles edge cases, special characters, and large inputs gracefully
  • Intuitive interface designed for quick, daily developer tasks
  • Keyboard-friendly workflow for power users
  • Instant output with zero server round trips
  • Responsive design — works perfectly on desktop, tablet, and mobile

How to Use HTTP Status Codes Reference

  1. 1Enter your input data in the HTTP Status Codes Reference input area above
  2. 2Adjust any available options or settings to match your requirements
  3. 3Click the action button to process your data with HTTP Status Codes Reference
  4. 4Copy the result to your clipboard or download it for use in your project

When to Use HTTP Status Codes Reference

HTTP Status Codes Reference is ideal for developers who need a quick, reliable way to complete http status codes reference — search all http response codes (1xx–5xx) with descriptions, meanings, and usage guides for every status code. Whether you're working on a personal project, debugging production issues, or building enterprise applications, this tool saves time by handling dev utilities tasks directly in your browser without requiring any software installation or account setup.

Common use cases include day-to-day development workflows, code reviews, API debugging, data migration tasks, and quick one-off transformations. Since all processing happens client-side, HTTP Status Codes Reference is safe to use with sensitive or proprietary data — nothing ever leaves your machine.

Frequently Asked Questions

Q.What are HTTP status codes?

HTTP status codes are three-digit response codes returned by a server to indicate the result of an HTTP request. They are grouped into 5 classes: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error). Understanding these codes is essential for debugging HTTP errors and API responses.

Q.How many HTTP status codes are there?

There are about 60 officially defined HTTP status codes. The most common ones include 200 OK, 301 Moved Permanently, 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, and 500 Internal Server Error.

Q.What is the difference between 401 and 403?

401 Unauthorized means authentication is required — the request lacks valid credentials. 403 Forbidden (not allowed) means you are authenticated but do not have permission to access the resource. Both are HTTP client error status codes.

Q.What does a 500 status code mean?

500 Internal Server Error is an HTTP status code indicating the server encountered an unexpected condition. It's a generic server error response when no more specific 5xx code applies. Check server logs for the root cause.

Q.How do I fix HTTP errors?

Each HTTP error code points to a specific issue. 4xx errors indicate client-side problems (wrong URL, missing auth, bad request). 5xx errors indicate server-side issues. This reference explains each status code with troubleshooting guidance.

Q.Can I search for a specific status code?

Yes. Use the search box to filter by code number, name, or description to quickly find any HTTP status code and its meaning.

Related Articles

Regex Cheat Sheet for Developers — Patterns, Flags & Examples

A practical regex reference with common patterns, flags, lookaheads, and real-world examples for JavaScript, Python, and more.

2026-01-1511 min read

Cron Expressions Explained — Syntax, Examples & Common Schedules

Learn cron expression syntax from scratch — fields, wildcards, ranges, steps, and ready-to-use examples for common schedules.

2025-11-288 min read

Related Tools

Regex Tester

Free online regex tester — test and debug regular expressions with real-time matching, highlighting, and capture group display. Alternative to RegExr.

Text Diff Checker

Free online diff checker — compare text online side-by-side and highlight every difference. Fast text compare tool and DiffChecker alternative.

Word & Character Counter

Count words, characters, sentences, paragraphs, and estimate reading time.

Case Converter

Convert text between uppercase, lowercase, title case, camelCase, snake_case, and more.