HTTP Status Code Lookup & Guide

ReferenceGuide

Searchable directory of HTTP status codes with RFC specifications, causes, and debugging tips.

100
ContinueThe server has received the request headers and the client should proceed to send the request body.
101
Switching ProtocolsThe requester has asked the server to switch protocols and the server has agreed to do so.
200
OKStandard response for successful HTTP requests. The actual response will depend on the request method used.
201
CreatedThe request has been fulfilled, resulting in the creation of a new resource.
202
AcceptedThe request has been accepted for processing, but the processing has not been completed.
204
No ContentThe server successfully processed the request and is not returning any content.
206
Partial ContentThe server is delivering only part of the resource due to a Range header sent by the client.
301
Moved PermanentlyThis and all future requests should be directed to the given URI in the Location header.
302
FoundTells the client to look at (browse to) another URL. A temporary redirect.
304
Not ModifiedIndicates that the resource has not been modified since the version specified by the request headers.
307
Temporary RedirectThe request should be repeated with another URI while strictly retaining the original HTTP method.
308
Permanent RedirectThe request and all future requests should be repeated using another URI, retaining the HTTP method.
400
Bad RequestThe server cannot or will not process the request due to an apparent client error.
401
UnauthorizedAuthentication is required and has failed or has not yet been provided.
403
ForbiddenThe request contained valid credentials, but the client lacks necessary permissions for the target.
404
Not FoundThe requested resource could not be found but may be available in the future.
405
Method Not AllowedA request method is not supported for the requested resource.
408
Request TimeoutThe server timed out waiting for the request from the client.
409
ConflictThe request could not be processed because of conflict in the current state of the resource.
422
Unprocessable ContentThe request was well-formed but was unable to be followed due to semantic errors.
429
Too Many RequestsThe user has sent too many requests in a given amount of time (rate limiting).
500
Internal Server ErrorA generic error message, given when an unexpected condition was encountered.
502
Bad GatewayThe server was acting as a gateway or proxy and received an invalid response from upstream.
503
Service UnavailableThe server cannot handle the request because it is overloaded or down for maintenance.
504
Gateway TimeoutThe server was acting as a gateway or proxy and did not receive a timely response from upstream.
202

Accepted

The request has been accepted for processing, but the processing has not been completed.

Common Causes

Asynchronous job queues, background batch workers, or webhook dispatchers received the task.

Debugging & Developer Best Practices

Return a job ID or status polling URL so the client can monitor processing progress.

Sample Implementation Snippet

// Next.js Route Handler / Express
import { NextResponse } from 'next/server';

export async function GET() {
  return NextResponse.json(
    { status: 202, message: "Accepted" },
    { status: 202 }
  );
}

About HTTP Status Code Lookup & Guide

HTTP status codes are standard 3-digit numeric codes issued by a server in response to a client's request. Grouped into five distinct categories (1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error, 5xx Server Error), they communicate whether an HTTP request was successfully completed or why it failed.

Zero-Upload Privacy Guarantee

Quick local reference loads instantaneously without page jumps or advertisements, letting developers debug API responses seamlessly.

Client-Side Sandbox● 100% Air-Gapped

Key Capabilities & Features

Complete index of standard RFC status codes (100 through 511)
Instant search filter by code number, name, or description
Detailed breakdown of common causes and debugging solutions
Visual color coding by status class (Green for 2xx, Blue for 3xx, Amber for 4xx, Red for 5xx)
Code snippets showing how to return each status in modern web frameworks

How to use this HTTP status codes

1

Search or Filter

Filter by status class (2xx, 3xx, 4xx, 5xx) or type a code or keyword (e.g. 'rate limit', '403', 'cors').

2

Select Status Code

Click any status code to view its comprehensive specification card.

3

Review Debugging Tips

Read common causes on the client/server side, and actionable steps to resolve the issue.

4

Copy Code Snippet

Copy sample response headers or Express/Next.js response handlers.

Frequently Asked Questions

401 means unauthenticated (the user is not logged in or credentials are missing/invalid). 403 means authenticated, but unauthorized (the server knows who you are, but you lack permission to access the resource).