Does HTTP Status Code Reference store my data?

No. All processing happens in your browser. We never see, store, or transmit your data to any server.

Does HTTP Status Code Reference work offline?

Yes, once the page is loaded, the tool works offline since all processing is client-side.

Is HTTP Status Code Reference secure to use?

Yes. Your data never leaves your browser — all processing happens client-side with zero server transmission. We use HTTPS encryption for the site itself.

Built with❤️by theCodelithLabs Engineering Team

Remove Ads + Priority SupportGo Premium

Developer ToolsRuns in Browser (Private)

HTTP Status Code Reference

Searchable reference for all HTTP status codes (1xx–5xx) with descriptions, causes, and examples.

4.8/5

Used by 728 developers today

Updated 15 Mar 2026

Loading tool...

Was this tool helpful?

Remove ads and work faster? Go Premium.

Unlock Premium

How to Use HTTP Status Code Reference

Features

Why Choose HTTP Status Code Reference?

Common Use Cases

Technical Details

Best Practices

Frequently Asked Questions

Is HTTP Status Code Reference really free?

Do you store my data?

Can I use this for commercial projects?

Does it work offline?

What browsers are supported?

Related Tools

Developer Tools

API Tester

Test REST API endpoints with custom methods, headers, and body — like Postman in your browser.

Developer Tools

cURL to Fetch Converter

Convert cURL commands to JavaScript fetch code. Supports headers, body, and auth.

Developer Tools

JSON Schema Generator

Auto-generate JSON Schema (Draft-07 / 2020-12) from any JSON object with nested definitions.

Developer Tools

GraphQL Query Builder

Build GraphQL queries, mutations, and fragments visually without writing raw syntax.

Loading…

Built with❤️by theCodelithLabs Engineering Team

Remove Ads + Priority SupportGo Premium

Developer ToolsRuns in Browser (Private)

HTTP Status Code Reference

Searchable reference for all HTTP status codes (1xx–5xx) with descriptions, causes, and examples.

4.8/5

Used by 728 developers today

Updated 15 Mar 2026

HTTP Status Codes Reference: Search and browse all HTTP status codes with descriptions and use cases.

Continue

Server received request headers, client should proceed with body

Switching Protocols

Server is switching protocols as requested

Processing

Server is processing request (WebDAV)

Early Hints

Returns some response headers before final response

Request succeeded. Standard response for successful HTTP requests

Created

Request succeeded and new resource created. Typical for POST requests

Accepted

Request accepted for processing, but not completed yet

Non-Authoritative Information

Returned meta-information is not from origin server

No Content

Request succeeded but no content to return. Common for DELETE

Reset Content

Request succeeded, client should reset document view

Partial Content

Partial resource delivered (Range header). Used for resumable downloads

Multi-Status

Multiple status codes for multiple resources (WebDAV)

Multiple Choices

Multiple options for the resource

Moved Permanently

Resource moved permanently. Future requests should use new URL

Found

Resource temporarily at different URI. Use original for future requests

See Other

Response found at different URI. Use GET for redirect

Not Modified

Resource not modified since last request. Use cached version

Temporary Redirect

Temporary redirect, use same HTTP method

Permanent Redirect

Permanent redirect, use same HTTP method

Bad Request

Malformed request syntax, invalid parameters

Unauthorized

Authentication required. Include WWW-Authenticate header

Payment Required

Reserved for future use (digital payment)

Forbidden

Server understood but refuses to authorize. Authentication won't help

Not Found

Resource not found at specified URI

Method Not Allowed

HTTP method not allowed for this resource

Not Acceptable

Can't provide content matching Accept headers

Proxy Authentication Required

Authentication with proxy required

Request Timeout

Server timed out waiting for request

Conflict

Request conflicts with current state of resource

Gone

Resource permanently removed, no forwarding address

Length Required

Content-Length header required

Precondition Failed

Precondition in headers evaluated to false

Payload Too Large

Request entity too large for server to process

URI Too Long

Request URI too long for server to process

Unsupported Media Type

Media type not supported by server

Range Not Satisfiable

Requested range not available

Expectation Failed

Expect header requirements cannot be met

I'm a Teapot

April Fools' joke RFC 2324. Server refuses to brew coffee

Unprocessable Entity

Request well-formed but semantic errors (WebDAV)

Locked

Resource is locked (WebDAV)

Too Many Requests

Rate limited. Check Retry-After header

Unavailable For Legal Reasons

Blocked for legal reasons (censorship)

Internal Server Error

Generic server error, unexpected condition

Not Implemented

Server doesn't support functionality required

Bad Gateway

Invalid response from upstream server

Service Unavailable

Server temporarily unavailable (overload/maintenance)

Gateway Timeout

Upstream server didn't respond in time

HTTP Version Not Supported

HTTP version in request not supported

Insufficient Storage

Server unable to store representation (WebDAV)

Loop Detected

