HTTP Status Codes & Log Analyzer

Look up HTTP status codes and analyze response lines or access logs with counts and explanations.

Analyze status lines or access logs

Codes or log lines — one per line

Accepts bare 100–599 codes, HTTP status lines, and common access logs with a quoted request followed by status and byte count. Up to 1,000 lines / 100,000 characters. Other lines are reported as ignored.

HTTP status reference

Search code, meaning or older name

Response class

64 reference entries. IANA naming checked October 6, 2026; 104 is temporary until November 13, 2026. Unassigned codes remain nonstandard.

100Continue

The client may continue sending the request body.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

101Switching Protocols

The server agrees to change protocol as requested.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

102Processing

Historical WebDAV interim processing response.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

103Early Hints

Interim hints can prepare resources before the final response.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

104Upload Resumption Supported

Temporary IANA registration for resumable uploads; currently expires 2026-11-13. Check the registry before relying on it.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

200OK

The request succeeded; the response meaning depends on the method.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

201Created

The request created one or more resources.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

202Accepted

Processing was accepted but has not necessarily completed or succeeded.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

203Non-Authoritative Information

A transforming proxy changed the origin's successful response.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

204No Content

The request succeeded without response content.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

205Reset Content

The client is asked to reset the document view; no response content is supplied.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

206Partial Content

The response contains selected ranges of a representation.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

207Multi-Status

WebDAV results for multiple resources or operations are in the body.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

208Already Reported

A WebDAV binding was already enumerated in a multi-status response.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

226IM Used

The response reflects instance manipulations applied to a representation.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

300Multiple Choices

Several representations or destinations are available.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

301Moved Permanently

The resource has a permanent new URI.

A client may change POST to GET when following this redirect. Use 308 or 307 when the method must be preserved; inspect Location.

302Found

The resource is temporarily available at another URI.

A client may change POST to GET when following this redirect. Use 308 or 307 when the method must be preserved; inspect Location.

303See Other

Retrieve the result through another URI.

Follow the other URI with a retrieval request (GET, or HEAD). This is commonly used after a POST.

304Not Modified

A conditional GET or HEAD can reuse its stored representation; this is not a navigation redirect.

Reuse the cached representation after applying response metadata. A 304 contains no response content.

305Use Proxy

Deprecated proxy-selection response; do not use for new implementations.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

306(Unused)

Reserved, unused code.

Interpret this code with the request method, response fields and body; a status by itself does not establish application-level success.

307Temporary Redirect

A temporary destination preserves the request method.

Automatic redirection must preserve the method and request content. Check Location and avoid forwarding credentials to an untrusted destination.

308Permanent Redirect

A permanent destination preserves the request method.

Automatic redirection must preserve the method and request content. Check Location and avoid forwarding credentials to an untrusted destination.

400Bad Request

The server cannot or will not process the request due to a perceived client error.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

401Unauthorized

Valid authentication credentials are missing or unacceptable.

Inspect WWW-Authenticate and provide valid credentials through the expected authentication flow.

402Payment Required

Reserved for future use; service-specific meanings vary.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

403Forbidden

The server understands the request and refuses it.

Check permissions and server policy; supplying credentials again does not guarantee access.

404Not Found

No current representation was found, or the server will not disclose one.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

405Method Not Allowed

The method is recognized but unavailable for this resource; inspect Allow.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

406Not Acceptable

No available representation satisfies the requested negotiation preferences.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

407Proxy Authentication Required

Authentication with the proxy is required.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

408Request Timeout

The server did not receive a complete request in time.

A retry may be appropriate after diagnosing the cause. Do not blindly repeat a non-idempotent operation; it may already have taken effect.

409Conflict

The request conflicts with the resource's current state.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

410Gone

The resource is no longer available and the condition is likely permanent.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

411Length Required

A defined Content-Length is required.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

412Precondition Failed

A request precondition evaluated to false.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

413Content Too Large

The request content exceeds what the server accepts.

Reduce request size. If the limit is temporary, the server may provide Retry-After.

414URI Too Long

The request URI exceeds what the server accepts.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

415Unsupported Media Type

The content's format or coding is unsupported for this request.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

416Range Not Satisfiable

