Advertisement

HTTP Status Reference

Look up any HTTP status code: what it means, when servers send it, and how to handle it. Searchable, free, instant.

Find a status code

Search by code or keyword, or filter by class.

Click any row to copy the code.

Status codes

Advertisement

How the reference is organized

Codes are grouped by their first digit: 1xx informational, 2xx success, 3xx redirection, 4xx client errors, 5xx server errors. Search matches the numeric code, the official reason phrase, and the plain-English explanation, so typing redirect or server error narrows the list instantly.

Click to copy

Clicking any row copies just the numeric code to your clipboard, handy when writing error-handling code, API docs or support tickets that reference a specific status.

HTTP Status Reference FAQs

What is the difference between 301 and 302?
301 means the move is permanent: browsers and search engines should remember the new URL. 302 is temporary: keep using the old URL next time. Use 308/307 when the request method must not change.
Why do I get 403 instead of 401?
401 means you are not authenticated (log in and retry). 403 means you are authenticated but not permitted, so retrying with the same credentials will keep failing.
What should my API return for validation errors?
422 Unprocessable Content is the modern choice for well-formed requests with semantic errors. 400 works too but is vaguer about what went wrong.
Is 418 a real status code?
It started as an April Fools joke (RFC 2324) but is reserved and occasionally used playfully. You will not see it from serious APIs.
What does 429 mean and how do I handle it?
You hit a rate limit. Slow down, respect any Retry-After header, and use exponential backoff instead of hammering the endpoint.
Advertisement