New
browser-only
No account required

HTTP Status Reference

Search common HTTP response status codes by number, name, category, or purpose while debugging APIs and web applications.

HTTP status codes
Search common registered response codes by number, name, or purpose.
100
Informational

Continue

The server received the headers and the client can continue.

101
Informational

Switching Protocols

The server is switching protocols as requested.

200
Success

OK

The request succeeded.

201
Success

Created

A new resource was created.

202
Success

Accepted

The request was accepted for asynchronous processing.

204
Success

No Content

The request succeeded with no response body.

206
Success

Partial Content

The response contains the requested byte range.

301
Redirect

Moved Permanently

The resource has a permanent new URL.

302
Redirect

Found

The resource is temporarily available elsewhere.

304
Redirect

Not Modified

The cached representation remains valid.

307
Redirect

Temporary Redirect

Repeat the request at another URL without changing its method.

308
Redirect

Permanent Redirect

Permanently repeat the request at another URL without changing its method.

400
Client error

Bad Request

The request syntax or parameters are invalid.

401
Client error

Unauthorized

Authentication is required or failed.

403
Client error

Forbidden

The server understood but refuses the request.

404
Client error

Not Found

The requested resource does not exist.

405
Client error

Method Not Allowed

The resource does not support this HTTP method.

409
Client error

Conflict

The request conflicts with the current resource state.

410
Client error

Gone

The resource was intentionally removed.

413
Client error

Content Too Large

The request content exceeds the server limit.

415
Client error

Unsupported Media Type

The content type is not supported.

418
Client error

I'm a Teapot

An April Fools status retained in the HTTP registry.

422
Client error

Unprocessable Content

The syntax is valid but semantic processing failed.

425
Client error

Too Early

The server will not process a potentially replayed request.

429
Client error

Too Many Requests

The client exceeded a rate limit.

500
Server error

Internal Server Error

The server encountered an unexpected failure.

501
Server error

Not Implemented

The server does not support the requested functionality.

502
Server error

Bad Gateway

An upstream server returned an invalid response.

503
Server error

Service Unavailable

The service is temporarily unable to handle requests.

504
Server error

Gateway Timeout

An upstream server did not respond in time.

The Complete Guide

About the HTTP Status Reference

Search common HTTP response status codes by number, name, category, or purpose while debugging APIs and web applications.

Your input is processed locally in your browser and is not uploaded.

How to use HTTP Status Reference

1

Enter your input

Add the value or settings you want to process.

2

Review the result

Check the generated output and any validation messages.

3

Copy, save, or reset

Copy the result, save locally, or start over.

Common Use Cases

Complete a quick http status reference task without installing software.

Use HTTP Status Reference for this workflow without sending the input to an external service.

Keep a reusable result or draft in your local workspace.

Use HTTP Status Reference for this workflow without sending the input to an external service.

Combine the output with related tools in the same workflow.

Use HTTP Status Reference for this workflow without sending the input to an external service.

Frequently Asked Questions

Common questions about HTTP Status Reference.

Related searches:

http
status
code
response
404
500
api