📡

HTTP Status Codes

Complete reference for all HTTP status codes with descriptions.

Input
HTTP Status Codes

📖 What is HTTP Status Codes?

HTTP Status Code Reference explains every HTTP response code — from 100 Continue to 599. Each code includes its official meaning, when servers return it, and how to handle it as a developer. Use it as a quick lookup when debugging API responses, configuring error pages, or learning HTTP. Everything runs in your browser.

💡 Example

Input
404
Output
404 Not Found — The server cannot find the requested resource. The URL may be wrong, the resource may have been deleted, or the route is not configured.

🛠️ Common Use Cases

  • Looking up unfamiliar HTTP status codes during API debugging
  • Understanding the difference between similar codes (401 vs 403, 302 vs 307)
  • Configuring custom error pages for common status codes
  • Learning HTTP protocol fundamentals
  • Documenting API response codes

📝 Status Code Categories

  • 1xx Informational — request received, processing continues
  • 2xx Success — request successfully received and processed
  • 3xx Redirection — further action needed to complete the request
  • 4xx Client Error — the request contains an error
  • 5xx Server Error — the server failed to fulfill a valid request

⚠️ Commonly Confused Codes

  • 401 vs 403 — 401 means "not authenticated" (log in first). 403 means "not authorized" (logged in but not allowed).
  • 302 vs 307 — both are temporary redirects. 302 may change the method to GET; 307 preserves the original method.
  • 404 vs 410 — 404 means "not found" (might return later). 410 means "gone permanently" (better for SEO cleanup).

❓ Frequently Asked Questions

What is the most common HTTP status code?
200 OK is the most common — it means the request succeeded. 404 Not Found is the most common error code.
What is the difference between 401 and 403?
401 Unauthorized means authentication is required — the user is not logged in. 403 Forbidden means the user is authenticated but does not have permission.
When should I use 204 No Content?
Use 204 for successful requests that return no body — typically DELETE operations or updates where no response data is needed.
Is my data private?
Yes — all processing runs entirely in your browser. Your data is never sent to any server.
Is this tool free?
Completely free — no login, no usage limits, works offline once loaded.
Yes — completely free, no login required, no usage limits.
Is my data private?
Yes — all processing runs in your browser. Your data is never sent to any server.
Does it work offline?
Yes — once the page is loaded, the tool works without an internet connection.
🔒
Your data stays private. All processing happens entirely in your browser using JavaScript. Nothing is ever sent to our servers. You can even use this tool offline after the page loads.