Skip to content

HTTP Status Codes

Every HTTP status code, searchable, with what it actually means.

Quick Tool Overview

The complete HTTP status code list, searchable by number, name or intent, with a practical explanation of each rather than its specification wording — including which codes require a companion header to be implemented correctly.

What it does
Lists and explains every HTTP status code
You give it
A number, a name or a phrase
You get back
The matching codes with what they mean in practice
Best for
Choosing the right code, and decoding an unexpected one
Developer Tools Free, unlimited use No sign-up Runs in your browser

About the HTTP Status Codes

The complete list of HTTP status codes, searchable by number, by name or by what you are trying to describe. Each entry says what the code means in practice rather than quoting the specification back at you.

The distinctions that actually matter are spelled out: why 401 means unauthenticated despite being named Unauthorized, why 403 means authentication will not help, when to send 422 rather than 400, and why 307 exists when 302 already did. Codes that require a companion header — 405 needs Allow, 401 needs WWW-Authenticate, 429 should carry Retry-After — are marked, because omitting them is the most common way a correct status code is still implemented wrongly.

Key features of the HTTP Status Codes

Practical meanings

Why 401 means unauthenticated, why 403 means authenticating will not help, and when 422 beats 400 — the distinctions that decide which code to send.

Companion headers flagged

405 needs Allow, 401 needs WWW-Authenticate, 429 should carry Retry-After. Omitting those is the usual way a correct code is still implemented wrongly.

Search anything

Type a number, part of a name, or a phrase such as "rate limit" and the matching codes surface.

Filter by class

Narrow to informational, success, redirection, client error or server error when you are choosing rather than looking up.

The whole range

From 100 through 511, including the WebDAV codes and 418, which every framework implements anyway.

How to use the HTTP Status Codes

  1. 1

    Search or browse

    Type a number, a name, or a phrase such as "rate limit".

  2. 2

    Filter by class

    Narrow to informational, success, redirection, client error or server error.

  3. 3

    Read what it means

    Each code has a practical explanation, not just its official name.

  4. 4

    Copy what you need

    Click a code or its name to copy it.

Frequently asked questions

401 means the server does not know who you are — authenticate and try again. 403 means it knows exactly who you are and is refusing anyway, so authenticating will not help.

Reviews of the HTTP Status Codes

What people who use the HTTP Status Codes think of it. Reviews come from visitors and are posted as written.

No ratings yet

Yours would be the first.

  • 5 0 reviews rated 5 stars
  • 4 0 reviews rated 4 stars
  • 3 0 reviews rated 3 stars
  • 2 0 reviews rated 2 stars
  • 1 0 reviews rated 1 star

Write a review

Used this tool? Your rating helps the next person decide.

Your rating

Plain text only — links, email addresses and HTML are not accepted. Your name and review are shown publicly; nothing else is collected. See the privacy policy.

0 reviews

Newest first

No reviews yet

Be the first to rate the HTTP Status Codes. It takes half a minute and no account.

Write the first review

More developer tools