Web & 認証

HTTP ステータスコードリファレンス

HTTP レスポンスコードを検索 / 参照し、意味、分類、よくある用途を確認できます。

無料で利用登録不要ブラウザ内で実行

1xx Informational

100

Continue

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

101

Switching Protocols

The server is switching protocols as requested (e.g., WebSocket upgrade).

2xx Success

200

The request succeeded. Standard response for successful HTTP requests.

201

Created

The request succeeded and a new resource was created. Common after POST requests.

204

No Content

The request succeeded but there is no content to return. Common for DELETE.

206

Partial Content

The server is delivering only part of the resource due to a range header.

3xx Redirection

301

Moved Permanently

The resource has been permanently moved to a new URL. Use for SEO redirects.

302

Found

The resource is temporarily at a different URL. Often used in OAuth redirects.

304

Not Modified

The resource has not been modified since the last request. Use cached version.

307

Temporary Redirect

Like 302 but preserves the HTTP method. Used in HSTS redirects.

308

Permanent Redirect

Like 301 but preserves the HTTP method.

4xx Client Error

400

Bad Request

The server cannot process the request due to invalid syntax or parameters.

401

Unauthorized

Authentication is required. The client must provide valid credentials.

403

Forbidden

The client does not have permission to access the resource, even with auth.

404

Not Found

The requested resource does not exist on the server.

405

Method Not Allowed

The HTTP method is not supported for the requested resource.

409

Conflict

The request conflicts with the current state of the resource.

410

Gone

The resource is permanently gone and will not be available again.

413

Payload Too Large

The request body exceeds the server limit.

415

Unsupported Media Type

The media type in the request is not supported by the server.

422

Unprocessable Entity

The request is well-formed but contains semantic errors (used in APIs).

429

Too Many Requests

The user has sent too many requests in a given time. Rate limiting.

5xx Server Error

500

Internal Server Error

Generic server error. Something unexpected went wrong.

502

Bad Gateway

The server received an invalid response from an upstream server.

503

Service Unavailable

The server is temporarily unable to handle the request (maintenance/overload).

504

Gateway Timeout

The upstream server did not respond in time.

What is HTTP ステータスコードリファレンス?

HTTP ステータスコードリファレンス helps people convert, inspect, validate, or generate http, status code, 200, 404, 500, 301 directly in the browser. It is designed for everyday work, coding, debugging, documentation, quality checks, and data preparation where clear input, reliable output, and privacy-first local processing matter.

HTTP ステータスコードリファレンスの使い方

1検索語、拡張子、コード、カテゴリなどで対象を絞り込みます。
2一覧や候補から必要な項目を選び、詳細や対応関係を確認します。
3参照値や説明をコピーするか、そのまま仕様確認に使います。

Common HTTP ステータスコードリファレンス use cases

Developer debugging

Use HTTP ステータスコードリファレンス to quickly inspect generated output, API payloads, configuration values, or encoded data while building and debugging software.

Review before reuse

Validate or transform http, status code, 200, 404, 500, 301 before adding the result to a project, document, form, message, or shared file.

Privacy-first browser processing

Run common http, status code, 200, 404, 500, 301 tasks locally in the browser without sending sensitive development data to a backend service.

よくある質問

What problem does HTTP ステータスコードリファレンス solve?