HTTP Status Codes Reference — Free Online Tool | T1000

1xx Informational

100

Continue

The server has received the request headers and the client should proceed to send the request body.

101

Switching Protocols

The requester has asked the server to switch protocols and the server has agreed to do so.

102

Processing

The server has received and is processing the request, but no response is available yet (WebDAV).

103

Early Hints

Used to return some response headers before final HTTP message.

2xx Success

200

Standard successful HTTP response. The request has succeeded.

201

Created

The request has succeeded and a new resource has been created as a result.

202

Accepted

The request has been received but not yet acted upon.

203

Non-Authoritative Information

The returned meta-information is not identical to what was available from the origin server.

204

No Content

There is no content to send for this request, but the headers may be useful.

205

Reset Content

Tells the user agent to reset the document which sent this request.

206

Partial Content

The server is delivering only part of the resource due to a Range header sent by the client.

3xx Redirection

301

Moved Permanently

The URL of the requested resource has been changed permanently.

302

Found

The URI of requested resource has been changed temporarily.

304

Not Modified

This is used for caching purposes — client may use its cached version.

307

Temporary Redirect

The server sends this response to direct the client to get the requested resource at another URI using the same method.

308

Permanent Redirect

The resource is now permanently located at another URI, specified in the Location header.

4xx Client Error

400

Bad Request

The server could not understand the request due to invalid syntax.

401

Unauthorized

The client must authenticate itself to get the requested response.

403

Forbidden

The client does not have access rights to the content.

404

Not Found

The server can not find the requested resource.

405

Method Not Allowed

The request method is known by the server but is not supported by the target resource.

408

Request Timeout

The server would like to shut down this unused connection.

409

Conflict

The request conflicts with the current state of the server.

410

Gone

The requested content has been permanently deleted from the server.

413

Content Too Large

Request entity is larger than limits defined by the server.

414

URI Too Long

The URI requested by the client is longer than the server is willing to interpret.

415

Unsupported Media Type

The media format of the requested data is not supported by the server.

422

Unprocessable Content

The request was well-formed but was unable to be followed due to semantic errors.

429

Too Many Requests

The user has sent too many requests in a given amount of time (rate limiting).

5xx Server Error

500

Internal Server Error

The server has encountered a situation it does not know how to handle.

501

Not Implemented

The request method is not supported by the server and cannot be handled.

502

Bad Gateway

The server, while working as a gateway, got an invalid response.

503

Service Unavailable

The server is not ready to handle the request. Common causes: down for maintenance or overloaded.

504

Gateway Timeout

The server is acting as a gateway and cannot get a response in time.

505

HTTP Version Not Supported

The HTTP version used in the request is not supported by the server.

What is HTTP Status Codes Reference?

HTTP Status Codes Reference is a free online developer utility. Look up all HTTP status codes across 1xx, 2xx, 3xx, 4xx, and 5xx ranges with names and descriptions. Searchable, color-coded reference — essential for developers and API designers. It runs entirely client-side using modern browser APIs — no server, no API key, no sign-up required.

How to use HTTP Status Codes Reference

Getting started is instant:

✓Paste your input (code, string, or data) into the input field.
✓The output is generated immediately in your browser.
✓Copy the result with the one-click copy button.
✓Use it directly in your project, API, or debug workflow.

Why use HTTP Status Codes Reference?

HTTP Status Codes Reference saves developer time by eliminating the need to write one-off scripts or search for library documentation. All processing is local — your sensitive data never reaches a server. It is also completely free with no rate limits.

Frequently Asked Questions

How do I use HTTP Status Codes Reference?

Look up all HTTP status codes across 1xx, 2xx, 3xx, 4xx, and 5xx ranges with names and descriptions. Searchable, color-coded reference — essential for developers and API designers. Paste your input, and the output is generated instantly in your browser.

Is HTTP Status Codes Reference free?

Yes, HTTP Status Codes Reference is 100% free with no rate limits or API keys required.

Is HTTP Status Codes Reference secure?

All processing happens locally in your browser — your data is never sent to any server.

Can I use HTTP Status Codes Reference in production?

HTTP Status Codes Reference is great for development, debugging and quick conversions. For production pipelines, integrate the same logic server-side.

Does HTTP Status Codes Reference work offline?

Yes — HTTP Status Codes Reference is a fully client-side tool that works without an internet connection once loaded.

Related Tools

💻

JSON Formatter

Format, prettify, and validate JSON online. Instantly beautify minified JSON with proper indentation and syntax highlighting. Free JSON formatter tool.

💻

UUID Generator

Generate RFC 4122 compliant UUIDs (v1 and v4) instantly online. Bulk generate unique identifiers for databases, APIs, and software development.

💻

Base64 Encoder

Encode any text or string to Base64 format instantly. Used for encoding data for URLs, emails, and APIs. Free online Base64 encoder tool.