The requested ranges cannot be satisfied.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

417Expectation Failed

The expectation in the request cannot be met.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

418(Unused)

IANA marks this reserved code unused; historically known as I'm a teapot.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

421Misdirected Request

This server cannot provide an authoritative response for the target URI.

A retry may be appropriate after diagnosing the cause. Do not blindly repeat a non-idempotent operation; it may already have taken effect.

422Unprocessable Content

The type and syntax are understood but the contained instructions cannot be processed.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

423Locked

A WebDAV resource is locked.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

424Failed Dependency

The operation depends on another operation that failed.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

425Too Early

The server will not risk processing a request that could be replayed.

A retry may be appropriate after diagnosing the cause. Do not blindly repeat a non-idempotent operation; it may already have taken effect.

426Upgrade Required

The client must use a different protocol; inspect Upgrade.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

428Precondition Required

The origin requires a conditional request, commonly to avoid lost updates.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

429Too Many Requests

A request rate limit has been reached.

Inspect Retry-After (delay seconds or an HTTP date), then use bounded backoff. Retrying still depends on the method, idempotency and service policy.

431Request Header Fields Too Large

One or more request header fields exceed accepted size.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

451Unavailable For Legal Reasons

Access is unavailable because of a legal demand.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

500Internal Server Error

An unexpected server condition prevented completion.

A retry may be appropriate after diagnosing the cause. Do not blindly repeat a non-idempotent operation; it may already have taken effect.

501Not Implemented

The server does not support the functionality required by the request.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

502Bad Gateway

A gateway received an invalid upstream response.

A retry may be appropriate after diagnosing the cause. Do not blindly repeat a non-idempotent operation; it may already have taken effect.

503Service Unavailable

Temporary overload or maintenance prevents service.

Inspect Retry-After (delay seconds or an HTTP date), then use bounded backoff. Retrying still depends on the method, idempotency and service policy.

504Gateway Timeout

A gateway did not receive an upstream response in time.

A retry may be appropriate after diagnosing the cause. Do not blindly repeat a non-idempotent operation; it may already have taken effect.

505HTTP Version Not Supported

The major HTTP version is unsupported.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

506Variant Also Negotiates

An experimental content-negotiation configuration has a circular reference.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

507Insufficient Storage

The server cannot store what is needed to complete the operation.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

508Loop Detected

A WebDAV operation encountered an infinite loop.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

510Not Extended (OBSOLETED)

Obsolete HTTP extension-framework response; do not use for new designs.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

511Network Authentication Required

Network access requires authentication, often through a captive portal.

Inspect the response body and request context before changing or retrying the request; the code alone is not a root-cause diagnosis.

Pasted lines are analyzed locally. Counts cover recognized lines only, not requests omitted from the sample. The tool does not contact URLs or automatically retry requests.

This tool runs entirely in your browser. Your data is never uploaded, never stored, and never leaves your device.

Search HTTP response codes and analyze pasted status lines or common access logs with per-code counts, ignored-line reporting and redirect or retry guidance.

How to use it

1Paste codes, HTTP status lines or supported common access-log entries.
2Analyze recognized lines and review any ignored lines before using the totals.
3Look up a code's meaning and copy JSON or download the recognized rows as CSV.

Example

Input: HTTP/2 200 429 429
Output: 3 recognized lines · 2 distinct codes: 200 × 1, 429 × 2

Counts describe only the supplied recognized lines.

What happens to your data

Search and log analysis run locally. The tool does not contact pasted URLs, upload logs, follow redirects or retry requests.

Last updated October 2026

Search HTTP response codes by number, current name, older name or meaning, then analyze a pasted set of status lines or common access-log entries. The analyzer counts each recognized code and response class, keeps source line numbers, and separates ignored lines so an incomplete sample cannot silently become a complete-looking total. Download the recognized rows as CSV or copy the analysis as JSON.

The reference explains how to act on a result: why a 304 is not a navigation redirect, which redirects preserve a request method, and why a retry may be unsafe even after a server error. The tool works locally on supplied text. It never sends a request to a pasted URL, follows a redirect or retries an operation.

How it works