Infinite loop detected while processing (WebDAV)

Network Authentication Required

Client needs to authenticate for network access

Quick Reference:

1xx Informational

2xx Success

3xx Redirection

4xx Client Error

5xx Server Error

Loading tool...

Was this tool helpful?

Remove ads and work faster? Go Premium.

Unlock Premium

How to Use HTTP Status Code Reference

Features

Why Choose HTTP Status Code Reference?

Common Use Cases

Technical Details

Best Practices

Frequently Asked Questions

Is HTTP Status Code Reference really free?

Do you store my data?

Can I use this for commercial projects?

Does it work offline?

What browsers are supported?

Related Tools

Developer Tools

API Tester

Test REST API endpoints with custom methods, headers, and body — like Postman in your browser.

Developer Tools

cURL to Fetch Converter

Convert cURL commands to JavaScript fetch code. Supports headers, body, and auth.

Developer Tools

JSON Schema Generator

Auto-generate JSON Schema (Draft-07 / 2020-12) from any JSON object with nested definitions.

Developer Tools

GraphQL Query Builder

Build GraphQL queries, mutations, and fragments visually without writing raw syntax.

HTTP Status Codes Reference: Search and browse all HTTP status codes with descriptions and use cases.

Continue

Server received request headers, client should proceed with body

Switching Protocols

Server is switching protocols as requested

Processing

Server is processing request (WebDAV)

Early Hints

Returns some response headers before final response

Request succeeded. Standard response for successful HTTP requests

Created

Request succeeded and new resource created. Typical for POST requests

Accepted

Request accepted for processing, but not completed yet

Non-Authoritative Information

Returned meta-information is not from origin server

No Content

Request succeeded but no content to return. Common for DELETE

Reset Content

Request succeeded, client should reset document view

Partial Content

Partial resource delivered (Range header). Used for resumable downloads

Multi-Status

Multiple status codes for multiple resources (WebDAV)

Multiple Choices

Multiple options for the resource

Moved Permanently

Resource moved permanently. Future requests should use new URL

Found

Resource temporarily at different URI. Use original for future requests

See Other

Response found at different URI. Use GET for redirect

Not Modified

Resource not modified since last request. Use cached version

Temporary Redirect

Temporary redirect, use same HTTP method

Permanent Redirect

Permanent redirect, use same HTTP method

Bad Request

Malformed request syntax, invalid parameters

Unauthorized

Authentication required. Include WWW-Authenticate header

Payment Required

Reserved for future use (digital payment)

Forbidden

Server understood but refuses to authorize. Authentication won't help

Not Found

Resource not found at specified URI

Method Not Allowed

HTTP method not allowed for this resource

Not Acceptable

Can't provide content matching Accept headers

Proxy Authentication Required

Authentication with proxy required

Request Timeout

Server timed out waiting for request

Conflict

Request conflicts with current state of resource

Gone

Resource permanently removed, no forwarding address

Length Required

Content-Length header required

Precondition Failed

Precondition in headers evaluated to false

Payload Too Large

Request entity too large for server to process

URI Too Long

Request URI too long for server to process

Unsupported Media Type

Media type not supported by server

Range Not Satisfiable

Requested range not available

Expectation Failed

Expect header requirements cannot be met

I'm a Teapot

April Fools' joke RFC 2324. Server refuses to brew coffee

Unprocessable Entity

Request well-formed but semantic errors (WebDAV)

Locked

Resource is locked (WebDAV)

Too Many Requests

Rate limited. Check Retry-After header

Unavailable For Legal Reasons

Blocked for legal reasons (censorship)

Internal Server Error

Generic server error, unexpected condition

Not Implemented

Server doesn't support functionality required

Bad Gateway

Invalid response from upstream server

Service Unavailable

Server temporarily unavailable (overload/maintenance)

Gateway Timeout

Upstream server didn't respond in time

HTTP Version Not Supported

HTTP version in request not supported

Insufficient Storage

Server unable to store representation (WebDAV)

Loop Detected

Infinite loop detected while processing (WebDAV)

Network Authentication Required

Client needs to authenticate for network access

Quick Reference:

1xx Informational

2xx Success

3xx Redirection

4xx Client Error

5xx Server Error

Tool

HTTP Status Code Reference

How to Use HTTP Status Code Reference

Features

Why Choose HTTP Status Code Reference?

Common Use Cases

Technical Details

Best Practices

Frequently Asked Questions

Related Topics

Related Tools

API Tester

cURL to Fetch Converter

JSON Schema Generator

GraphQL Query Builder

Tool

HTTP Status Code Reference

How to Use HTTP Status Code Reference

Features

Why Choose HTTP Status Code Reference?

Common Use Cases

Technical Details

Best Practices

Frequently Asked Questions

Related Topics

Related Tools

API Tester

cURL to Fetch Converter

JSON Schema Generator

GraphQL Query Builder