HTTP Status Codes Online — Free Tool

Quickly look up definitions, causes, and standard use cases for HTTP network response status codes.

Search
Search by code, phrase, or category (e.g. “404”, “rate limit”, “server error”).
Results: 31
Code
Status
Copy
100
Continue
Request received; client can continue.
Informational
101
Switching Protocols
Server is switching protocols as requested.
Informational
102
Processing
Server has received and is processing the request.
Informational
103
Early Hints
Hints to preload resources while the final response is prepared.
Informational
200
OK
Request succeeded.
Success
201
Created
New resource created successfully.
Success
202
Accepted
Request accepted for processing (not completed yet).
Success
204
No Content
Request succeeded but no content to return.
Success
206
Partial Content
Partial response for range requests.
Success
301
Moved Permanently
Resource moved permanently (use new URL).
Redirection
302
Found
Temporary redirect.
Redirection
304
Not Modified
Cached version is still valid.
Redirection
307
Temporary Redirect
Temporary redirect; method and body must not change.
Redirection
308
Permanent Redirect
Permanent redirect; method and body must not change.
Redirection
400
Bad Request
Malformed request or invalid parameters.
Client Error
401
Unauthorized
Authentication required or failed.
Client Error
403
Forbidden
Authenticated but not allowed.
Client Error
404
Not Found
Resource not found.
Client Error
405
Method Not Allowed
HTTP method not supported for this endpoint.
Client Error
408
Request Timeout
Client took too long to send the request.
Client Error
409
Conflict
Request conflicts with current state.
Client Error
413
Payload Too Large
Request payload exceeds server limits.
Client Error
415
Unsupported Media Type
Request content type not supported.
Client Error
418
I'm a teapot
A playful status code used in some APIs/tests.
Client Error
422
Unprocessable Content
Semantically invalid content (often validation errors).
Client Error
429
Too Many Requests
Rate limited.
Client Error
500
Internal Server Error
Unexpected server error.
Server Error
501
Not Implemented
Server does not support the functionality.
Server Error
502
Bad Gateway
Invalid response from upstream server.
Server Error
503
Service Unavailable
Server unavailable (overloaded or down).
Server Error
504
Gateway Timeout
Upstream server did not respond in time.
Server Error
Privacy note: All processing happens entirely in your browser. No data is sent to our servers.

About this tool

HTTP Status Codes is a fast, browser-based developer utility. Quickly look up definitions, causes, and standard use cases for HTTP network response status codes. To use it, paste or upload your input in the tool above, choose any options (like formatting style, separators, or output type), and copy or download the result. Because it runs in your browser, it’s ideal for quick edits, previews, and conversions without installing extra software. Common use cases include cleaning up data before sharing, converting formats for a spreadsheet or API, validating content before deployment, and generating outputs you can paste directly into your codebase. If you handle sensitive data, prefer tools that run locally in your browser—this helps reduce the risk of uploading private content to a server.

How to use

  1. Enter or upload your input in the tool panel above.
  2. Adjust any options if provided.
  3. Copy or download the output.

This page is available at /tools/http-status-code-reference.

Related keywords

http status codeshttp status code reference404500status code list

FAQ

What is HTTP Status Codes?

HTTP Status Codes is an online tool that helps you quickly look up definitions, causes, and standard use cases for http network response status codes.

How do I use the HTTP Status Codes?

Add your input in the tool panel, adjust options if available, then copy or download the output.

Is this tool free?

Yes—this tool is free to use.

Does it run locally in the browser?

Most tools are designed to run in your browser. If a tool uploads files to a server, it should say so in the UI.