HTTP Status Code Reference

What this tool does

Every time a browser, app, or script talks to a server, the response comes back with a three-digit status code — 200, 404, 500, and so on. This tool is a quick way to look one up without digging through an RFC or scrolling a static Wikipedia table. Type a code or a keyword and you'll see the official name, what it actually means in practice, and which category it falls into (informational, success, redirection, client error, or server error).

How to use it

Start typing in the search box — a code number like "429", a name like "not found", or a concept like "rate limit" all work. Use the category buttons above the search to narrow things down to just redirects or just server errors when you're scanning logs. Click the clipboard icon on any card to copy "404 Not Found" straight to your clipboard for a bug report, a commit message, or API documentation.

Common use cases

• Debugging a failed API call and figuring out whether the problem is on your end (4xx) or the server's (5xx)
• Writing API documentation and needing the exact, correctly-worded status name
• Configuring a reverse proxy or CDN and deciding which redirect code (301 vs 302 vs 307) actually fits the situation
• Studying for a web development interview or course that covers HTTP fundamentals

Frequently asked questions

What's the difference between 401 and 403?

401 Unauthorized means you haven't proven who you are yet — you're missing or have invalid credentials. 403 Forbidden means the server knows exactly who you are and still won't let you in, because you don't have permission.

Should I use 301 or 302 for a redirect?

301 tells search engines and browsers the move is permanent — they'll update bookmarks and transfer SEO ranking to the new URL. 302 (or 307) says it's temporary, so the original URL should stay the one that's remembered and indexed.

What is 429 Too Many Requests used for?

It's the standard way an API tells a client "you're rate limited, slow down." Well-behaved clients back off and retry after a delay, often using a Retry-After header the server sends alongside it.

Is 418 I'm a Teapot a real status code?

It started as an April Fools' joke in RFC 2324 from 1998, but it's technically registered and some APIs and testing tools still return it playfully — it isn't something you'd use in a production system.

Why does 404 show up so often even for real pages?

Usually a broken link, a typo in the URL, a page that was deleted or moved without a redirect, or a client requesting a resource before it's been created server-side.