HTTP Status Codes
Searchable reference for common HTTP status codes.
| Code | Name | Category | Description |
|---|---|---|---|
| 100 | Continue | informational | Client should continue the request. |
| 101 | Switching Protocols | informational | Server is switching protocols as requested. |
| 102 | Processing | informational | Server received and is processing the request. |
| 103 | Early Hints | informational | Preload hints before the final response. |
| 200 | OK | success | Request succeeded. |
| 201 | Created | success | Resource was created successfully. |
| 202 | Accepted | success | Request accepted for processing. |
| 204 | No Content | success | Success with no response body. |
| 206 | Partial Content | success | Partial resource returned for range requests. |
| 301 | Moved Permanently | redirect | Resource permanently moved to a new URL. |
| 302 | Found | redirect | Resource temporarily moved to another URL. |
| 304 | Not Modified | redirect | Cached version is still valid. |
| 307 | Temporary Redirect | redirect | Temporary redirect preserving request method. |
| 308 | Permanent Redirect | redirect | Permanent redirect preserving request method. |
| 400 | Bad Request | client-error | Request syntax or parameters are invalid. |
| 401 | Unauthorized | client-error | Authentication is required. |
| 403 | Forbidden | client-error | Authenticated but not allowed to access the resource. |
| 404 | Not Found | client-error | Requested resource does not exist. |
| 405 | Method Not Allowed | client-error | HTTP method is not supported for this route. |
| 408 | Request Timeout | client-error | Server timed out waiting for the request. |
| 409 | Conflict | client-error | Request conflicts with current resource state. |
| 410 | Gone | client-error | Resource is permanently unavailable. |
| 413 | Payload Too Large | client-error | Request body exceeds server limits. |
| 415 | Unsupported Media Type | client-error | Content type is not supported. |
| 418 | I'm a teapot | client-error | April Fools' RFC 2324 reference status. |
| 422 | Unprocessable Entity | client-error | Validation failed for a well-formed request. |
| 429 | Too Many Requests | client-error | Rate limit exceeded. |
| 500 | Internal Server Error | server-error | Unexpected server-side failure. |
| 501 | Not Implemented | server-error | Server does not support the requested feature. |
| 502 | Bad Gateway | server-error | Invalid response from upstream server. |
| 503 | Service Unavailable | server-error | Server temporarily unavailable. |
| 504 | Gateway Timeout | server-error | Upstream server did not respond in time. |
HTTP status codes tell you whether an API call succeeded, redirected, failed validation, or hit a server error - but memorizing every code is impractical. Utilitoo's HTTP Status Codes reference lists common codes with plain-language names, categories, and descriptions you can search instantly while debugging APIs, reviewing logs, or writing documentation.
Backend developers interpreting fetch errors, frontend engineers handling axios responses, technical writers documenting API behavior, and students learning web fundamentals all need a quick status code lookup without opening multiple browser tabs.
Search by code number, name, or keyword like "not found" or "timeout." Results show informational, success, redirect, client error, and server error categories with color-coded badges. Pair with HTTP Header Viewer when inspecting live responses or MIME Type Lookup when checking Content-Type headers.
This reference runs entirely in your browser on Utilitoo. No account required and no data is collected. Free for developers, ops teams, and anyone building or consuming HTTP APIs.
HTTP Status Codes helps interpret network and protocol details during debugging. Searchable reference for common HTTP status codes. Treat geolocation and vendor metadata as hints - routing and policy decisions need authoritative sources.
Common use cases
- Turning messy http status codes data into something readable during a live debugging session.
- Sanity-checking exports from databases, queues, or SaaS admin panels with HTTP Status Codes.
- Building fixtures and examples for docs or tests from real http status codes samples.
- Avoiding a full IDE or CLI install when you only need a one-off http status codes transform.
- Reproducing a reported bug by pasting the exact http status codes payload the user shared.
Tips & common mistakes
Use HTTP Status Codes when you need a fast browser-side check: Searchable reference for common HTTP status codes. Prefer plain-text pastes over rich HTML from email clients. For production-bound transforms, validate on a staging copy first. Large inputs can slow a tab - split multi-megabyte blobs when the UI feels sluggish.
Common errors
- Unexpected output from HTTP Status Codes - double-check input format, encoding, and whether the paste was truncated.
- Browser limits - very large inputs may slow the tab; split into smaller chunks if performance drops.
How to use
- Search by code, name, or description.
- Browse the matching status code table.
- Use it while debugging APIs and web apps.
Frequently Asked Questions
What is an HTTP status code?▼
An HTTP status code is a three-digit number in every HTTP response indicating whether the request succeeded, redirected, or failed.
What does HTTP 404 mean?▼
404 Not Found means the server could not locate the requested resource at the given URL.
What is the difference between 401 and 403?▼
401 Unauthorized means authentication is required or failed. 403 Forbidden means the client is authenticated but not allowed to access the resource.
Can I search status codes by name?▼
Yes. Search by number, name, or description keywords like gateway, timeout, or redirect.
Is this status code list updated?▼
Utilitoo covers the most commonly used standard HTTP status codes developers encounter in production APIs and web apps.
Related Tools
HTTP Header Viewer
View HTTP response headers for any URL.
MIME Type Lookup
Look up MIME types by extension or media type.
User Agent Parser
Parse browser user agent strings.
Locale Converter
Convert BCP 47, POSIX, and Accept-Language locale strings.
DNS Lookup
Look up DNS records for any domain.
IP Lookup
Look up IP address information.