HTTP Status Codes Reference

Search, filter, and copy any HTTP status code. A complete reference with descriptions for all standard codes.

How to use HTTP Status Codes

1. Browse all HTTP status codes organized by category — use the colored tabs to filter.
2. Type in the search box to find codes by number (e.g., '404'), phrase ('Not Found'), or keyword ('redirect').
3. Click any status code card to copy it to your clipboard — the card shows a brief scale animation and a toast confirmation.
4. Use Ctrl+K to focus the search box instantly for quick lookups.

What is HTTP Status Codes?

FAQ

Are all these codes standard?

All codes in the 1xx-5xx ranges defined by IANA are included. The tool also lists commonly-used non-standard codes (like 418 I'm a teapot, Cloudflare's 52x series, and nginx codes) with a 'Non-standard' tag for clarity.

What's the difference between 4xx and 5xx?

4xx codes mean the client sent a bad request (e.g., 404 Not Found, 403 Forbidden). The server is saying 'the problem is on your side.' 5xx codes mean the server failed to fulfill a valid request (e.g., 500 Internal Server Error, 503 Service Unavailable). The server is saying 'the problem is on my side.'

How do I use this in my API?

Use this reference when designing your API to choose semantically correct status codes. For example, 201 Created for successful resource creation, 409 Conflict for duplicate resources, or 429 Too Many Requests for rate limiting. Consistent status code usage makes your API easier to consume.

Related tools

• URL Redirect Checker
• URL Parser
• Response Time Test
• Email Validator
• JSON Formatter / Validator