The analyzer accepts one code or log entry per line. Supported forms include a bare code such as 429, a code followed by a reason phrase, HTTP/1.1 200 OK, HTTP/2 200, and a common access-log entry with a quoted request followed by a three-digit status and byte count. HTTP/3 textual status representations are also accepted. Arbitrary numbers elsewhere in a log are not treated as responses: a year, elapsed time or byte size should not become a false status count.

Inputs are limited to 1,000 lines and 100,000 characters. Nonempty lines that do not match a supported shape appear in the ignored-line report. If no recognized status is present, the tool gives an error rather than an empty success result. Counts and CSV output cover recognized rows only. They do not describe the traffic outside your sample, establish an uptime percentage, or distinguish a user-visible failure from an expected application response.

The first digit assigns the broad response class: informational, success, redirection, client error or server error. An unassigned code in the 100–599 range can still be counted, but its meaning is labeled Unassigned / nonstandard. For example, a vendor may use 499, but the tool does not present that service-specific convention as a standardized HTTP definition. Consult the service's documentation when an unassigned value appears.

Names follow the IANA registry checked on October 6, 2026. The current names include Content Too Large for 413 and Unprocessable Content for 422; older phrases remain searchable. The registry lists 418 as unused, while its historical teapot association remains explained. Code 510 is marked obsolete. Code 104 is a temporary upload-resumption registration whose current expiry is November 13, 2026; the linked registry is the authority if its status changes.

Redirect details matter when a request has side effects. A client may change POST to GET after 301 or 302. The method-preserving alternatives are 308 and 307. A 303 directs a retrieval of another resource, commonly after a submitted form. A 304 answers a conditional retrieval and allows a stored representation to be reused with updated metadata; it does not tell the browser to navigate to a Location. The tool's notes explain these differences beside the relevant codes.

A 429 or 503 can include Retry-After, expressed as delay seconds or an HTTP date. The code alone supplies neither a trustworthy delay nor permission to replay an operation. Check the response fields, request method, service rules and any idempotency support before retrying. A payment or order creation may already have taken effect despite an interrupted response. Bounded backoff is a strategy to consider after that context is understood, not an action this page performs.

Editing the analysis input removes the previous counts and downloads. Reference search and class filters operate independently, allowing you to look up a result without changing its recorded sample. CSV preserves the recognized source lines and neutralizes cells that could be interpreted as spreadsheet formulas. JSON retains the analysis structure, including ignored line numbers. Neither format authenticates the logs or establishes their completeness.

Worked example: five lines, four distinct status codes

Input: HTTP/2 200; HTTP/1.1 301 Moved Permanently; one common access-log 404; 429; 429 (each on a separate line)
Result: 5 recognized lines; 4 distinct codes; 200 × 1, 301 × 1, 404 × 1, 429 × 2; 2xx: 1, 3xx: 1, 4xx: 3

Load example supplies the complete supported access-log line. No ignored lines are present in that example.

Common use cases

Summarizing a small access-log sample without uploading it
Looking up a current status name or older alias
Comparing the method behavior of 301, 302, 303, 307 and 308
Separating standardized codes from service-specific responses

Frequently asked questions

What is the difference between 401 and 403?＋

401 indicates that acceptable authentication credentials are missing and should be interpreted with WWW-Authenticate. 403 means the server understood the request and refuses it; signing in again does not guarantee the required permission.

Will a 301 or 302 redirect keep my POST request?＋

A client is allowed to change POST to GET for these responses. If preserving the method is required, 307 and 308 provide that semantic rule. Also review the destination and whether forwarding sensitive request data is appropriate.

Why is 499 labeled nonstandard?＋

The IANA registry does not assign that exact code. Some products use it with a documented private meaning. This tool counts the value and shows its 4xx class without claiming that private meaning is universal.

Can I paste any server log format?＋

No. The analyzer supports bare codes, HTTP status lines and common access logs with a quoted request, status and byte count. Unsupported lines are listed as ignored. Convert a custom format to one status per line before relying on the totals.

Does a 500 mean it is safe to retry?＋

No. The operation may already have changed state before the error or interrupted response. Check method semantics, application guarantees and any idempotency mechanism before repeating it. The tool does not automatically retry anything.