HTTP Status Codes
Search common HTTP status codes
Search a status code or keyword first to find the right HTTP status and copy the status line immediately; scenario guidance is available in Advanced mode.
The full guide also includes pitfalls, worked examples, snippets, FAQs, and related tools for checking results or troubleshooting.
About this tool
Search a curated local reference of 25 HTTP status codes by number or description and filter by response class. Each entry provides a meaning, example and copyable HTTP/1.1 status line. The list is not the complete IANA registry and does not test a live URL.
Production Snippets
Choose a redirect for a POST endpoint
text
Temporary move, preserve POST + body: 307
Permanent move, preserve POST + body: 308
Check the actual Location header and destination response.Suggested Workflow
Frequently Asked Questions
Does 403 prove the user has logged in?
No. 401 signals missing or invalid authentication credentials and normally includes a WWW-Authenticate challenge. 403 means the server refuses the request; this can happen whether or not the client is authenticated.
How do 301, 302, 307 and 308 differ?
301 and 308 are permanent redirects; 302 and 307 are temporary. 307 and 308 preserve the method and body, while 301/302 can change POST to GET in clients. A temporary redirect does not inherently block search signals from being transferred.
When is 422 useful instead of 400?
400 covers bad requests, including malformed syntax. 422 Unprocessable Content is useful when syntax and content type are understood but the instructions cannot be processed. Follow the API contract rather than assuming all validation errors must use 422.
Can this page diagnose a 502 or 504?
It explains their meanings: 502 is an invalid upstream response, and 504 is an upstream timeout at a gateway. It does not issue requests or inspect logs, so the status alone cannot identify the failing dependency.
What can I copy?
Select a code to copy its HTTP/1.1 status line and consult the displayed explanation. The line is a reference string, not a complete response with headers and body; HTTP/2 and HTTP/3 use different framing.
Keep browsing