HTTP Status Codes Cheat Sheet
Complete reference guide to all HTTP status codes. Print this page or bookmark it for quick reference.
Informational Responses
Server received request headers, client should proceed with body.
Server is switching to a different protocol (e.g., WebSocket).
Server is processing the request (WebDAV).
Used for preloading resources while server prepares response.
Success Responses
Request succeeded. Standard response for successful HTTP requests.
Request succeeded and new resource was created (POST/PUT).
Request accepted for processing but not completed yet.
Response modified by a proxy/intermediate server.
Request succeeded but no content to return (DELETE operations).
Client should reset the document view (clear form data).
Server delivering part of resource (Range header requests).
Multiple status codes for multiple resources (WebDAV).
Redirection Messages
Multiple options available for the resource.
Resource permanently moved. Search engines update their index. SEO: Passes link juice.
Resource temporarily at different URI. SEO: Use 301 for permanent moves.
Response to POST - redirect to GET another resource.
Cached version is still valid. Saves bandwidth.
Like 302 but method/body must not change.
Like 301 but method/body must not change.
Client Error Responses
Malformed request syntax. Check request parameters.
Authentication required. Login or provide valid credentials.
Reserved for future use. Sometimes used by APIs for billing.
Access denied. You don't have permission to access this resource.
Resource doesn't exist. SEO: Fix broken links immediately!
HTTP method not supported (e.g., POST on GET-only endpoint).
Server can't produce content matching Accept headers.
Client took too long to send the request.
Request conflicts with current state (e.g., duplicate entry).
Resource permanently deleted. SEO: Better than 404 for removed pages.
Request body exceeds server limits.
URL is too long for server to process.
Server doesn't support the Content-Type sent.
Rate limiting. You're sending too many requests.
Blocked for legal reasons (DMCA, government censorship).
Server Error Responses
Generic server error. Check server logs for details.
Server doesn't support the functionality required.
Upstream server returned invalid response. Check proxy/origin server.
Server overloaded or under maintenance. Try again later.
Upstream server didn't respond in time.
Server doesn't support the HTTP version used.
Server cannot store the representation needed (WebDAV).
Infinite loop detected while processing request (WebDAV).
Cloudflare-Specific Errors
Origin server returned unexpected response to Cloudflare.
Origin server refused connection from Cloudflare.
Cloudflare couldn't establish TCP connection to origin.
DNS error or origin server is offline.
TCP connection established but origin didn't respond in time.
SSL/TLS handshake with origin server failed.
Origin SSL certificate is invalid or expired.
Cloudflare Railgun connection interrupted.
Check Your URLs for Errors
Found a status code you need to fix? Use our FREE bulk URL checker to scan up to 100 URLs at once.
Check URLs FREE - No Signup