âšď¸ Skipped - page is already crawled
| Filter | Status | Condition | Details |
|---|---|---|---|
| HTTP status | PASS | download_http_code = 200 | HTTP 200 |
| Age cutoff | PASS | download_stamp > now() - 6 MONTH | 0 months ago |
| History drop | PASS | isNull(history_drop_reason) | No drop reason |
| Spam/ban | PASS | fh_dont_index != 1 AND ml_spam_score = 0 | ml_spam_score=0 |
| Canonical | PASS | meta_canonical IS NULL OR = '' OR = src_unparsed | Not set |
| Property | Value |
|---|---|
| URL | https://www.infidigit.com/blog/http-status-codes/ |
| Last Crawled | 2026-04-13 22:36:56 (22 hours ago) |
| First Indexed | 2020-01-10 21:37:12 (6 years ago) |
| HTTP Status Code | 200 |
| Meta Title | What Are HTTP Status Codes? Complete List of HTTP Response Codes |
| Meta Description | Learn what HTTP status codes are and how they affect website performance. Explore the full list of HTTP response codes (1xx to 5xx) with clear explanations for each. |
| Meta Canonical | null |
| Boilerpipe Text | 3.4
(
14
)
Every time you browse the internet, thereâs a silent exchange of messages between your browser and the server hosting the website. These messages, known as HTTP status codes, are crucial in ensuring smooth communication. Whether youâre accessing a webpage, encountering an error, or being redirected, these codes tell you exactly whatâs going on behind the scenes.
HTTP status codes help determine whether the page is accessible, what went wrong, and what action you need to take. Understanding these codes is essential for anyone managing websites, troubleshooting online issues, or looking to improve their websiteâs performance. In this article, we will explain HTTP status codes in detail and provide a comprehensive list to help you understand their meanings and implications better.
What are HTTP status codes?
In simple terms,
HTTP status codes
are messages that a server sends to a browser to indicate the result of a request. When you type a website address into your browser, it sends a request to the server. In return, the server sends back a three-digit HTTP status code, indicating whether the request was successful or if there was an issue.
These codes act as a form of communication between browsers and servers. Think of them as âsignalsâ that tell browsers how to handle the requested page.
Understanding HTTP status codes is not just for technical people. If you manage a website, knowing these codes is crucial for identifying errors, reducing website downtime, and ensuring a smooth user experienceâall of which contribute to improving
search engine rankings
.
John Mueller explained that HTTP status codes are the first thing Google checks when crawling the content.
He was posed with the question:
âWondering if Google checks status codes before anything else, like before rendering content?â
In response, Mueller confirmed that Google does check the status codes before rendering or indexing content. Google checks for a â200â status code before proceeding with crawling any further. A 200 status code indicates to Google that it is crawling a valid page and there might be content worth indexing on it. Here is the video on different errors that Google may find & report while crawling your website
Why do HTTP Status Codes Matter for SEO?
You may not always see HTTP status codes when browsing a webpage, but they are incredibly important behind the scenes. If a webpage is unavailable, for example, the browser will receive an HTTP status code showing the issue, such as a server error or a missing page.
These codes impact
Search Engine Optimization (SEO)
significantly. Search engines like Google rely on HTTP status codes to detect errors, crawlability issues, and even reduce website downtime. When Google crawls a website, it first checks the HTTP status code before anything else.
For instance, a
200 OK
status code signals to Google that the page is valid, functional, and ready to be indexed. Pages that return this code are considered
crawlable
and
indexable
, which is essential for
ranking
in search engines. If a page returns a
404
or
500
status code, it can negatively affect your SEO.
John Mueller, a Google Search Advocate, explained that Google checks these codes before proceeding to crawl and index the content. If Google encounters a
200 status code
, it indicates that the page is healthy, and the content may be worth indexing. You can watch his video on the
errors that Google might find and report
while crawling your website.
List of HTTP Status Codes
HTTP status codes are divided into five groups based on their first digit. Each group signifies a different type of response from the server.
1xx HTTP status codes group (Informational): These codes tell you that the server has received and is processing your request.
2xx HTTP status codes group (Success): These codes mean your request was successful.
3xx HTTP status codes group (Redirection): These codes tell you that further action is needed to complete the request (usually a redirect to a new URL).
4xx HTTP status codes group (Client Error): These codes indicate that there was an issue with the request you sent.
5xx HTTP status codes group â (Server Error): These codes mean thereâs a problem on the server side.
Hereâs an interesting and detailed image that will help you understand the different types of HTTP response codes you might encounter when accessing a webpage.
List of HTTP Status Codes and What They Mean
HTTP status codes are categorized into five main groups, each representing a different type of response from the server. Below is a breakdown of each group and what the various status codes within them signify.
1xx HTTP response status codes group
100 Status Code: Continue
The 100 Continue status code means that the server has received the initial part of the request and is ready to continue processing. Itâs often used when the client is sending large amounts of data, allowing the server to confirm that itâs prepared to handle the entire request before the data is fully transmitted.
Example:
This might occur when submitting large files in a POST request.
101 Status Code: Switching Protocol
The 101 Switching Protocols status code indicates that the client requested a protocol change (e.g., upgrading from HTTP to HTTPS or switching to WebSocket) and the server agrees. This ensures that communication between the client and server can occur using a more secure or appropriate protocol.
Example:
Upgrading from HTTP to HTTPS for security purposes.
102 Status Code: Processing
This code signals that the server has received the request, but itâs still being processed. This is common for long-running tasks that take time to complete. It tells the client to wait while the server processes the request.
Example:
Used when executing large database queries or processing complex operations.
103 Status Code: Early Hints
The 103 Early Hints status code tells the client about preloaded resources (such as images, scripts, or CSS files) before the full response is ready. This allows the browser to start loading resources early, improving page load times.
Example:
Preloading resources for faster rendering while waiting for the final response.
2xx HTTP response status codes group
These codes indicate that the request was successfully received, understood, and processed by the server.
201 Status Code: Created
A 201 status code indicates that a new resource has been successfully created as a result of the clientâs request. Itâs commonly used for POST requests, such as creating a new user or submitting a form.
Example:
After submitting a form to create a new blog post, you may see this status code.
202 Status Code: Accepted
The 202 Accepted status code means the server has received and accepted the request, but the process is not yet complete. Itâs useful for asynchronous tasks that take time to finish.
Example:
A background task for processing an order might return this code, indicating that the order is in progress but not yet finalized.
203 Status Code: Non-Authoritative Information
The 203 status code is returned when the server successfully processes the request, but the response is based on third-party information, not the origin server.
Example:
When fetching data from a cache instead of the original server.
204 Status Code: No Content
A 204 No Content status code tells the client that the server has successfully processed the request, but there is no content to send in the response body. This often happens after a successful action, such as form submission.
Example:
After submitting a contact form where no additional data needs to be returned.
205 Status Code: Reset Content
The 205 Reset Content status code instructs the client to reset the documentâs state. Itâs typically used in forms to clear the form fields after submission.
Example:
After submitting a form with errors, the server might send a 205 response to reset the form fields.
206 Status Code: Partial Content
The 206 Partial Content status code indicates that the server is returning part of the requested resource. This is often used for large files that are downloaded in chunks.
Example:
Downloading a large video file in multiple parts.
207 Status Code: Multi-Status
This code indicates that the server has returned information from multiple resources in a single response, typically used in batch processing operations.
Example:
A single request that modifies multiple resources, such as adding new records to a database.
208 Status Code: Already Reported
This code is used to avoid redundant reporting when the same resource has been listed previously. It helps improve efficiency, especially in collaboration environments.
Example:
In a collaborative environment, when multiple users edit the same file, this status code prevents redundant enumeration.
226 Status Code: IM Used
The 226 IM Used status code indicates that the server has fulfilled the request and applied some modifications to the resource during the process, such as applying an Instance Manipulation (IM) operation.
Example:
Applying image optimization during an HTTP GET request.
3xx HTTP response status codes group
The 3xx range of HTTP status codes is used for redirection. These codes indicate that the client must take additional actions to complete the request.
300 Status Code: Multiple Choice
The 300 Multiple Choices status code indicates that the server has multiple options for the requested resource, but it does not specify which one to choose. The client may have several ways to access the same resource, such as different formats or languages. The server leaves the decision to the client or user.
Example:
Imagine visiting a website that supports both English and Spanish versions. When you request the resource, the server responds with a 300 Multiple Choices status code, listing the available language versions. The user can then select which version to view.
301 Status Code: Permanent Redirection
The 301 Moved Permanently status code indicates that the requested resource has been permanently moved to a new URL. Both browsers and search engines will now use the new location for future requests. This code is important for maintaining SEO integrity, as search engines update their indexes to reflect the new URL, ensuring that search rankings are preserved.
Example:
If a website undergoes a major restructuring and a pageâs URL changes permanently, the server responds with a 301 status code, ensuring that any links or search engine results pointing to the old URL will redirect to the new one.
SEO Tip:
When using a 301 redirect, itâs important to implement it properly to avoid 404 errors and ensure your SEO rankings are preserved.
Here is what Googleâs John Mueller has to say on how long it will take to rank a new URL after doing a 301 redirect to the old URL:
302 Status Code: Temporary Redirection
The 302 Found status code (formerly called âMoved Temporarilyâ) tells the client that the requested resource has temporarily moved to a different URL. Unlike the 301 status code, this change is not permanent, and future requests should use the original URL.
Example:
A webpage might be temporarily moved during maintenance or for special events. For instance, if an e-commerce site has a special sale on a subdomain, a 302 redirect can be used to direct users to a temporary location.
303 Status Code: See Other
The 303 See Other status code tells the client to retrieve the requested resource from a different URL using a GET request. This is commonly used after a POST request to indicate that the response is available at another location and that a GET request should be used to fetch it.
Example:
After submitting an online form (POST), the server might return a 303 status code to inform the client that the result of the submission is available at another URL via a GET request.
304 Status Code: Not Modified
The 304 Not Modified status code indicates that the requested resource has not changed since the last time it was requested. The client can continue using the cached version of the resource, saving bandwidth and reducing load times.
Example:
A user revisits a website and their browser sends a request for a resource. The server checks the last modification date of the resource and, if it hasnât changed, returns a 304 status code to inform the browser to use the cached version.
305 Status Code: Use Proxy (Deprecated in HTTP/1.1)
The 305 Use Proxy status code was used to indicate that the client must access the requested resource through a specified proxy. However, this status code was deprecated in HTTP/1.1 and is no longer used in modern web development. Other codes, such as 407 (Proxy Authentication Required), are used in its place.
307 Status Code: Temporary Redirect
The 307 Temporary Redirect status code indicates that the resource has temporarily moved to a new URL. Unlike a 302 redirect, the 307 code specifies that the HTTP method used for the request (e.g., POST or GET) should remain unchanged when following the redirect.
Example:
If an API endpoint temporarily moves but the server doesnât want to change the request method, it will return a 307 status code to ensure that the client uses the same HTTP method to fetch the resource from the new location.
308 Status Code: Permanent Redirect
The 308 Permanent Redirect status code is similar to the 301 code, but it ensures that the HTTP method used in the original request is preserved when redirected to the new URL.
Example:
A REST API endpoint that permanently moves to a new URL and wants to ensure that POST requests are also forwarded as POST requests would return a 308 status code.
4xx HTTP response status codes group
The 4xx range is reserved for client-side errors. These errors usually occur when there is an issue with the request sent to the server.
400 Status Code: Bad Request
The 400 Bad Request status code indicates that the server could not understand the request due to malformed syntax. This typically happens due to issues like missing parameters, incorrect formatting, or invalid query syntax.
Example:
If a user sends a request with an invalid URL (like a malformed query string), the server will respond with a 400 error, prompting the user to correct the issue.
401 Status Code: Unauthorized Error
The 401 Unauthorized status code is returned when the client must authenticate before accessing the requested resource. This error occurs when the request is missing valid authentication credentials, or the credentials provided are not sufficient.
Example:
When attempting to access a secure page on a website that requires login credentials, the server will return a 401 status code if the user hasnât logged in or provided invalid credentials.
402 Status Code: Payment Required
The 402 Payment Required status code was originally intended to indicate that the client needs to pay for access to the resource. However, it is not widely used and is reserved for future use.
403 Status Code: Forbidden Error
The 403 Forbidden status code indicates that the server understands the request, but refuses to authorize it. This could be because the user doesnât have the necessary permissions or access rights to the resource.
Example:
If a user tries to access a protected page (like an admin dashboard) without the correct permissions, the server will return a 403 status code.
404 Status Code: Page Not Found
The 404 Not Found status code occurs when the requested resource cannot be found on the server. This is one of the most common errors encountered on the web, usually indicating that the URL was typed incorrectly, or the page was removed.
Example:
If a user tries to access a non-existent page, such as example.com/about-us, theyâll see a 404 error because the page does not exist.
SEO Tip: Properly handling 404 errors can help improve user experience and SEO. Itâs advisable to create a custom 404 page and manage broken links to maintain the siteâs SEO ranking.
405 Status Code: Method Not Allowed
The 405 Method Not Allowed status code occurs when the client sends a request using an HTTP method that the resource does not support. For example, trying to submit a form with a GET request instead of POST will trigger this error.
Example:
If a form is designed to be submitted via POST but a user tries to access it via a GET request, the server will respond with a 405 error.
406 Status Code: Not Acceptable
The 406 Not Acceptable status code is returned when the server is unable to provide a version of the resource that meets the clientâs preferences, such as language or media type. This happens when the server canât match the content with what the client accepts.
Example:
If a client requests a page in French but the server only has the page available in English, it might return a 406 error.
407 Status Code: Proxy Authentication Required
The 407 Proxy Authentication Required status code is similar to the 401 Unauthorized error, but it indicates that the client must authenticate with a proxy server before the request can proceed.
Example:
A client behind a corporate firewall or proxy server might see this error if the server requires authentication to pass the request through the proxy.
408 Status Code: Request Timeout
The â408 Request Timeoutâ status code is returned when the clientâs request took too long to complete, and the server decides to close the connection. This typically happens when the client does not send a request or complete a request within a certain time frame. Servers use this to prevent idle connections from consuming server resources. In many cases, a timeout might occur if the client is uploading a large file and it takes longer than expected to complete the operation.
Example:
If youâre trying to upload a 10MB file over a slow connection and it takes too long, the server may close the connection and return a 408 error, asking you to resend the request.
409 Status Code: Conflict
The â409 Conflictâ error occurs when a request cannot be completed because it conflicts with the current state of the server or resource. This can happen when the client is attempting an operation that cannot be performed due to conflicting information. The conflict may be due to data changes made by another client or system.
Example:
If two users try to update the same database record at the same time, the second update attempt might trigger a 409 error, indicating a conflict with the data.
410 Status Code: Gone
The â410 Goneâ status code indicates that the requested resource has been permanently removed from the server and is no longer available, with no forwarding address. Unlike a â404 Not Foundâ error, which could mean that the resource is temporarily unavailable, a 410 error means the resource has been intentionally and permanently deleted. This helps inform users and search engines that the resource will not return.
Example:
If an online store deletes a product page permanently and does not redirect it elsewhere, users trying to access that page will receive a 410 error.
411 Status Code: Length Required
A â411 Length Requiredâ error is returned when the server expects the client to include a Content-Length header in the request but it is missing. This header specifies the size of the request body in bytes. If the client fails to provide this information, the server cannot process the request properly and rejects it with a 411 error.
Example:
When submitting a POST request with data (e.g., form data or JSON), the client needs to specify how much data is being sent by including the Content-Length header. If omitted, the server responds with a 411 status.
412 Status Code: Precondition Failed
The â412 Precondition Failedâ status code indicates that one or more conditions provided by the client in the request headers could not be satisfied by the server. These conditions are often specified using the If-Match, If-None-Match, If-Modified-Since, or If-Unmodified-Since headers. If the condition is not met, the server will return this error.
Example:
If a client sends a request to update a resource with an If-Match header that contains an outdated version of the resource, the server will return a 412 error, indicating the precondition has failed.
413 Status Code: Payload Too Large
The â413 Payload Too Largeâ status code occurs when the request is too large for the server to process. This is typically seen when the client is sending a request with a body that exceeds the maximum allowed size configured on the server. Servers often limit the size of the data they can handle to prevent abuse or resource exhaustion.
Example:
Uploading a file that exceeds the serverâs size limit (e.g., attempting to upload a 100MB file to a server that allows a maximum of 10MB) would result in a 413 error.
414 Status Code: URL Too Long
The â414 URI Too Longâ status code is returned when the URL of the request exceeds the maximum length the server can process. URLs are subject to length limitations, and if the client sends a request with an excessively long URL, the server will reject it. This error often arises when the URL contains a large number of query parameters or data.
Example:
A search URL with many parameters or a URL that encodes large amounts of data could exceed the serverâs length restrictions, triggering a 414 error.
415 Status Code: Unsupported Media Type
The â415 Unsupported Media Typeâ error indicates that the server cannot process the request because the media type (e.g., content type) is not supported. The clientâs request is typically accompanied by a Content-Type header, which specifies the format of the data being sent (e.g., application/json, text/html). If the server doesnât support the specified format, it will return a 415 status code.
Example:
If you try to upload an image in a format like .webp to a server that only accepts .jpg or .png, the server would return a 415 error due to unsupported media.
416 Status Code: Range Not Satisfiable
The â416 Range Not Satisfiableâ status code occurs when the Range header sent in the request specifies a range of bytes that is outside the bounds of the file or resource. If the client requests a range that exceeds the file size or is invalid, the server returns this error to indicate it cannot fulfill the request.
Example:
If a client requests the first 1000 bytes of a file, but the file is only 500 bytes long, the server will return a 416 error because the requested range cannot be satisfied.
417 Status Code: Expectation Failed
The â417 Expectation Failedâ status code is returned when the server cannot meet the expectations specified by the client in the Expect header. The Expect header allows the client to set certain expectations (e.g., Expect: 100-continue), and if the server is unable to fulfill these expectations, it will return a 417 error.
Example:
If the client sends a Expect: 100-continue header but the server cannot process the request due to internal issues, it will respond with a 417 error.
418 Status Code: Iâm a teapot
The â418 Iâm a Teapotâ status code is part of an April Foolsâ joke in the âHyper Text Coffee Pot Control Protocolâ (HTCPCP). It humorously indicates that a teapot cannot brew coffee. While not meant for real-world usage, this status code has become a well-known part of internet culture.
Example:
Sending a request to a server that supports HTCPCP to brew coffee with a teapot would return a 418 status code.
421 Status Code: Misdirected Request
The â421 Misdirected Requestâ status code is returned when a request is sent to the wrong server, and the server cannot process it because it is not configured to handle the request. This typically occurs in environments with multiple servers that serve different purposes.
Example:
If a client sends a request to the wrong server in a load-balanced environment, the server will return a 421 error.
422 Status Code: Unprocessable Entity
The â422 Unprocessable Entityâ status code is returned when the server understands the content of the request but cannot process it due to semantic errors. This often occurs when data in the request is valid in structure but fails validation rules (e.g., missing required fields or incorrect data format).
Example:
Submitting a form with incomplete or invalid data (e.g., a date in the wrong format) could result in a 422 error.
423 Status Code: Locked
The â423 Lockedâ status code indicates that the requested resource is locked and cannot be accessed or modified at the moment. This often occurs when a resource is being edited or is in use by another process.
Example:
If a user is editing a document and another user tries to access it, the server may return a 423 error indicating that the document is locked.
424 Status Code: Failed Dependency
The â424 Failed Dependencyâ status code is used when a request fails due to the failure of a preceding request that it depends on. This is often seen in WebDAV or similar protocols where the successful execution of one request depends on the success of another.
Example:
If a DELETE request fails, a subsequent request that depends on the deleted resource will return a 424 error.
425 Status Code: Too Early
The â425 Too Earlyâ status code is used to indicate that the server is not ready to process a request because it was received too early. This can help prevent issues like replay attacks or race conditions that could arise if the request is processed prematurely.
Example:
A client trying to process a request too soon after a previous request, potentially causing unintended consequences, would result in a 425 error.
426 Status Code: Upgrade Required
The â426 Upgrade Requiredâ status code indicates that the client must upgrade to a different protocol to access the requested resource. This could be to a newer version of HTTP or another protocol entirely (e.g., switching from HTTP/1.1 to HTTP/2).
Example:
If a server requires HTTP/2 for certain operations, but the client is using HTTP/1.1, the server will return a 426 error.
428 Status Code: Precondition Required
The â428 Precondition Requiredâ status code indicates that the server requires certain conditions to be met before processing the request. This is typically used in scenarios where operations should only be performed if specific preconditions are met (e.g., ensuring a resource hasnât changed).
Example:
Before updating a document, the client may need to ensure that the document has not been modified since the last request by including an If-Match header. If this condition is not met, a 428 error is returned.
429 Status Code: Too Many Requests
The â429 Too Many Requestsâ status code is returned when the client has sent too many requests in a given time period and is being rate-limited. This is often used to prevent abuse or excessive load on the server.
Example:
If you hit an API rate limit by sending too many requests in a short time, the server will return a 429 error, and you may also receive a Retry-After header with a time when you can retry the request.
431 Status Code: Request Header Fields Too Large
The â431 Request Header Fields Too Largeâ status code is returned when the requestâs header fields (e.g., cookies or HTTP headers) exceed the serverâs size limits.
Example:
If a client sends a request with very large cookies or headers, causing the server to exceed its size limit for headers, a 431 error will be returned.
451 Status Code: Unavailable For Legal Reasons
The â451 Unavailable For Legal Reasonsâ status code indicates that the requested resource cannot be accessed due to legal restrictions. This may occur if the content is blocked in certain jurisdictions due to censorship, legal disputes, or government regulations.
Example:
A streaming service might block access to a movie in certain countries due to legal issues, returning a 451 error when users attempt to access it from those locations.
5xx HTTP response status codes group
500 Status Code: Internal Server Error
The â500 Internal Server Errorâ indicates that the server encountered an unexpected condition or issue that prevented it from fulfilling the request. This error does not specify the exact problem but points to an internal issue within the server, such as a misconfiguration or a server-side failure. It typically means the problem lies with the server itself, requiring further investigation by the server administrator or technical team.
Example:
If a website experiences a sudden software crash or a malfunctioning server-side script, users trying to access the site may see a 500 error. The root cause might be a misconfigured script, insufficient server resources, or an issue with the serverâs infrastructure.
501 Status Code: Not Implemented
The â501 Not Implementedâ error occurs when the server does not recognize the request method used by the client and is unable to support it. This can happen when a client sends a request using a method (such as PUT, DELETE, or PATCH) that the server is not configured to handle. Essentially, the server cannot process the request using the specified method.
Example:
A client sends a DELETE request to a server, but the server does not support or allow the DELETE method for the requested resource. As a result, the server responds with a 501 error.
502 Status Code: Bad Gateway
The â502 Bad Gatewayâ error occurs when a server, acting as a gateway or proxy, receives an invalid response from an upstream server while trying to fulfill a request. This error indicates a communication failure between servers, where the gateway server could not get a valid response from the upstream server it was trying to access.
Example:
If youâre using a reverse proxy (e.g., Nginx or Apache) that forwards requests to a backend web server, and the backend server returns an invalid or no response, the proxy server will return a 502 error. This is common in server-side failures, like a backend database going down.
503 Status Code: Service unavailable
The â503 Service Unavailableâ status code is returned when the server is temporarily unable to process the request. This typically happens when the server is overloaded or undergoing maintenance. Itâs a temporary condition, and the server should return to normal operation once the issue is resolved.
Example:
If a popular website experiences high traffic, it may overload the server, leading to a 503 error. Similarly, during scheduled maintenance or updates, users trying to access the site may encounter this error.
504 Status Code: Gateway Timeout
The â504 Gateway Timeoutâ error occurs when a server acting as a gateway or proxy does not receive a timely response from another server it is trying to access in order to load a web page or fulfill a request. This often happens when the upstream server takes too long to respond, causing the gateway server to timeout.
Example:
If a user tries to access a website that requires data from a third-party service, and that third-party service is slow to respond or unavailable, the gateway server will return a 504 error, indicating that the timeout was caused by the upstream service.
505 Status Code: HTTP Version Not Supported
The â505 HTTP Version Not Supportedâ error occurs when the server does not support the version of the HTTP protocol used in the clientâs request. This error typically arises when the client uses an outdated or unsupported HTTP version that the server cannot process.
Example:
If a client sends a request using HTTP/1.0 but the server only supports HTTP/1.1 or HTTP/2, the server will return a 505 error because it cannot handle the older version.
506 Status Code: Variant Also Negotiates
The â506 Variant Also Negotiatesâ status code indicates that the server has an internal configuration error. It typically happens when a server attempts to select a variant of the requested resource but encounters a problem in the content negotiation process. The error occurs when the server cannot determine the appropriate variant resource.
Example:
A server misconfiguration, such as when multiple resources are set to negotiate content but one of them is also configured to perform content negotiation itself, leading to a conflict that results in a 506 error.
507 Status Code: Insufficient Storage
The â507 Insufficient Storageâ error indicates that the server does not have enough storage space to complete the request. This typically happens when the server runs out of storage or resources needed to fulfill the operation, such as when the server cannot write to the file system or database.
Example:
If a server running a file-sharing application runs out of disk space while uploading a new file, it may return a 507 error indicating insufficient storage.
508 Status Code: Loop Detected
The â508 Loop Detectedâ status code occurs when the server detects an infinite loop while processing a request. This usually happens when a request is repeatedly forwarded between multiple resources without ever reaching its destination, causing the server to detect a processing loop.
Example:
If a URL is incorrectly configured to redirect to itself or another URL that redirects back to the original, an infinite loop will occur, and the server will return a 508 error.
510 Status Code: Not Extended
The â510 Not Extendedâ error indicates that the server requires additional extensions or features to fulfill the request. The current request lacks the necessary extensions or features, meaning the server cannot process it successfully without further modifications or additions.
Example:
If the server requires specific headers or protocols to process a request but the client does not provide them, the server may return a 510 error.
511 Status Code: Network Authentication Required
The â511 Network Authentication Requiredâ error occurs when the client must authenticate with the network before the server will allow access. This is often seen with captive portals, such as those in public Wi-Fi networks, where the user must authenticate or log in before they can access the internet.
Example:
A user connects to a public Wi-Fi network and tries to visit a website, but they receive a 511 error indicating they need to complete a login or authentication process before they can proceed.
Tools for Checking HTTP Status Codes
There are several tools available to help you check the HTTP status codes of your websiteâs pages, which is crucial for monitoring site health and optimizing SEO. These tools provide insights into server responses, identifying issues like broken links, redirects, or inaccessible pages. Here are some popular
tools for checking HTTP status codes
:
1. Google Search Console
:
Purpose
: Google Search Console offers a comprehensive view of how Googlebot is interacting with your site. It provides detailed reports on crawl errors, server issues, and HTTP status codes. Using this tool, you can easily identify 404 errors, server unresponsiveness, or any issues preventing Google from indexing your pages.
How it helps
: Google Search Console will alert you to pages that have issues, such as â404 Not Foundâ errors or â500 Internal Server Errors.â You can use this information to resolve problems that may hinder your siteâs search engine rankings.
2. Screaming Frog SEO Spider
:Â
Purpose
: Screaming Frog is a powerful desktop tool that crawls your website, similar to how a search engine bot would. It provides a comprehensive analysis of all the HTTP status codes on your website, including 404 errors, redirects, and other issues.
How it helps
: It not only checks for broken links but also helps you analyze the serverâs response for each URL, allowing you to find and fix server-side issues. You can also export the results into various formats for detailed reporting.
3. GTMetrix
:Â
Purpose
: GTMetrix is a performance analysis tool that provides insights into your websiteâs loading times, including detailed HTTP status codes and server performance. It offers a comprehensive report on various elements of page speed and response times.
How it helps
: It gives you an understanding of how your server responds to requests. This is helpful for detecting HTTP errors such as slow server responses, redirects, or server misconfigurations that affect performance. It also provides suggestions for improving your websiteâs speed and server response time.
4. Pingdom
:Â
Purpose
: Pingdom is a popular website monitoring tool that helps you check your siteâs uptime, performance, and server response. It offers HTTP status code checks along with a detailed performance report from multiple locations worldwide.
How it helps
: Pingdom allows you to monitor the HTTP status codes returned by your website from different parts of the world, ensuring that users from various locations are experiencing optimal load times and server responses. It can also send you alerts if certain pages return errors or slow down.
5. Curl
:
Purpose
: Curl is a command-line tool that allows you to manually check the HTTP status codes for any website. By entering a URL, you can directly interact with the server and analyze the response.
How it helps
: Curl is useful for developers or users with technical knowledge who need to check the response from a server for debugging or troubleshooting. By adding flags (e.g.,
-I
to get header information), you can get detailed server responses, including HTTP status codes, headers, and more.
6. Ahrefs
:Â
Purpose: Ahrefs is a comprehensive SEO toolset that provides detailed audits of your website, including a breakdown of HTTP status codes for each page. It helps you monitor broken links, redirect chains, and other server-side issues that could impact SEO.
How it helps: Ahrefs crawls your entire website, identifies HTTP errors such as 404s or 500s, and generates reports. It can also identify other SEO-related issues, such as slow-loading pages or poor server responses, which can negatively impact your siteâs ranking.
These tools are essential for diagnosing server issues, ensuring a smooth user experience, and maintaining good SEO practices.
Now that you are familiar with the most common HTTP errors, you should have a good basis for troubleshooting issues with your web servers or applications. If you come across any error codes that were not mentioned above, feel free to discuss them in the comments section.
FAQs about HTTP Status Codes
What are HTTP Status Codes?
HTTP status codes are three-digit numbers used in the HTTP protocol to indicate the outcome of a clientâs request to a web server. They help communicate whether the request was successful, encountered an error, or requires further action. Understanding these HTTP protocol status codes is essential for diagnosing website issues and ensuring smooth user experiences.
Why are HTTP Status Codes Important?
HTTP status codes play a crucial role in helping search engines and browsers understand the state of a webpage. These HTTP response codes assist in diagnosing website issues, ensuring proper indexing, and improving user experience. By identifying errors like broken links or redirects, they help maintain website performance and SEO effectiveness.
What is the Difference Between 2xx and 3xx Status Codes?
2xx codes represent successful requests, while 3xx codes indicate redirects. 2xx confirms the server processed the request, and 3xx informs the client that the resource has been moved or redirected.
How Do I Fix a 403 Forbidden Error?
A 403 Forbidden error occurs when a server blocks access to a resource due to insufficient permissions. To fix this, check and adjust file or directory permissions, update your .htaccess file, or modify security settings. If the issue persists, contact your hosting provider for assistance. Understanding web server status codes like 403 helps diagnose and resolve such access issues effectively.
How Can I Check HTTP Status Codes for My Website?
You can check web page status codes using various methods, including browser developer tools, online status checkers, and website crawlers. Tools like Screaming Frog, Google Search Console, and third-party HTTP header checkers help identify status codes, allowing you to diagnose errors and ensure smooth website performance.
Popular Searches
SEO Services
Website SEO Audit Packages
WordPress Development
Website Structure
E-commerce SEO Services
SEO For Ecommerce
SEO Packages
Types of SEO
SEO Audit Services
SEO for Education
Top YouTube Searches
Googlebots IP Addresses
SEO Services in Mumbai
SEO for Insurance
List of Search Engines
YouTube SEO Tools
Link Building Services
SEO for OTT Platforms
Top YT Cooking Channels
308 Permanent Redirect
SEO Services in Bangalore
WordPress SEO Services
What is a Blog
Import XML Formula
How useful was this post?
3.4
/ 5.
14 |
| Markdown | [Skip to content](https://www.infidigit.com/blog/http-status-codes/#content "Skip to content")
[](https://www.infidigit.com/)
- [Organic Search](https://www.infidigit.com/services/)
- - - Organic Search
- [SEO Services ](https://www.infidigit.com/seo-search-engine-optimization/)
- [CRO Services ](https://www.infidigit.com/conversion-rate-optimization/)
- [ASO Services ](https://www.infidigit.com/aso-app-store-optimization/)
- [SEO Audit Services ](https://www.infidigit.com/seo-audit/)
- [Enterprise SEO Services ](https://www.infidigit.com/enterprise-seo-services/)
- [Penalty Recovery Services ](https://www.infidigit.com/seo-penalty-recovery/)
Platforms
- [AI SEO Services ](https://www.infidigit.com/ai-seo-services/)
- [LLM SEO Services ](https://www.infidigit.com/llm-seo-services/)
- [Ecommerce SEO Services ](https://www.infidigit.com/e-commerce-seo/)
- [Local SEO Services ](https://www.infidigit.com/local-seo/)
- [WordPress SEO Services ](https://www.infidigit.com/wordpress-seo-services/)
- [Shopify SEO Services ](https://www.infidigit.com/shopify-seo-services/)
Industries
- [SEO for BFSI ](https://www.infidigit.com/industries/seo-for-bfsi/)
- [SEO for Ecommerce ](https://www.infidigit.com/industries/seo-for-ecommerce/)
- [SEO for EdTech ](https://www.infidigit.com/industries/seo-for-educational/)
- [SEO for B2B ](https://www.infidigit.com/industries/seo-for-b2b/)
- [SEO for Law Firms ](https://www.infidigit.com/industries/seo-for-law-firm/)
[View All](https://www.infidigit.com/industries/)
Overview
Driven by Results
We have a achieved outstanding growth for brands in various industries
\+3.1B
Total Organic Sessions
\+1.9B
Total Organic Clicks
\+1.24B
Total Organic User Acquisiton
- Winners of 70+ Prestigious Awards
- 150+ Experts
- A.I Capabilities
- Infigrowth TM Platform
- 100s of Proven Results
- [Website & Content]()
- - - Content & Outreach
- [Content Writing Services ](https://www.infidigit.com/content-writing-services/)
- [Ecommerce Content Writing ](https://www.infidigit.com/ecommerce-content-writing-services/)
- [BFSI Content Writing ](https://www.infidigit.com/bfsi-content-writing-services/)
- [Content Marketing Services ](https://www.infidigit.com/content-marketing-services/)
- [Guest Posting Services ](https://www.infidigit.com/guest-posting-services/)
- [Link Building Services ](https://www.infidigit.com/link-building/)
Design & Develop
- [Website Development Services ](https://www.infidigit.com/website-development-services/)
- [Site Speed Optimization Services ](https://www.infidigit.com/website-speed-optimization-services/)
- [Website Maintenance Services ](https://www.infidigit.com/website-maintenance-services/)
- [Website Design Services ](https://www.infidigit.com/website-design-services/)
- [Website Redesign Services ](https://www.infidigit.com/website-redesign-services/)
- [Logo Design Services ](https://www.infidigit.com/logo-design-services/)
Industries & Platform
- [WordPress Website Development ](https://www.infidigit.com/wordpress-development-services/)
- [Shopify Website Development ](https://www.infidigit.com/shopify-development-services/)
- [Webflow Website Development ](https://www.infidigit.com/webflow-development-services/)
- [Wix Website Development ](https://www.infidigit.com/wix-development-services/)
- [Magento Website development ](https://www.infidigit.com/magento-development-services/)
- [Woocommerce Development ](https://www.infidigit.com/woocommerce-development-services/)
[Read Our Reviews](https://www.infidigit.com/testimonials/)
[](https://www.infidigit.com/testimonials/)
[âTheir website designing skills are top-tier, and they were able to create a stunning and user-friendly website that perfectly captured our brand identity.â](https://www.infidigit.com/testimonials/)
[](https://www.infidigit.com/testimonials/)
[Read More](https://www.infidigit.com/testimonials/)
- Winners of 70+ Prestigious Awards
- 150+ Experts
- A.I Capabilities
- Infigrowth TM Platform
- 100s of Proven Results
- [Tools & Technology](https://www.infidigit.com/tools/)
- - - Tools
- [Infigrowth ](https://www.infigrowth.com/)
- [Rank Tracker ](https://www.infidigit.com/tools/rank-tracker/)
- [SearchSense ](https://www.infidigit.com/tools/search-sense/)
- [Free Rank Checker](https://www.infidigit.com/tools/rank-checker/)
- [Free Keyword Generator ](https://www.infidigit.com/tools/keyword-generator/)
- [SEO Extension ](https://chromewebstore.google.com/detail/infigrowth-seo-extension/jfoglaanpbhcocepekeocbdnlmifjgol?utm_source=infidigit-website&utm_medium=seo-ext-add-to-chrome&utm_campaign=sep-2024)
Schemas and Calculators
- [Article Schema ](https://www.infidigit.com/tools/article-schema-generator/)
- [FAQ Schema ](https://www.infidigit.com/tools/faq-schema-generator/)
- [Breadcrumb Schema ](https://www.infidigit.com/tools/breadcrumb-schema-generator/)
- [Person Schema ](https://www.infidigit.com/tools/person-schema-generator/)
- [HTTPS Status Checker ](https://www.infidigit.com/tools/http-status-checker/)
- [Keyword Density ](https://www.infidigit.com/tools/keyword-density-checker/)
- [Link Counter ](https://www.infidigit.com/tools/website-links-counter/)
- [Word Counter ](https://www.infidigit.com/tools/word-counter/)
- [ROAS Calculator ](https://www.infidigit.com/tools/roas-calculator/)
- [CPC Calculator ](https://www.infidigit.com/tools/cpc-calculator/)
- [Conversion Rate Calculator ](https://www.infidigit.com/tools/conversion-rate-calculator/)
[View All](https://www.infidigit.com/tools/)
[Platforms](https://www.infigrowth.com/?utm_source=infidigit-website&utm_medium=mega-menu-cta&utm_campaign=sep-2024)
[Infigrowth](https://www.infigrowth.com/?utm_source=infidigit-website&utm_medium=mega-menu-cta&utm_campaign=sep-2024)
[From keyword optimization to hacking growth, DIY your way to SEO success](https://www.infigrowth.com/?utm_source=infidigit-website&utm_medium=mega-menu-cta&utm_campaign=sep-2024)
[](https://www.infigrowth.com/?utm_source=infidigit-website&utm_medium=mega-menu-cta&utm_campaign=sep-2024)
- Winners of 70+ Prestigious Awards
- 150+ Experts
- A.I Capabilities
- Infigrowth TM Platform
- 100s of Proven Results
- [Plans](https://www.infidigit.com/get-started/)
- - - Plans
- [SEO Plans ](https://www.infidigit.com/seo-pricing-p1/)
- [Ecommerce SEO Plans ](https://www.infidigit.com/e-commerce-seo-pricing-p1/)
- [Enterprise SEO Plans ](https://www.infidigit.com/enterprise-seo-pricing-p1/)
- [SEO Audit Plans ](https://www.infidigit.com/seo-audit-pricing-p1/)
- [Ecommerce SEO Audit Plans ](https://www.infidigit.com/e-commerce-seo-audit-pricing-p1/)
- [Local SEO Plans ](https://www.infidigit.com/local-seo-pricing-p1/)
- [ASO Plans ](https://www.infidigit.com/aso-pricing-p1/)
- [CRO Plans ](https://www.infidigit.com/cro-pricing-p1/)
- [Content Writing Plans ](https://www.infidigit.com/content-writing-pricing-p1/)
- [YouTube SEO Plans ](https://www.infidigit.com/youtube-seo-pricing-p1/)
- [Amazon SEO Plans ](https://www.infidigit.com/amazon-seo-pricing-p1/)
[View All](https://www.infidigit.com/get-started/)
USP
Why Choose Us?
[](https://www.infidigit.com/clients/)
[](https://www.infidigit.com/testimonials/)
Free
[Meet an Expert](https://www.infidigit.com/get-demo/)
[A solutions expert will guide you personally to achieve your goals.](https://www.infidigit.com/get-demo/)
[](https://www.infidigit.com/get-demo/)
- Winners of 70+ Prestigious Awards
- 150+ Experts
- A.I Capabilities
- Infigrowth TM Platform
- 100s of Proven Results
- [Discover](https://www.infidigit.com/about/)
- - - Who We Are
- [About Infidigit ](https://www.infidigit.com/about/)
- [Teams ](https://www.infidigit.com/teams/)
- [About the Founder ](https://www.infidigit.com/about-our-founder-kaushal-thakkar/)
- [Life at Infidigit ](https://www.infidigit.com/life-at-infidigit/)
- [History of Infidigit ](https://www.infidigit.com/history/)
- [Careers ](https://www.infidigit.com/careers/)
Our Work
- [Clients ](https://www.infidigit.com/clients/)
- [Testimonials ](https://www.infidigit.com/testimonials/)
- [Awards ](https://www.infidigit.com/awards/)
- [Success Stories ](https://www.infidigit.com/case-study/)
- [Proven Results ](https://www.infidigit.com/proven-results/)
- [Media Coverage ](https://www.infidigit.com/media-coverage/)
Learn
- [Blogs ](https://www.infidigit.com/blog/)
- [News ](https://www.infidigit.com/news/)
- [TGG Podcast ](https://www.infidigit.com/growth-genius/)
- [Whitepapers ](https://www.infidigit.com/whitepaper/)
- [SEO Q\&A ](https://www.infidigit.com/qna-videos)
- [Webstories ](https://www.infidigit.com/web-stories/)
Winners
Great Place to Work
For two consecutive years, we are awarded by this honour

- Winners of 70+ Prestigious Awards
- 150+ Experts
- A.I Capabilities
- Infigrowth TM Platform
- 100s of Proven Results
- [Success Stories](https://www.infidigit.com/case-study/)
- - - By Service
- [SEO Case Studies ](https://www.infidigit.com/seo-case-studies/)
- [LLM SEO Case Studies ](https://www.infidigit.com/llm-case-studies/)
- [Ecommerce Case Studies ](https://www.infidigit.com/e-commerce-case-studies/)
- [CRO Case Studies ](https://www.infidigit.com/cro-case-studies/)
- [Content Case Studies ](https://www.infidigit.com/content-writing-case-studies/)
- [Website Development Case Studies ](https://www.infidigit.com/website-development-case-studies/)
By Industries
- [BFSI ](https://www.infidigit.com/bfsi-case-studies/)
- [Fitness ](https://www.infidigit.com/beauty-fitness-case-studies/)
- [Fashion ](https://www.infidigit.com/fashion-seo-case-studies/)
- [Healthcare ](https://www.infidigit.com/healthcare-seo-case-studies/)
- [B2B ](https://www.infidigit.com/b2b-seo-case-studies/)
- [EdTech ](https://www.infidigit.com/edtech-case-studies/)
By Goals
- [Website Traffic ](https://www.infidigit.com/website-traffic-case-studies/)
- [Lead Generation ](https://www.infidigit.com/leads-generation-case-studies/)
- [Revenue Growth ](https://www.infidigit.com/revenue-growth-case-studies/)
- [App Downloads ](https://www.infidigit.com/app-downloads-case-studies/)
- [Product Sales ](https://www.infidigit.com/product-sales-case-studies/)
[View All](https://www.infidigit.com/case-study/)
Results
Our Proven Results
[](https://www.infidigit.com/case-study/)
[](https://www.infidigit.com/awards/)
- Winners of 70+ Prestigious Awards
- 150+ Experts
- A.I Capabilities
- Infigrowth TM Platform
- 100s of Proven Results
- IN âž
- [USA](https://www.infidigit.us/)
[Get Free Proposal](https://www.infidigit.com/get-demo/)
[](https://www.infidigit.com/)
- IN âž
- [USA](https://www.infidigit.us/)
- [Organic Search](https://www.infidigit.com/services/)
- - - Organic Search
- [SEO Services ](https://www.infidigit.com/seo-search-engine-optimization/)
- [CRO Services ](https://www.infidigit.com/conversion-rate-optimization/)
- [ASO Services ](https://www.infidigit.com/aso-app-store-optimization/)
- [SEO Audit Services ](https://www.infidigit.com/seo-audit/)
- [Enterprise SEO Services ](https://www.infidigit.com/enterprise-seo-services/)
- [Penalty Recovery Services ](https://www.infidigit.com/seo-penalty-recovery/)
Platforms
- [AI SEO Services ](https://www.infidigit.com/ai-seo-services/)
- [LLM SEO Services ](https://www.infidigit.com/llm-seo-services/)
- [Ecommerce SEO Services ](https://www.infidigit.com/e-commerce-seo/)
- [Local SEO Services ](https://www.infidigit.com/local-seo/)
- [WordPress SEO Services ](https://www.infidigit.com/wordpress-seo-services/)
- [Shopify SEO Services ](https://www.infidigit.com/shopify-seo-services/)
Industries
- [SEO for BFSI ](https://www.infidigit.com/industries/seo-for-bfsi/)
- [SEO for Ecommerce ](https://www.infidigit.com/industries/seo-for-ecommerce/)
- [SEO for EdTech ](https://www.infidigit.com/industries/seo-for-educational/)
- [SEO for B2B ](https://www.infidigit.com/industries/seo-for-b2b/)
- [SEO for Law Firms ](https://www.infidigit.com/industries/seo-for-law-firm/)
[View All](https://www.infidigit.com/industries/)
Overview
Driven by Results
We have a achieved outstanding growth for brands in various industries
\+3.1B
Total Organic Sessions
\+1.9B
Total Organic Clicks
\+1.24B
Total Organic User Acquisiton
- Winners of 70+ Prestigious Awards
- 150+ Experts
- A.I Capabilities
- Infigrowth TM Platform
- 100s of Proven Results
- [Website & Content]()
- - - Content & Outreach
- [Content Writing Services ](https://www.infidigit.com/content-writing-services/)
- [Ecommerce Content Writing ](https://www.infidigit.com/ecommerce-content-writing-services/)
- [BFSI Content Writing ](https://www.infidigit.com/bfsi-content-writing-services/)
- [Content Marketing Services ](https://www.infidigit.com/content-marketing-services/)
- [Guest Posting Services ](https://www.infidigit.com/guest-posting-services/)
- [Link Building Services ](https://www.infidigit.com/link-building/)
Design & Develop
- [Website Development Services ](https://www.infidigit.com/website-development-services/)
- [Site Speed Optimization Services ](https://www.infidigit.com/website-speed-optimization-services/)
- [Website Maintenance Services ](https://www.infidigit.com/website-maintenance-services/)
- [Website Design Services ](https://www.infidigit.com/website-design-services/)
- [Website Redesign Services ](https://www.infidigit.com/website-redesign-services/)
- [Logo Design Services ](https://www.infidigit.com/logo-design-services/)
Industries & Platform
- [WordPress Website Development ](https://www.infidigit.com/wordpress-development-services/)
- [Shopify Website Development ](https://www.infidigit.com/shopify-development-services/)
- [Webflow Website Development ](https://www.infidigit.com/webflow-development-services/)
- [Wix Website Development ](https://www.infidigit.com/wix-development-services/)
- [Magento Website development ](https://www.infidigit.com/magento-development-services/)
- [Woocommerce Development ](https://www.infidigit.com/woocommerce-development-services/)
[Read Our Reviews](https://www.infidigit.com/testimonials/)
[](https://www.infidigit.com/testimonials/)
[âTheir website designing skills are top-tier, and they were able to create a stunning and user-friendly website that perfectly captured our brand identity.â](https://www.infidigit.com/testimonials/)
[](https://www.infidigit.com/testimonials/)
[Read More](https://www.infidigit.com/testimonials/)
- Winners of 70+ Prestigious Awards
- 150+ Experts
- A.I Capabilities
- Infigrowth TM Platform
- 100s of Proven Results
- [Tools & Technology](https://www.infidigit.com/tools/)
- - - Tools
- [Infigrowth ](https://www.infigrowth.com/)
- [Rank Tracker ](https://www.infidigit.com/tools/rank-tracker/)
- [SearchSense ](https://www.infidigit.com/tools/search-sense/)
- [Free Rank Checker](https://www.infidigit.com/tools/rank-checker/)
- [Free Keyword Generator ](https://www.infidigit.com/tools/keyword-generator/)
- [SEO Extension ](https://chromewebstore.google.com/detail/infigrowth-seo-extension/jfoglaanpbhcocepekeocbdnlmifjgol?utm_source=infidigit-website&utm_medium=seo-ext-add-to-chrome&utm_campaign=sep-2024)
Schemas and Calculators
- [Article Schema ](https://www.infidigit.com/tools/article-schema-generator/)
- [FAQ Schema ](https://www.infidigit.com/tools/faq-schema-generator/)
- [Breadcrumb Schema ](https://www.infidigit.com/tools/breadcrumb-schema-generator/)
- [Person Schema ](https://www.infidigit.com/tools/person-schema-generator/)
- [HTTPS Status Checker ](https://www.infidigit.com/tools/http-status-checker/)
- [Keyword Density ](https://www.infidigit.com/tools/keyword-density-checker/)
- [Link Counter ](https://www.infidigit.com/tools/website-links-counter/)
- [Word Counter ](https://www.infidigit.com/tools/word-counter/)
- [ROAS Calculator ](https://www.infidigit.com/tools/roas-calculator/)
- [CPC Calculator ](https://www.infidigit.com/tools/cpc-calculator/)
- [Conversion Rate Calculator ](https://www.infidigit.com/tools/conversion-rate-calculator/)
[View All](https://www.infidigit.com/tools/)
[Platforms](https://www.infigrowth.com/?utm_source=infidigit-website&utm_medium=mega-menu-cta&utm_campaign=sep-2024)
[Infigrowth](https://www.infigrowth.com/?utm_source=infidigit-website&utm_medium=mega-menu-cta&utm_campaign=sep-2024)
[From keyword optimization to hacking growth, DIY your way to SEO success](https://www.infigrowth.com/?utm_source=infidigit-website&utm_medium=mega-menu-cta&utm_campaign=sep-2024)
[](https://www.infigrowth.com/?utm_source=infidigit-website&utm_medium=mega-menu-cta&utm_campaign=sep-2024)
- Winners of 70+ Prestigious Awards
- 150+ Experts
- A.I Capabilities
- Infigrowth TM Platform
- 100s of Proven Results
- [Plans](https://www.infidigit.com/get-started/)
- - - Plans
- [SEO Plans ](https://www.infidigit.com/seo-pricing-p1/)
- [Ecommerce SEO Plans ](https://www.infidigit.com/e-commerce-seo-pricing-p1/)
- [Enterprise SEO Plans ](https://www.infidigit.com/enterprise-seo-pricing-p1/)
- [SEO Audit Plans ](https://www.infidigit.com/seo-audit-pricing-p1/)
- [Ecommerce SEO Audit Plans ](https://www.infidigit.com/e-commerce-seo-audit-pricing-p1/)
- [Local SEO Plans ](https://www.infidigit.com/local-seo-pricing-p1/)
- [ASO Plans ](https://www.infidigit.com/aso-pricing-p1/)
- [CRO Plans ](https://www.infidigit.com/cro-pricing-p1/)
- [Content Writing Plans ](https://www.infidigit.com/content-writing-pricing-p1/)
- [YouTube SEO Plans ](https://www.infidigit.com/youtube-seo-pricing-p1/)
- [Amazon SEO Plans ](https://www.infidigit.com/amazon-seo-pricing-p1/)
[View All](https://www.infidigit.com/get-started/)
USP
Why Choose Us?
[](https://www.infidigit.com/clients/)
[](https://www.infidigit.com/testimonials/)
Free
[Meet an Expert](https://www.infidigit.com/get-demo/)
[A solutions expert will guide you personally to achieve your goals.](https://www.infidigit.com/get-demo/)
[](https://www.infidigit.com/get-demo/)
- Winners of 70+ Prestigious Awards
- 150+ Experts
- A.I Capabilities
- Infigrowth TM Platform
- 100s of Proven Results
- [Discover](https://www.infidigit.com/about/)
- - - Who We Are
- [About Infidigit ](https://www.infidigit.com/about/)
- [Teams ](https://www.infidigit.com/teams/)
- [About the Founder ](https://www.infidigit.com/about-our-founder-kaushal-thakkar/)
- [Life at Infidigit ](https://www.infidigit.com/life-at-infidigit/)
- [History of Infidigit ](https://www.infidigit.com/history/)
- [Careers ](https://www.infidigit.com/careers/)
Our Work
- [Clients ](https://www.infidigit.com/clients/)
- [Testimonials ](https://www.infidigit.com/testimonials/)
- [Awards ](https://www.infidigit.com/awards/)
- [Success Stories ](https://www.infidigit.com/case-study/)
- [Proven Results ](https://www.infidigit.com/proven-results/)
- [Media Coverage ](https://www.infidigit.com/media-coverage/)
Learn
- [Blogs ](https://www.infidigit.com/blog/)
- [News ](https://www.infidigit.com/news/)
- [TGG Podcast ](https://www.infidigit.com/growth-genius/)
- [Whitepapers ](https://www.infidigit.com/whitepaper/)
- [SEO Q\&A ](https://www.infidigit.com/qna-videos)
- [Webstories ](https://www.infidigit.com/web-stories/)
Winners
Great Place to Work
For two consecutive years, we are awarded by this honour

- Winners of 70+ Prestigious Awards
- 150+ Experts
- A.I Capabilities
- Infigrowth TM Platform
- 100s of Proven Results
- [Success Stories](https://www.infidigit.com/case-study/)
- - - By Service
- [SEO Case Studies ](https://www.infidigit.com/seo-case-studies/)
- [LLM SEO Case Studies ](https://www.infidigit.com/llm-case-studies/)
- [Ecommerce Case Studies ](https://www.infidigit.com/e-commerce-case-studies/)
- [CRO Case Studies ](https://www.infidigit.com/cro-case-studies/)
- [Content Case Studies ](https://www.infidigit.com/content-writing-case-studies/)
- [Website Development Case Studies ](https://www.infidigit.com/website-development-case-studies/)
By Industries
- [BFSI ](https://www.infidigit.com/bfsi-case-studies/)
- [Fitness ](https://www.infidigit.com/beauty-fitness-case-studies/)
- [Fashion ](https://www.infidigit.com/fashion-seo-case-studies/)
- [Healthcare ](https://www.infidigit.com/healthcare-seo-case-studies/)
- [B2B ](https://www.infidigit.com/b2b-seo-case-studies/)
- [EdTech ](https://www.infidigit.com/edtech-case-studies/)
By Goals
- [Website Traffic ](https://www.infidigit.com/website-traffic-case-studies/)
- [Lead Generation ](https://www.infidigit.com/leads-generation-case-studies/)
- [Revenue Growth ](https://www.infidigit.com/revenue-growth-case-studies/)
- [App Downloads ](https://www.infidigit.com/app-downloads-case-studies/)
- [Product Sales ](https://www.infidigit.com/product-sales-case-studies/)
[View All](https://www.infidigit.com/case-study/)
Results
Our Proven Results
[](https://www.infidigit.com/case-study/)
[](https://www.infidigit.com/awards/)
- Winners of 70+ Prestigious Awards
- 150+ Experts
- A.I Capabilities
- Infigrowth TM Platform
- 100s of Proven Results
# HTTP Status Codes: List of HTTP Response Status Codes
[](https://www.infidigit.com/blog/author/aishwaryakirodian/)
[Aishwarya Kirodian](https://www.infidigit.com/blog/author/aishwaryakirodian/)
Aishwarya Kirodian is an experienced SEO analyst with skills in sales, business development, and market research. A marketing professional graduated from NMIMS University. [In](https://in.linkedin.com/in/aishwarya-kirodian-3177ba63)

Reviewed By
Growth Team
This post is contributed by the Growth Team, dedicated to providing insights and updates on the latest trends and best practices.
- Published on
April 2, 2025
- Reading Time
22 min read
[Home](https://www.infidigit.com/) \> [HTTP Status Code](https://www.infidigit.com/blog/category/http-status-code/) \> HTTP Status Codes: List of HTTP Response Status Codes
[](https://www.infidigit.com/blog/author/aishwaryakirodian/)
[Aishwarya Kirodian](https://www.infidigit.com/blog/author/aishwaryakirodian/)
- [Published on April 2, 2025](https://www.infidigit.com/blog/http-status-codes/)
- 
Reviewed By
Growth Team
This post is contributed by the Growth Team, dedicated to providing insights and updates on the latest trends and best practices.
- Reading Time
22 min read
HTTP Status Codes: List of HTTP Response Status Codes
[](https://www.infidigit.com/blog/http-status-codes/#section-of_comment)
[](https://www.infidigit.com/blog/http-status-codes/#elementor-action%3Aaction%3Dpopup%3Aopen%26settings%3DeyJpZCI6Ijg3OTYwIiwidG9nZ2xlIjpmYWxzZX0%3D)
Table of Contents
- [What are HTTP status codes?](https://www.infidigit.com/blog/http-status-codes/#What_are_HTTP_status_codes)
- [Why do HTTP Status Codes Matter for SEO?](https://www.infidigit.com/blog/http-status-codes/#Why_do_HTTP_Status_Codes_Matter_for_SEO)
- [List of HTTP Status Codes](https://www.infidigit.com/blog/http-status-codes/#List_of_HTTP_Status_Codes)
- [List of HTTP Status Codes and What They Mean](https://www.infidigit.com/blog/http-status-codes/#List_of_HTTP_Status_Codes_and_What_They_Mean)
- [Tools for Checking HTTP Status Codes](https://www.infidigit.com/blog/http-status-codes/#Tools_for_Checking_HTTP_Status_Codes)
- [FAQs about HTTP Status Codes](https://www.infidigit.com/blog/http-status-codes/#FAQs_about_HTTP_Status_Codes)
- [Popular Searches](https://www.infidigit.com/blog/http-status-codes/#Popular_Searches)
Letâs Connect & Accelerate Your Organic Growth
- Your data is properly secured encrypted by SSL
3\.4
(14)
Every time you browse the internet, thereâs a silent exchange of messages between your browser and the server hosting the website. These messages, known as HTTP status codes, are crucial in ensuring smooth communication. Whether youâre accessing a webpage, encountering an error, or being redirected, these codes tell you exactly whatâs going on behind the scenes.
HTTP status codes help determine whether the page is accessible, what went wrong, and what action you need to take. Understanding these codes is essential for anyone managing websites, troubleshooting online issues, or looking to improve their websiteâs performance. In this article, we will explain HTTP status codes in detail and provide a comprehensive list to help you understand their meanings and implications better.
## **What are HTTP status codes?**
In simple terms, **HTTP status codes** are messages that a server sends to a browser to indicate the result of a request. When you type a website address into your browser, it sends a request to the server. In return, the server sends back a three-digit HTTP status code, indicating whether the request was successful or if there was an issue.
These codes act as a form of communication between browsers and servers. Think of them as âsignalsâ that tell browsers how to handle the requested page.
Understanding HTTP status codes is not just for technical people. If you manage a website, knowing these codes is crucial for identifying errors, reducing website downtime, and ensuring a smooth user experienceâall of which contribute to improving **search engine rankings**.
John Mueller explained that HTTP status codes are the first thing Google checks when crawling the content.
He was posed with the question:
âWondering if Google checks status codes before anything else, like before rendering content?â
In response, Mueller confirmed that Google does check the status codes before rendering or indexing content. Google checks for a â200â status code before proceeding with crawling any further. A 200 status code indicates to Google that it is crawling a valid page and there might be content worth indexing on it. Here is the video on different errors that Google may find & report while crawling your website


## **Why do HTTP Status Codes Matter for SEO?**
You may not always see HTTP status codes when browsing a webpage, but they are incredibly important behind the scenes. If a webpage is unavailable, for example, the browser will receive an HTTP status code showing the issue, such as a server error or a missing page.
These codes impact **Search Engine Optimization (SEO)** significantly. Search engines like Google rely on HTTP status codes to detect errors, crawlability issues, and even reduce website downtime. When Google crawls a website, it first checks the HTTP status code before anything else.
For instance, a **200 OK** status code signals to Google that the page is valid, functional, and ready to be indexed. Pages that return this code are considered **crawlable** and **indexable**, which is essential for **ranking** in search engines. If a page returns a **404** or **500** status code, it can negatively affect your SEO.
John Mueller, a Google Search Advocate, explained that Google checks these codes before proceeding to crawl and index the content. If Google encounters a **200 status code**, it indicates that the page is healthy, and the content may be worth indexing. You can watch his video on the **errors that Google might find and report** while crawling your website.
## **List of HTTP Status Codes**
HTTP status codes are divided into five groups based on their first digit. Each group signifies a different type of response from the server.
- 1xx HTTP status codes group (Informational): These codes tell you that the server has received and is processing your request.
- 2xx HTTP status codes group (Success): These codes mean your request was successful.
- 3xx HTTP status codes group (Redirection): These codes tell you that further action is needed to complete the request (usually a redirect to a new URL).
- 4xx HTTP status codes group (Client Error): These codes indicate that there was an issue with the request you sent.
- 5xx HTTP status codes group â (Server Error): These codes mean thereâs a problem on the server side.
Hereâs an interesting and detailed image that will help you understand the different types of HTTP response codes you might encounter when accessing a webpage.

## **List of HTTP Status Codes and What They Mean**
HTTP status codes are categorized into five main groups, each representing a different type of response from the server. Below is a breakdown of each group and what the various status codes within them signify.
### **1xx HTTP response status codes group**
#### **100 Status Code: Continue**
The 100 Continue status code means that the server has received the initial part of the request and is ready to continue processing. Itâs often used when the client is sending large amounts of data, allowing the server to confirm that itâs prepared to handle the entire request before the data is fully transmitted.
**Example:** This might occur when submitting large files in a POST request.
#### **101 Status Code: Switching Protocol**
The 101 Switching Protocols status code indicates that the client requested a protocol change (e.g., upgrading from HTTP to HTTPS or switching to WebSocket) and the server agrees. This ensures that communication between the client and server can occur using a more secure or appropriate protocol.
**Example:** Upgrading from HTTP to HTTPS for security purposes.
#### **102 Status Code: Processing**
This code signals that the server has received the request, but itâs still being processed. This is common for long-running tasks that take time to complete. It tells the client to wait while the server processes the request.
**Example:** Used when executing large database queries or processing complex operations.
#### **103 Status Code: Early Hints**
The 103 Early Hints status code tells the client about preloaded resources (such as images, scripts, or CSS files) before the full response is ready. This allows the browser to start loading resources early, improving page load times.
**Example:** Preloading resources for faster rendering while waiting for the final response.
### **2xx HTTP response status codes group**
These codes indicate that the request was successfully received, understood, and processed by the server.
#### **201 Status Code: Created**
A 201 status code indicates that a new resource has been successfully created as a result of the clientâs request. Itâs commonly used for POST requests, such as creating a new user or submitting a form.
**Example:** After submitting a form to create a new blog post, you may see this status code.
#### **202 Status Code: Accepted**
The 202 Accepted status code means the server has received and accepted the request, but the process is not yet complete. Itâs useful for asynchronous tasks that take time to finish.
**Example:** A background task for processing an order might return this code, indicating that the order is in progress but not yet finalized.
#### **203 Status Code: Non-Authoritative Information**
The 203 status code is returned when the server successfully processes the request, but the response is based on third-party information, not the origin server.
**Example:** When fetching data from a cache instead of the original server.
#### **204 Status Code: No Content**
A 204 No Content status code tells the client that the server has successfully processed the request, but there is no content to send in the response body. This often happens after a successful action, such as form submission.
**Example:** After submitting a contact form where no additional data needs to be returned.
#### **205 Status Code: Reset Content**
The 205 Reset Content status code instructs the client to reset the documentâs state. Itâs typically used in forms to clear the form fields after submission.
**Example:** After submitting a form with errors, the server might send a 205 response to reset the form fields.
#### **206 Status Code: Partial Content**
The 206 Partial Content status code indicates that the server is returning part of the requested resource. This is often used for large files that are downloaded in chunks.
**Example:** Downloading a large video file in multiple parts.
#### **207 Status Code: Multi-Status**
This code indicates that the server has returned information from multiple resources in a single response, typically used in batch processing operations.
**Example:** A single request that modifies multiple resources, such as adding new records to a database.
#### **208 Status Code: Already Reported**
This code is used to avoid redundant reporting when the same resource has been listed previously. It helps improve efficiency, especially in collaboration environments.
**Example:** In a collaborative environment, when multiple users edit the same file, this status code prevents redundant enumeration.
#### **226 Status Code: IM Used**
The 226 IM Used status code indicates that the server has fulfilled the request and applied some modifications to the resource during the process, such as applying an Instance Manipulation (IM) operation.
**Example:** Applying image optimization during an HTTP GET request.
### **3xx HTTP response status codes group**
The 3xx range of HTTP status codes is used for redirection. These codes indicate that the client must take additional actions to complete the request.
#### **300 Status Code: Multiple Choice**
The 300 Multiple Choices status code indicates that the server has multiple options for the requested resource, but it does not specify which one to choose. The client may have several ways to access the same resource, such as different formats or languages. The server leaves the decision to the client or user.
**Example:** Imagine visiting a website that supports both English and Spanish versions. When you request the resource, the server responds with a 300 Multiple Choices status code, listing the available language versions. The user can then select which version to view.
#### **301 Status Code: Permanent Redirection**
The 301 Moved Permanently status code indicates that the requested resource has been permanently moved to a new URL. Both browsers and search engines will now use the new location for future requests. This code is important for maintaining SEO integrity, as search engines update their indexes to reflect the new URL, ensuring that search rankings are preserved.
**Example:** If a website undergoes a major restructuring and a pageâs URL changes permanently, the server responds with a 301 status code, ensuring that any links or search engine results pointing to the old URL will redirect to the new one.
**SEO Tip:** When using a 301 redirect, itâs important to implement it properly to avoid 404 errors and ensure your SEO rankings are preserved.
Here is what Googleâs John Mueller has to say on how long it will take to rank a new URL after doing a 301 redirect to the old URL:


#### **302 Status Code: Temporary Redirection**
The 302 Found status code (formerly called âMoved Temporarilyâ) tells the client that the requested resource has temporarily moved to a different URL. Unlike the 301 status code, this change is not permanent, and future requests should use the original URL.
**Example:** A webpage might be temporarily moved during maintenance or for special events. For instance, if an e-commerce site has a special sale on a subdomain, a 302 redirect can be used to direct users to a temporary location.
#### **303 Status Code: See Other**
The 303 See Other status code tells the client to retrieve the requested resource from a different URL using a GET request. This is commonly used after a POST request to indicate that the response is available at another location and that a GET request should be used to fetch it.
**Example:** After submitting an online form (POST), the server might return a 303 status code to inform the client that the result of the submission is available at another URL via a GET request.
#### **304 Status Code: Not Modified**
The 304 Not Modified status code indicates that the requested resource has not changed since the last time it was requested. The client can continue using the cached version of the resource, saving bandwidth and reducing load times.
**Example:** A user revisits a website and their browser sends a request for a resource. The server checks the last modification date of the resource and, if it hasnât changed, returns a 304 status code to inform the browser to use the cached version.
#### **305 Status Code: Use Proxy (Deprecated in HTTP/1.1)**
The 305 Use Proxy status code was used to indicate that the client must access the requested resource through a specified proxy. However, this status code was deprecated in HTTP/1.1 and is no longer used in modern web development. Other codes, such as 407 (Proxy Authentication Required), are used in its place.
#### **307 Status Code: Temporary Redirect**
The 307 Temporary Redirect status code indicates that the resource has temporarily moved to a new URL. Unlike a 302 redirect, the 307 code specifies that the HTTP method used for the request (e.g., POST or GET) should remain unchanged when following the redirect.
**Example:** If an API endpoint temporarily moves but the server doesnât want to change the request method, it will return a 307 status code to ensure that the client uses the same HTTP method to fetch the resource from the new location.
#### **308 Status Code: Permanent Redirect**
The 308 Permanent Redirect status code is similar to the 301 code, but it ensures that the HTTP method used in the original request is preserved when redirected to the new URL.
**Example:** A REST API endpoint that permanently moves to a new URL and wants to ensure that POST requests are also forwarded as POST requests would return a 308 status code.
### **4xx HTTP response status codes group**
The 4xx range is reserved for client-side errors. These errors usually occur when there is an issue with the request sent to the server.
#### **400 Status Code: Bad Request**
The 400 Bad Request status code indicates that the server could not understand the request due to malformed syntax. This typically happens due to issues like missing parameters, incorrect formatting, or invalid query syntax.
**Example:** If a user sends a request with an invalid URL (like a malformed query string), the server will respond with a 400 error, prompting the user to correct the issue.
#### **401 Status Code: Unauthorized Error**
The 401 Unauthorized status code is returned when the client must authenticate before accessing the requested resource. This error occurs when the request is missing valid authentication credentials, or the credentials provided are not sufficient.
**Example:** When attempting to access a secure page on a website that requires login credentials, the server will return a 401 status code if the user hasnât logged in or provided invalid credentials.
#### **402 Status Code: Payment Required**
The 402 Payment Required status code was originally intended to indicate that the client needs to pay for access to the resource. However, it is not widely used and is reserved for future use.
#### **403 Status Code: Forbidden Error**
The 403 Forbidden status code indicates that the server understands the request, but refuses to authorize it. This could be because the user doesnât have the necessary permissions or access rights to the resource.
**Example:** If a user tries to access a protected page (like an admin dashboard) without the correct permissions, the server will return a 403 status code.
#### **404 Status Code: Page Not Found**
The 404 Not Found status code occurs when the requested resource cannot be found on the server. This is one of the most common errors encountered on the web, usually indicating that the URL was typed incorrectly, or the page was removed.
**Example:** If a user tries to access a non-existent page, such as example.com/about-us, theyâll see a 404 error because the page does not exist.
SEO Tip: Properly handling 404 errors can help improve user experience and SEO. Itâs advisable to create a custom 404 page and manage broken links to maintain the siteâs SEO ranking.


#### **405 Status Code: Method Not Allowed**
The 405 Method Not Allowed status code occurs when the client sends a request using an HTTP method that the resource does not support. For example, trying to submit a form with a GET request instead of POST will trigger this error.
**Example:** If a form is designed to be submitted via POST but a user tries to access it via a GET request, the server will respond with a 405 error.
#### **406 Status Code: Not Acceptable**
The 406 Not Acceptable status code is returned when the server is unable to provide a version of the resource that meets the clientâs preferences, such as language or media type. This happens when the server canât match the content with what the client accepts.
**Example:** If a client requests a page in French but the server only has the page available in English, it might return a 406 error.
#### **407 Status Code: Proxy Authentication Required**
The 407 Proxy Authentication Required status code is similar to the 401 Unauthorized error, but it indicates that the client must authenticate with a proxy server before the request can proceed.
**Example:** A client behind a corporate firewall or proxy server might see this error if the server requires authentication to pass the request through the proxy.
#### **408 Status Code: Request Timeout**
The â408 Request Timeoutâ status code is returned when the clientâs request took too long to complete, and the server decides to close the connection. This typically happens when the client does not send a request or complete a request within a certain time frame. Servers use this to prevent idle connections from consuming server resources. In many cases, a timeout might occur if the client is uploading a large file and it takes longer than expected to complete the operation.
**Example:** If youâre trying to upload a 10MB file over a slow connection and it takes too long, the server may close the connection and return a 408 error, asking you to resend the request.
#### **409 Status Code: Conflict**
The â409 Conflictâ error occurs when a request cannot be completed because it conflicts with the current state of the server or resource. This can happen when the client is attempting an operation that cannot be performed due to conflicting information. The conflict may be due to data changes made by another client or system.
**Example:** If two users try to update the same database record at the same time, the second update attempt might trigger a 409 error, indicating a conflict with the data.
#### **410 Status Code: Gone**
The â410 Goneâ status code indicates that the requested resource has been permanently removed from the server and is no longer available, with no forwarding address. Unlike a â404 Not Foundâ error, which could mean that the resource is temporarily unavailable, a 410 error means the resource has been intentionally and permanently deleted. This helps inform users and search engines that the resource will not return.
**Example:** If an online store deletes a product page permanently and does not redirect it elsewhere, users trying to access that page will receive a 410 error.
#### **411 Status Code: Length Required**
A â411 Length Requiredâ error is returned when the server expects the client to include a Content-Length header in the request but it is missing. This header specifies the size of the request body in bytes. If the client fails to provide this information, the server cannot process the request properly and rejects it with a 411 error.
**Example:** When submitting a POST request with data (e.g., form data or JSON), the client needs to specify how much data is being sent by including the Content-Length header. If omitted, the server responds with a 411 status.
#### **412 Status Code: Precondition Failed**
The â412 Precondition Failedâ status code indicates that one or more conditions provided by the client in the request headers could not be satisfied by the server. These conditions are often specified using the If-Match, If-None-Match, If-Modified-Since, or If-Unmodified-Since headers. If the condition is not met, the server will return this error.
**Example:** If a client sends a request to update a resource with an If-Match header that contains an outdated version of the resource, the server will return a 412 error, indicating the precondition has failed.
#### **413 Status Code: Payload Too Large**
The â413 Payload Too Largeâ status code occurs when the request is too large for the server to process. This is typically seen when the client is sending a request with a body that exceeds the maximum allowed size configured on the server. Servers often limit the size of the data they can handle to prevent abuse or resource exhaustion.
**Example:** Uploading a file that exceeds the serverâs size limit (e.g., attempting to upload a 100MB file to a server that allows a maximum of 10MB) would result in a 413 error.
#### **414 Status Code: URL Too Long**
The â414 URI Too Longâ status code is returned when the URL of the request exceeds the maximum length the server can process. URLs are subject to length limitations, and if the client sends a request with an excessively long URL, the server will reject it. This error often arises when the URL contains a large number of query parameters or data.
**Example:** A search URL with many parameters or a URL that encodes large amounts of data could exceed the serverâs length restrictions, triggering a 414 error.
#### **415 Status Code: Unsupported Media Type**
The â415 Unsupported Media Typeâ error indicates that the server cannot process the request because the media type (e.g., content type) is not supported. The clientâs request is typically accompanied by a Content-Type header, which specifies the format of the data being sent (e.g., application/json, text/html). If the server doesnât support the specified format, it will return a 415 status code.
**Example:** If you try to upload an image in a format like .webp to a server that only accepts .jpg or .png, the server would return a 415 error due to unsupported media.
#### **416 Status Code: Range Not Satisfiable**
The â416 Range Not Satisfiableâ status code occurs when the Range header sent in the request specifies a range of bytes that is outside the bounds of the file or resource. If the client requests a range that exceeds the file size or is invalid, the server returns this error to indicate it cannot fulfill the request.
**Example:** If a client requests the first 1000 bytes of a file, but the file is only 500 bytes long, the server will return a 416 error because the requested range cannot be satisfied.
#### **417 Status Code: Expectation Failed**
The â417 Expectation Failedâ status code is returned when the server cannot meet the expectations specified by the client in the Expect header. The Expect header allows the client to set certain expectations (e.g., Expect: 100-continue), and if the server is unable to fulfill these expectations, it will return a 417 error.
**Example:** If the client sends a Expect: 100-continue header but the server cannot process the request due to internal issues, it will respond with a 417 error.
#### **418 Status Code: Iâm a teapot**
The â418 Iâm a Teapotâ status code is part of an April Foolsâ joke in the âHyper Text Coffee Pot Control Protocolâ (HTCPCP). It humorously indicates that a teapot cannot brew coffee. While not meant for real-world usage, this status code has become a well-known part of internet culture.
**Example:** Sending a request to a server that supports HTCPCP to brew coffee with a teapot would return a 418 status code.
#### **421 Status Code: Misdirected Request**
The â421 Misdirected Requestâ status code is returned when a request is sent to the wrong server, and the server cannot process it because it is not configured to handle the request. This typically occurs in environments with multiple servers that serve different purposes.
**Example:** If a client sends a request to the wrong server in a load-balanced environment, the server will return a 421 error.
#### **422 Status Code: Unprocessable Entity**
The â422 Unprocessable Entityâ status code is returned when the server understands the content of the request but cannot process it due to semantic errors. This often occurs when data in the request is valid in structure but fails validation rules (e.g., missing required fields or incorrect data format).
**Example:** Submitting a form with incomplete or invalid data (e.g., a date in the wrong format) could result in a 422 error.
#### **423 Status Code: Locked**
The â423 Lockedâ status code indicates that the requested resource is locked and cannot be accessed or modified at the moment. This often occurs when a resource is being edited or is in use by another process.
**Example:** If a user is editing a document and another user tries to access it, the server may return a 423 error indicating that the document is locked.
#### **424 Status Code: Failed Dependency**
The â424 Failed Dependencyâ status code is used when a request fails due to the failure of a preceding request that it depends on. This is often seen in WebDAV or similar protocols where the successful execution of one request depends on the success of another.
**Example:** If a DELETE request fails, a subsequent request that depends on the deleted resource will return a 424 error.
#### **425 Status Code: Too Early**
The â425 Too Earlyâ status code is used to indicate that the server is not ready to process a request because it was received too early. This can help prevent issues like replay attacks or race conditions that could arise if the request is processed prematurely.
**Example:** A client trying to process a request too soon after a previous request, potentially causing unintended consequences, would result in a 425 error.
#### **426 Status Code: Upgrade Required**
The â426 Upgrade Requiredâ status code indicates that the client must upgrade to a different protocol to access the requested resource. This could be to a newer version of HTTP or another protocol entirely (e.g., switching from HTTP/1.1 to HTTP/2).
**Example:** If a server requires HTTP/2 for certain operations, but the client is using HTTP/1.1, the server will return a 426 error.
#### **428 Status Code: Precondition Required**
The â428 Precondition Requiredâ status code indicates that the server requires certain conditions to be met before processing the request. This is typically used in scenarios where operations should only be performed if specific preconditions are met (e.g., ensuring a resource hasnât changed).
**Example:** Before updating a document, the client may need to ensure that the document has not been modified since the last request by including an If-Match header. If this condition is not met, a 428 error is returned.
#### **429 Status Code: Too Many Requests**
The â429 Too Many Requestsâ status code is returned when the client has sent too many requests in a given time period and is being rate-limited. This is often used to prevent abuse or excessive load on the server.
**Example:** If you hit an API rate limit by sending too many requests in a short time, the server will return a 429 error, and you may also receive a Retry-After header with a time when you can retry the request.
#### **431 Status Code: Request Header Fields Too Large**
The â431 Request Header Fields Too Largeâ status code is returned when the requestâs header fields (e.g., cookies or HTTP headers) exceed the serverâs size limits.
**Example:** If a client sends a request with very large cookies or headers, causing the server to exceed its size limit for headers, a 431 error will be returned.
#### **451 Status Code: Unavailable For Legal Reasons**
The â451 Unavailable For Legal Reasonsâ status code indicates that the requested resource cannot be accessed due to legal restrictions. This may occur if the content is blocked in certain jurisdictions due to censorship, legal disputes, or government regulations.
**Example:** A streaming service might block access to a movie in certain countries due to legal issues, returning a 451 error when users attempt to access it from those locations.
### **5xx HTTP response status codes group**
#### **500 Status Code: Internal Server Error**
The â500 Internal Server Errorâ indicates that the server encountered an unexpected condition or issue that prevented it from fulfilling the request. This error does not specify the exact problem but points to an internal issue within the server, such as a misconfiguration or a server-side failure. It typically means the problem lies with the server itself, requiring further investigation by the server administrator or technical team.
**Example:** If a website experiences a sudden software crash or a malfunctioning server-side script, users trying to access the site may see a 500 error. The root cause might be a misconfigured script, insufficient server resources, or an issue with the serverâs infrastructure.
#### **501 Status Code: Not Implemented**
The â501 Not Implementedâ error occurs when the server does not recognize the request method used by the client and is unable to support it. This can happen when a client sends a request using a method (such as PUT, DELETE, or PATCH) that the server is not configured to handle. Essentially, the server cannot process the request using the specified method.
**Example:** A client sends a DELETE request to a server, but the server does not support or allow the DELETE method for the requested resource. As a result, the server responds with a 501 error.
#### **502 Status Code: Bad Gateway**
The â502 Bad Gatewayâ error occurs when a server, acting as a gateway or proxy, receives an invalid response from an upstream server while trying to fulfill a request. This error indicates a communication failure between servers, where the gateway server could not get a valid response from the upstream server it was trying to access.
**Example:** If youâre using a reverse proxy (e.g., Nginx or Apache) that forwards requests to a backend web server, and the backend server returns an invalid or no response, the proxy server will return a 502 error. This is common in server-side failures, like a backend database going down.
#### **503 Status Code: Service unavailable**
The â503 Service Unavailableâ status code is returned when the server is temporarily unable to process the request. This typically happens when the server is overloaded or undergoing maintenance. Itâs a temporary condition, and the server should return to normal operation once the issue is resolved.
**Example:** If a popular website experiences high traffic, it may overload the server, leading to a 503 error. Similarly, during scheduled maintenance or updates, users trying to access the site may encounter this error.
#### **504 Status Code: Gateway Timeout**
The â504 Gateway Timeoutâ error occurs when a server acting as a gateway or proxy does not receive a timely response from another server it is trying to access in order to load a web page or fulfill a request. This often happens when the upstream server takes too long to respond, causing the gateway server to timeout.
**Example:** If a user tries to access a website that requires data from a third-party service, and that third-party service is slow to respond or unavailable, the gateway server will return a 504 error, indicating that the timeout was caused by the upstream service.
#### **505 Status Code: HTTP Version Not Supported**
The â505 HTTP Version Not Supportedâ error occurs when the server does not support the version of the HTTP protocol used in the clientâs request. This error typically arises when the client uses an outdated or unsupported HTTP version that the server cannot process.
**Example:** If a client sends a request using HTTP/1.0 but the server only supports HTTP/1.1 or HTTP/2, the server will return a 505 error because it cannot handle the older version.
#### **506 Status Code: Variant Also Negotiates**
The â506 Variant Also Negotiatesâ status code indicates that the server has an internal configuration error. It typically happens when a server attempts to select a variant of the requested resource but encounters a problem in the content negotiation process. The error occurs when the server cannot determine the appropriate variant resource.
**Example:** A server misconfiguration, such as when multiple resources are set to negotiate content but one of them is also configured to perform content negotiation itself, leading to a conflict that results in a 506 error.
#### **507 Status Code: Insufficient Storage**
The â507 Insufficient Storageâ error indicates that the server does not have enough storage space to complete the request. This typically happens when the server runs out of storage or resources needed to fulfill the operation, such as when the server cannot write to the file system or database.
**Example:** If a server running a file-sharing application runs out of disk space while uploading a new file, it may return a 507 error indicating insufficient storage.
#### **508 Status Code: Loop Detected**
The â508 Loop Detectedâ status code occurs when the server detects an infinite loop while processing a request. This usually happens when a request is repeatedly forwarded between multiple resources without ever reaching its destination, causing the server to detect a processing loop.
**Example:** If a URL is incorrectly configured to redirect to itself or another URL that redirects back to the original, an infinite loop will occur, and the server will return a 508 error.
#### **510 Status Code: Not Extended**
The â510 Not Extendedâ error indicates that the server requires additional extensions or features to fulfill the request. The current request lacks the necessary extensions or features, meaning the server cannot process it successfully without further modifications or additions.
**Example:** If the server requires specific headers or protocols to process a request but the client does not provide them, the server may return a 510 error.
#### **511 Status Code: Network Authentication Required**
The â511 Network Authentication Requiredâ error occurs when the client must authenticate with the network before the server will allow access. This is often seen with captive portals, such as those in public Wi-Fi networks, where the user must authenticate or log in before they can access the internet.
**Example:** A user connects to a public Wi-Fi network and tries to visit a website, but they receive a 511 error indicating they need to complete a login or authentication process before they can proceed.
## **Tools for Checking HTTP Status Codes**
There are several tools available to help you check the HTTP status codes of your websiteâs pages, which is crucial for monitoring site health and optimizing SEO. These tools provide insights into server responses, identifying issues like broken links, redirects, or inaccessible pages. Here are some popular [tools for checking HTTP status codes](https://www.infidigit.com/tools/http-status-checker/):
**1\. Google Search Console**:
**Purpose**: Google Search Console offers a comprehensive view of how Googlebot is interacting with your site. It provides detailed reports on crawl errors, server issues, and HTTP status codes. Using this tool, you can easily identify 404 errors, server unresponsiveness, or any issues preventing Google from indexing your pages.
**How it helps**: Google Search Console will alert you to pages that have issues, such as â404 Not Foundâ errors or â500 Internal Server Errors.â You can use this information to resolve problems that may hinder your siteâs search engine rankings.
**2\. Screaming Frog SEO Spider**:
**Purpose**: Screaming Frog is a powerful desktop tool that crawls your website, similar to how a search engine bot would. It provides a comprehensive analysis of all the HTTP status codes on your website, including 404 errors, redirects, and other issues.
**How it helps**: It not only checks for broken links but also helps you analyze the serverâs response for each URL, allowing you to find and fix server-side issues. You can also export the results into various formats for detailed reporting.
**3\. GTMetrix**:
**Purpose**: GTMetrix is a performance analysis tool that provides insights into your websiteâs loading times, including detailed HTTP status codes and server performance. It offers a comprehensive report on various elements of page speed and response times.
**How it helps**: It gives you an understanding of how your server responds to requests. This is helpful for detecting HTTP errors such as slow server responses, redirects, or server misconfigurations that affect performance. It also provides suggestions for improving your websiteâs speed and server response time.
**4\. Pingdom**:
**Purpose**: Pingdom is a popular website monitoring tool that helps you check your siteâs uptime, performance, and server response. It offers HTTP status code checks along with a detailed performance report from multiple locations worldwide.
**How it helps**: Pingdom allows you to monitor the HTTP status codes returned by your website from different parts of the world, ensuring that users from various locations are experiencing optimal load times and server responses. It can also send you alerts if certain pages return errors or slow down.
**5\. Curl**:
**Purpose**: Curl is a command-line tool that allows you to manually check the HTTP status codes for any website. By entering a URL, you can directly interact with the server and analyze the response.
**How it helps**: Curl is useful for developers or users with technical knowledge who need to check the response from a server for debugging or troubleshooting. By adding flags (e.g., \-I to get header information), you can get detailed server responses, including HTTP status codes, headers, and more.
**6\. Ahrefs**:
Purpose: Ahrefs is a comprehensive SEO toolset that provides detailed audits of your website, including a breakdown of HTTP status codes for each page. It helps you monitor broken links, redirect chains, and other server-side issues that could impact SEO.
How it helps: Ahrefs crawls your entire website, identifies HTTP errors such as 404s or 500s, and generates reports. It can also identify other SEO-related issues, such as slow-loading pages or poor server responses, which can negatively impact your siteâs ranking.
These tools are essential for diagnosing server issues, ensuring a smooth user experience, and maintaining good SEO practices.
Now that you are familiar with the most common HTTP errors, you should have a good basis for troubleshooting issues with your web servers or applications. If you come across any error codes that were not mentioned above, feel free to discuss them in the comments section.
## **FAQs about HTTP Status Codes**
### **What are HTTP Status Codes?**
HTTP status codes are three-digit numbers used in the HTTP protocol to indicate the outcome of a clientâs request to a web server. They help communicate whether the request was successful, encountered an error, or requires further action. Understanding these HTTP protocol status codes is essential for diagnosing website issues and ensuring smooth user experiences.
### **Why are HTTP Status Codes Important?**
HTTP status codes play a crucial role in helping search engines and browsers understand the state of a webpage. These HTTP response codes assist in diagnosing website issues, ensuring proper indexing, and improving user experience. By identifying errors like broken links or redirects, they help maintain website performance and SEO effectiveness.
### **What is the Difference Between 2xx and 3xx Status Codes?**
2xx codes represent successful requests, while 3xx codes indicate redirects. 2xx confirms the server processed the request, and 3xx informs the client that the resource has been moved or redirected.
### **How Do I Fix a 403 Forbidden Error?**
A 403 Forbidden error occurs when a server blocks access to a resource due to insufficient permissions. To fix this, check and adjust file or directory permissions, update your .htaccess file, or modify security settings. If the issue persists, contact your hosting provider for assistance. Understanding web server status codes like 403 helps diagnose and resolve such access issues effectively.
### **How Can I Check HTTP Status Codes for My Website?**
You can check web page status codes using various methods, including browser developer tools, online status checkers, and website crawlers. Tools like Screaming Frog, Google Search Console, and third-party HTTP header checkers help identify status codes, allowing you to diagnose errors and ensure smooth website performance.

## Popular Searches
[SEO Services](https://www.infidigit.com/seo-search-engine-optimization/)
[Website SEO Audit Packages](https://www.infidigit.com/seo-audit-pricing-p1/)
[WordPress Development](https://www.infidigit.com/wordpress-development-services/)
[Website Structure](https://www.infidigit.com/blog/website-structure/)
[E-commerce SEO Services](https://www.infidigit.com/e-commerce-seo/)
[SEO For Ecommerce](https://www.infidigit.com/industries/seo-for-ecommerce/)
[SEO Packages](https://www.infidigit.com/seo-pricing-p1/)
[Types of SEO](https://www.infidigit.com/blog/types-of-seo/)
[SEO Audit Services](https://www.infidigit.com/seo-audit/)
[SEO for Education](https://www.infidigit.com/industries/seo-for-educational/)
[Top YouTube Searches](https://www.infidigit.com/blog/top-youtube-searches/)
[Googlebots IP Addresses](https://www.infidigit.com/blog/google-update-googlebots-ip-addresses/)
[SEO Services in Mumbai](https://www.infidigit.com/location/india-mumbai-seo/)
[SEO for Insurance](https://www.infidigit.com/industries/seo-for-insurance/)
[List of Search Engines](https://www.infidigit.com/blog/list-of-search-engines/)
[YouTube SEO Tools](https://www.infidigit.com/blog/youtube-seo-tools/)
[Link Building Services](https://www.infidigit.com/link-building/)
[SEO for OTT Platforms](https://www.infidigit.com/industries/seo-for-ott/)
[Top YT Cooking Channels](https://www.infidigit.com/blog/top-youtube-cooking-channels/)
[308 Permanent Redirect](https://www.infidigit.com/blog/308-permanent-redirect/)
[SEO Services in Bangalore](https://www.infidigit.com/location/india-bangalore-seo/)
[WordPress SEO Services](https://www.infidigit.com/wordpress-seo-services/)
[What is a Blog](https://www.infidigit.com/blog/what-is-a-blog/)
[Import XML Formula](https://www.infidigit.com/blog/import-xml-formula)
How useful was this post?
Submit Rating
3\.4 / 5. 14
### 2 thoughts on âHTTP Status Codes: List of HTTP Response Status Codesâ
1. 
**Adrian Garbow**
[August 16, 2020 at 11:28 pm](https://www.infidigit.com/blog/http-status-codes/#comment-1267)
Just learning about HTTP codesâŚ
[Reply](https://www.infidigit.com/blog/http-status-codes/#comment-1267)
1. 

**[Infidigit](https://www.infidigit.com/)**
[August 17, 2020 at 8:21 am](https://www.infidigit.com/blog/http-status-codes/#comment-1270)
Thanks. Read our latest posts for more updates.
[Reply](https://www.infidigit.com/blog/http-status-codes/#comment-1270)
### Leave a Comment [Cancel Reply](https://www.infidigit.com/blog/http-status-codes/#respond)
## People are also reading
[](https://www.infidigit.com/blog/importance-of-https-in-seo/)
- [HTTP Status Code](https://www.infidigit.com/blog/category/http-status-code/)[SEO Basics](https://www.infidigit.com/blog/category/seo-basics/)
##### [The Importance of HTTPS in SEO](https://www.infidigit.com/blog/importance-of-https-in-seo/)
- 5 min read
- Jun 30, 2025
- [Sagar Waykar](https://www.infidigit.com/blog/author/sagar-waykar/)
[](https://www.infidigit.com/blog/404-and-soft-404-errors/)
- [HTTP Status Code](https://www.infidigit.com/blog/category/http-status-code/)[Technical SEO](https://www.infidigit.com/blog/category/technical-seo/)
##### [404 vs Soft 404 Errors: What Are They, Differences, & How to Fix Them](https://www.infidigit.com/blog/404-and-soft-404-errors/)
- 5 min read
- Aug 13, 2020
- [Monal Panchal](https://www.infidigit.com/blog/author/monalpanchal/)
[](https://www.infidigit.com/blog/http-to-https-migration/)
- [HTTP Status Code](https://www.infidigit.com/blog/category/http-status-code/)[Technical SEO](https://www.infidigit.com/blog/category/technical-seo/)
##### [HTTP to HTTPS Migration](https://www.infidigit.com/blog/http-to-https-migration/)
- 3 min read
- Aug 10, 2020
- [Roshni Dubey](https://www.infidigit.com/blog/author/roshnidubey/)
[](https://www.infidigit.com/blog/mixed-content/)
- [Advanced SEO](https://www.infidigit.com/blog/category/advanced-seo/)[HTTP Status Code](https://www.infidigit.com/blog/category/http-status-code/)[SEO Basics](https://www.infidigit.com/blog/category/seo-basics/)[Technical SEO](https://www.infidigit.com/blog/category/technical-seo/)
##### [How to solve Mixed Content Issue on your website](https://www.infidigit.com/blog/mixed-content/)
- 5 min read
- May 18, 2020
- [Robin Fernandes](https://www.infidigit.com/blog/author/robin-fernandes/)
## Our Solutions
[](https://www.infidigit.com/seo-audit/)
### [Website Audit](https://www.infidigit.com/seo-audit/)
[Get your website audited through 400+ checkpoints](https://www.infidigit.com/seo-audit/)
[](https://www.infidigit.com/e-commerce-seo/)
### [Ecommerce SEO](https://www.infidigit.com/e-commerce-seo/)
[Increase your product visibility to high intent searchers](https://www.infidigit.com/e-commerce-seo/)
[](https://www.infidigit.com/enterprise-seo-services/)
### [Enterprise SEO](https://www.infidigit.com/enterprise-seo-services/)
[Increase organic reach and revenue for large-scale business](https://www.infidigit.com/enterprise-seo-services/)
[](https://www.infidigit.com/local-seo/)
### [Local SEO](https://www.infidigit.com/local-seo/)
[Get found on ânear meâ search results and optimise your GMB profile](https://www.infidigit.com/local-seo/)
[](https://www.infidigit.com/aso-app-store-optimization/)
### [App Store Optimization](https://www.infidigit.com/aso-app-store-optimization/)
[Increase your mobile app installations on App store & Play Store](https://www.infidigit.com/aso-app-store-optimization/)
[](https://www.infidigit.com/conversion-rate-optimization/)
### [Conversion Rate Optimization](https://www.infidigit.com/conversion-rate-optimization/)
[Increase clicks to conversions rate ratio by bringing relevant traffic to your website](https://www.infidigit.com/conversion-rate-optimization/)
[](https://www.infidigit.com/seo-search-engine-optimization/)
### [SEO](https://www.infidigit.com/seo-search-engine-optimization/)
[Rank on google search engine results page organically and outperform your competitors](https://www.infidigit.com/seo-search-engine-optimization/)
[](https://www.infidigit.com/seo-penalty-recovery/)
### [Penalty Recovery](https://www.infidigit.com/seo-penalty-recovery/)
[Regain your traffic, index coverage, or SERP appearance after your website gets a penalty](https://www.infidigit.com/seo-penalty-recovery/)
[](https://www.infidigit.com/content-writing-services/)
### [Content Writing](https://www.infidigit.com/content-writing-services/)
[Engage your audience with compelling content created to rank on search as well as convert users](https://www.infidigit.com/content-writing-services/)
## Free SEO Tools
[Keyword Rank Checker](https://www.infidigit.com/tools/rank-checker/)
[Free Keyword Research Tool](https://www.infidigit.com/tools/keyword-generator/)
[Rank Tracker](https://www.infidigit.com/tools/rank-tracker/)
[Domain Age Checker](https://www.infidigit.com/tools/domain-age-checker/)
[Website Link Counter](https://www.infidigit.com/tools/website-links-counter/)
[CPC Calculator](https://www.infidigit.com/tools/cpc-calculator/)
[CTR Calculcator](https://www.infidigit.com/tools/ctr-calculator/)
[HTTP Status Checker](https://www.infidigit.com/tools/http-status-checker/)
[Word Counter](https://www.infidigit.com/tools/word-counter/)
[Conversion Rate Calculator](https://www.infidigit.com/tools/conversion-rate-calculator/)
[CPM Calculator](https://www.infidigit.com/tools/cpm-calculator/)
[Seo Extension](https://www.infidigit.com/tools/seo-extension/)
[Keyword Density Checker](https://www.infidigit.com/tools/keyword-density-checker/)
[ROAS Calculator](https://www.infidigit.com/tools/roas-calculator/)
[Product Schema Generator](https://www.infidigit.com/tools/product-schema-generator/)
[CPA Calculator](https://www.infidigit.com/tools/cpa-calculator/)
[Person Schema Generator](https://www.infidigit.com/tools/person-schema-generator/)
[FAQ Schema Generator](https://www.infidigit.com/tools/faq-schema-generator/)
[Article Schema Generator](https://www.infidigit.com/tools/article-schema-generator/)
[Breadcrumb Schema Generator](https://www.infidigit.com/tools/breadcrumb-schema-generator/)
## Think Your SEO Is On Track?
Find Out with Infigrowthâs Free 7-day Trial.
[Start Now](https://www.infigrowth.com/?utm_source=infidigit-website&utm_medium=blog-cta-sticky-mobile&utm_campaign=mar-25)

Ready to Scale Smarter?
[Get your Free Proposal](https://www.infidigit.com/get-demo/)
Navigate
- [Clients](https://www.infidigit.com/clients/)
- [Testimonials](https://www.infidigit.com/testimonials/)
- [Case Study](https://www.infidigit.com/case-study/)
- [Industries](https://www.infidigit.com/industries/)
- [Jobs HIRING](https://www.infidigit.com/careers/)
- [Blogs](https://www.infidigit.com/blog/)
- [News](https://www.infidigit.com/news/)
Solutions
- [SEO Services](https://www.infidigit.com/seo-search-engine-optimization/)
- [Ecommerce SEO Services](https://www.infidigit.com/e-commerce-seo/)
- [SEO Audit Services](https://www.infidigit.com/seo-audit/)
- [CRO Services](https://www.infidigit.com/conversion-rate-optimization/)
- [Local SEO Services](https://www.infidigit.com/local-seo/)
- [ASO Services](https://www.infidigit.com/aso-app-store-optimization/)
- [Penalty Recovery Services](https://www.infidigit.com/seo-penalty-recovery/)
Contact
[](https://infidigit.us/)
[**USA**](https://infidigit.us/) 8, The Green STE, R Dover,
DE 19901.
[\+1 (302) 608-9009](<tel:+1 (302) 608-9009>)
[ **INDIA** Topiwala Centre, 509 & 510, SV Road, Goregaon West, Mumbai, Maharashtra, 400104.](https://www.infidigit.com/contact-us/)
Industries
- [SEO For Ecommerce](https://www.infidigit.com/industries/seo-for-ecommerce/)
- [SEO For Automotive](https://www.infidigit.com/industries/seo-for-automotive/)
- [SEO For Cannabis](https://www.infidigit.com/industries/seo-for-cannabis/)
- [SEO For B2B](https://www.infidigit.com/industries/seo-for-b2b/)
- [SEO For Travel Website](https://www.infidigit.com/industries/seo-for-travel-website/)
- [SEO For Fitness](https://www.infidigit.com/industries/seo-for-fitness/)
- [SEO For Fashion Ecommerce](https://www.infidigit.com/industries/seo-for-fashion-ecommerce/)
Follow
- [LinkedIn](https://in.linkedin.com/company/infidigit)
- [YouTube](https://www.youtube.com/channel/UCGVKzNjYLJanK_WkyoeYpjQ)
- [Facebook](https://www.facebook.com/infidigitconsultants/)
- [X](https://twitter.com/InfidigitIndia?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor)
- [Instagram](https://www.instagram.com/infidigit/)
- [Threads](https://www.threads.net/@infidigit)
View All Solutions
SEO Company in India
- [SEO Services in India](https://www.infidigit.com/location/india-seo-services/)
- [SEO Company in Mumbai](https://www.infidigit.com/location/india-mumbai-seo/)
- [SEO Company in Delhi](https://www.infidigit.com/location/india-delhi-seo/)
- [SEO Company in Bangalore](https://www.infidigit.com/location/india-bangalore-seo/)
- [SEO Company in Ahmedabad](https://www.infidigit.com/location/india-ahmedabad-seo/)
- [SEO Company in Kolkata](https://www.infidigit.com/location/india-kolkata-seo/)
- [SEO Company in Pune](https://www.infidigit.com/location/india-pune-seo/)
- [SEO Company in Hyderabad](https://www.infidigit.com/location/india-hyderabad-seo/)
- [SEO Company in Chennai](https://www.infidigit.com/location/india-chennai-seo/)
- [SEO Company in Jaipur](https://www.infidigit.com/location/india-jaipur-seo/)
- [SEO Company in Chandigarh](https://www.infidigit.com/location/india-chandigarh-seo/)
- [SEO Company in Surat](https://www.infidigit.com/location/india-surat-seo/)
- [SEO Company in Noida](https://www.infidigit.com/location/india-noida-seo/)
- [SEO Company in Gurgaon](https://www.infidigit.com/location/india-gurgaon-seo/)
- [SEO Company in Mohali](https://www.infidigit.com/location/india-mohali-seo/)
- [SEO Company in Coimbatore](https://www.infidigit.com/location/india-coimbatore-seo/)







[](https://www.semrush.com/agencies/infidigit-seo-agency/)

- [Disclaimer](https://www.infidigit.com/disclaimer/)
- [Privacy Policy](https://www.infidigit.com/privacy-policy/)
- [Contact Us](https://www.infidigit.com/contact-us/)
- [Sitemap](https://www.infidigit.com/sitemap/)
Š 2026 Infidigit
This website uses cookies to ensure you get the best experience on our website.
.
[Cookie Settings]()[Reject All]()[Accept]()
Manage consent
Close
#### Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
[Necessary]()
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| viewed\_cookie\_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
[SAVE & ACCEPT]()
## Share this article

## HTTP Status Codes: List of HTTP Response Status Codes |
| Readable Markdown | 3\.4
(14)
Every time you browse the internet, thereâs a silent exchange of messages between your browser and the server hosting the website. These messages, known as HTTP status codes, are crucial in ensuring smooth communication. Whether youâre accessing a webpage, encountering an error, or being redirected, these codes tell you exactly whatâs going on behind the scenes.
HTTP status codes help determine whether the page is accessible, what went wrong, and what action you need to take. Understanding these codes is essential for anyone managing websites, troubleshooting online issues, or looking to improve their websiteâs performance. In this article, we will explain HTTP status codes in detail and provide a comprehensive list to help you understand their meanings and implications better.
## **What are HTTP status codes?**
In simple terms, **HTTP status codes** are messages that a server sends to a browser to indicate the result of a request. When you type a website address into your browser, it sends a request to the server. In return, the server sends back a three-digit HTTP status code, indicating whether the request was successful or if there was an issue.
These codes act as a form of communication between browsers and servers. Think of them as âsignalsâ that tell browsers how to handle the requested page.
Understanding HTTP status codes is not just for technical people. If you manage a website, knowing these codes is crucial for identifying errors, reducing website downtime, and ensuring a smooth user experienceâall of which contribute to improving **search engine rankings**.
John Mueller explained that HTTP status codes are the first thing Google checks when crawling the content.
He was posed with the question:
âWondering if Google checks status codes before anything else, like before rendering content?â
In response, Mueller confirmed that Google does check the status codes before rendering or indexing content. Google checks for a â200â status code before proceeding with crawling any further. A 200 status code indicates to Google that it is crawling a valid page and there might be content worth indexing on it. Here is the video on different errors that Google may find & report while crawling your website

## **Why do HTTP Status Codes Matter for SEO?**
You may not always see HTTP status codes when browsing a webpage, but they are incredibly important behind the scenes. If a webpage is unavailable, for example, the browser will receive an HTTP status code showing the issue, such as a server error or a missing page.
These codes impact **Search Engine Optimization (SEO)** significantly. Search engines like Google rely on HTTP status codes to detect errors, crawlability issues, and even reduce website downtime. When Google crawls a website, it first checks the HTTP status code before anything else.
For instance, a **200 OK** status code signals to Google that the page is valid, functional, and ready to be indexed. Pages that return this code are considered **crawlable** and **indexable**, which is essential for **ranking** in search engines. If a page returns a **404** or **500** status code, it can negatively affect your SEO.
John Mueller, a Google Search Advocate, explained that Google checks these codes before proceeding to crawl and index the content. If Google encounters a **200 status code**, it indicates that the page is healthy, and the content may be worth indexing. You can watch his video on the **errors that Google might find and report** while crawling your website.
## **List of HTTP Status Codes**
HTTP status codes are divided into five groups based on their first digit. Each group signifies a different type of response from the server.
- 1xx HTTP status codes group (Informational): These codes tell you that the server has received and is processing your request.
- 2xx HTTP status codes group (Success): These codes mean your request was successful.
- 3xx HTTP status codes group (Redirection): These codes tell you that further action is needed to complete the request (usually a redirect to a new URL).
- 4xx HTTP status codes group (Client Error): These codes indicate that there was an issue with the request you sent.
- 5xx HTTP status codes group â (Server Error): These codes mean thereâs a problem on the server side.
Hereâs an interesting and detailed image that will help you understand the different types of HTTP response codes you might encounter when accessing a webpage.

## **List of HTTP Status Codes and What They Mean**
HTTP status codes are categorized into five main groups, each representing a different type of response from the server. Below is a breakdown of each group and what the various status codes within them signify.
### **1xx HTTP response status codes group**
#### **100 Status Code: Continue**
The 100 Continue status code means that the server has received the initial part of the request and is ready to continue processing. Itâs often used when the client is sending large amounts of data, allowing the server to confirm that itâs prepared to handle the entire request before the data is fully transmitted.
**Example:** This might occur when submitting large files in a POST request.
#### **101 Status Code: Switching Protocol**
The 101 Switching Protocols status code indicates that the client requested a protocol change (e.g., upgrading from HTTP to HTTPS or switching to WebSocket) and the server agrees. This ensures that communication between the client and server can occur using a more secure or appropriate protocol.
**Example:** Upgrading from HTTP to HTTPS for security purposes.
#### **102 Status Code: Processing**
This code signals that the server has received the request, but itâs still being processed. This is common for long-running tasks that take time to complete. It tells the client to wait while the server processes the request.
**Example:** Used when executing large database queries or processing complex operations.
#### **103 Status Code: Early Hints**
The 103 Early Hints status code tells the client about preloaded resources (such as images, scripts, or CSS files) before the full response is ready. This allows the browser to start loading resources early, improving page load times.
**Example:** Preloading resources for faster rendering while waiting for the final response.
### **2xx HTTP response status codes group**
These codes indicate that the request was successfully received, understood, and processed by the server.
#### **201 Status Code: Created**
A 201 status code indicates that a new resource has been successfully created as a result of the clientâs request. Itâs commonly used for POST requests, such as creating a new user or submitting a form.
**Example:** After submitting a form to create a new blog post, you may see this status code.
#### **202 Status Code: Accepted**
The 202 Accepted status code means the server has received and accepted the request, but the process is not yet complete. Itâs useful for asynchronous tasks that take time to finish.
**Example:** A background task for processing an order might return this code, indicating that the order is in progress but not yet finalized.
#### **203 Status Code: Non-Authoritative Information**
The 203 status code is returned when the server successfully processes the request, but the response is based on third-party information, not the origin server.
**Example:** When fetching data from a cache instead of the original server.
#### **204 Status Code: No Content**
A 204 No Content status code tells the client that the server has successfully processed the request, but there is no content to send in the response body. This often happens after a successful action, such as form submission.
**Example:** After submitting a contact form where no additional data needs to be returned.
#### **205 Status Code: Reset Content**
The 205 Reset Content status code instructs the client to reset the documentâs state. Itâs typically used in forms to clear the form fields after submission.
**Example:** After submitting a form with errors, the server might send a 205 response to reset the form fields.
#### **206 Status Code: Partial Content**
The 206 Partial Content status code indicates that the server is returning part of the requested resource. This is often used for large files that are downloaded in chunks.
**Example:** Downloading a large video file in multiple parts.
#### **207 Status Code: Multi-Status**
This code indicates that the server has returned information from multiple resources in a single response, typically used in batch processing operations.
**Example:** A single request that modifies multiple resources, such as adding new records to a database.
#### **208 Status Code: Already Reported**
This code is used to avoid redundant reporting when the same resource has been listed previously. It helps improve efficiency, especially in collaboration environments.
**Example:** In a collaborative environment, when multiple users edit the same file, this status code prevents redundant enumeration.
#### **226 Status Code: IM Used**
The 226 IM Used status code indicates that the server has fulfilled the request and applied some modifications to the resource during the process, such as applying an Instance Manipulation (IM) operation.
**Example:** Applying image optimization during an HTTP GET request.
### **3xx HTTP response status codes group**
The 3xx range of HTTP status codes is used for redirection. These codes indicate that the client must take additional actions to complete the request.
#### **300 Status Code: Multiple Choice**
The 300 Multiple Choices status code indicates that the server has multiple options for the requested resource, but it does not specify which one to choose. The client may have several ways to access the same resource, such as different formats or languages. The server leaves the decision to the client or user.
**Example:** Imagine visiting a website that supports both English and Spanish versions. When you request the resource, the server responds with a 300 Multiple Choices status code, listing the available language versions. The user can then select which version to view.
#### **301 Status Code: Permanent Redirection**
The 301 Moved Permanently status code indicates that the requested resource has been permanently moved to a new URL. Both browsers and search engines will now use the new location for future requests. This code is important for maintaining SEO integrity, as search engines update their indexes to reflect the new URL, ensuring that search rankings are preserved.
**Example:** If a website undergoes a major restructuring and a pageâs URL changes permanently, the server responds with a 301 status code, ensuring that any links or search engine results pointing to the old URL will redirect to the new one.
**SEO Tip:** When using a 301 redirect, itâs important to implement it properly to avoid 404 errors and ensure your SEO rankings are preserved.
Here is what Googleâs John Mueller has to say on how long it will take to rank a new URL after doing a 301 redirect to the old URL:

#### **302 Status Code: Temporary Redirection**
The 302 Found status code (formerly called âMoved Temporarilyâ) tells the client that the requested resource has temporarily moved to a different URL. Unlike the 301 status code, this change is not permanent, and future requests should use the original URL.
**Example:** A webpage might be temporarily moved during maintenance or for special events. For instance, if an e-commerce site has a special sale on a subdomain, a 302 redirect can be used to direct users to a temporary location.
#### **303 Status Code: See Other**
The 303 See Other status code tells the client to retrieve the requested resource from a different URL using a GET request. This is commonly used after a POST request to indicate that the response is available at another location and that a GET request should be used to fetch it.
**Example:** After submitting an online form (POST), the server might return a 303 status code to inform the client that the result of the submission is available at another URL via a GET request.
#### **304 Status Code: Not Modified**
The 304 Not Modified status code indicates that the requested resource has not changed since the last time it was requested. The client can continue using the cached version of the resource, saving bandwidth and reducing load times.
**Example:** A user revisits a website and their browser sends a request for a resource. The server checks the last modification date of the resource and, if it hasnât changed, returns a 304 status code to inform the browser to use the cached version.
#### **305 Status Code: Use Proxy (Deprecated in HTTP/1.1)**
The 305 Use Proxy status code was used to indicate that the client must access the requested resource through a specified proxy. However, this status code was deprecated in HTTP/1.1 and is no longer used in modern web development. Other codes, such as 407 (Proxy Authentication Required), are used in its place.
#### **307 Status Code: Temporary Redirect**
The 307 Temporary Redirect status code indicates that the resource has temporarily moved to a new URL. Unlike a 302 redirect, the 307 code specifies that the HTTP method used for the request (e.g., POST or GET) should remain unchanged when following the redirect.
**Example:** If an API endpoint temporarily moves but the server doesnât want to change the request method, it will return a 307 status code to ensure that the client uses the same HTTP method to fetch the resource from the new location.
#### **308 Status Code: Permanent Redirect**
The 308 Permanent Redirect status code is similar to the 301 code, but it ensures that the HTTP method used in the original request is preserved when redirected to the new URL.
**Example:** A REST API endpoint that permanently moves to a new URL and wants to ensure that POST requests are also forwarded as POST requests would return a 308 status code.
### **4xx HTTP response status codes group**
The 4xx range is reserved for client-side errors. These errors usually occur when there is an issue with the request sent to the server.
#### **400 Status Code: Bad Request**
The 400 Bad Request status code indicates that the server could not understand the request due to malformed syntax. This typically happens due to issues like missing parameters, incorrect formatting, or invalid query syntax.
**Example:** If a user sends a request with an invalid URL (like a malformed query string), the server will respond with a 400 error, prompting the user to correct the issue.
#### **401 Status Code: Unauthorized Error**
The 401 Unauthorized status code is returned when the client must authenticate before accessing the requested resource. This error occurs when the request is missing valid authentication credentials, or the credentials provided are not sufficient.
**Example:** When attempting to access a secure page on a website that requires login credentials, the server will return a 401 status code if the user hasnât logged in or provided invalid credentials.
#### **402 Status Code: Payment Required**
The 402 Payment Required status code was originally intended to indicate that the client needs to pay for access to the resource. However, it is not widely used and is reserved for future use.
#### **403 Status Code: Forbidden Error**
The 403 Forbidden status code indicates that the server understands the request, but refuses to authorize it. This could be because the user doesnât have the necessary permissions or access rights to the resource.
**Example:** If a user tries to access a protected page (like an admin dashboard) without the correct permissions, the server will return a 403 status code.
#### **404 Status Code: Page Not Found**
The 404 Not Found status code occurs when the requested resource cannot be found on the server. This is one of the most common errors encountered on the web, usually indicating that the URL was typed incorrectly, or the page was removed.
**Example:** If a user tries to access a non-existent page, such as example.com/about-us, theyâll see a 404 error because the page does not exist.
SEO Tip: Properly handling 404 errors can help improve user experience and SEO. Itâs advisable to create a custom 404 page and manage broken links to maintain the siteâs SEO ranking.

#### **405 Status Code: Method Not Allowed**
The 405 Method Not Allowed status code occurs when the client sends a request using an HTTP method that the resource does not support. For example, trying to submit a form with a GET request instead of POST will trigger this error.
**Example:** If a form is designed to be submitted via POST but a user tries to access it via a GET request, the server will respond with a 405 error.
#### **406 Status Code: Not Acceptable**
The 406 Not Acceptable status code is returned when the server is unable to provide a version of the resource that meets the clientâs preferences, such as language or media type. This happens when the server canât match the content with what the client accepts.
**Example:** If a client requests a page in French but the server only has the page available in English, it might return a 406 error.
#### **407 Status Code: Proxy Authentication Required**
The 407 Proxy Authentication Required status code is similar to the 401 Unauthorized error, but it indicates that the client must authenticate with a proxy server before the request can proceed.
**Example:** A client behind a corporate firewall or proxy server might see this error if the server requires authentication to pass the request through the proxy.
#### **408 Status Code: Request Timeout**
The â408 Request Timeoutâ status code is returned when the clientâs request took too long to complete, and the server decides to close the connection. This typically happens when the client does not send a request or complete a request within a certain time frame. Servers use this to prevent idle connections from consuming server resources. In many cases, a timeout might occur if the client is uploading a large file and it takes longer than expected to complete the operation.
**Example:** If youâre trying to upload a 10MB file over a slow connection and it takes too long, the server may close the connection and return a 408 error, asking you to resend the request.
#### **409 Status Code: Conflict**
The â409 Conflictâ error occurs when a request cannot be completed because it conflicts with the current state of the server or resource. This can happen when the client is attempting an operation that cannot be performed due to conflicting information. The conflict may be due to data changes made by another client or system.
**Example:** If two users try to update the same database record at the same time, the second update attempt might trigger a 409 error, indicating a conflict with the data.
#### **410 Status Code: Gone**
The â410 Goneâ status code indicates that the requested resource has been permanently removed from the server and is no longer available, with no forwarding address. Unlike a â404 Not Foundâ error, which could mean that the resource is temporarily unavailable, a 410 error means the resource has been intentionally and permanently deleted. This helps inform users and search engines that the resource will not return.
**Example:** If an online store deletes a product page permanently and does not redirect it elsewhere, users trying to access that page will receive a 410 error.
#### **411 Status Code: Length Required**
A â411 Length Requiredâ error is returned when the server expects the client to include a Content-Length header in the request but it is missing. This header specifies the size of the request body in bytes. If the client fails to provide this information, the server cannot process the request properly and rejects it with a 411 error.
**Example:** When submitting a POST request with data (e.g., form data or JSON), the client needs to specify how much data is being sent by including the Content-Length header. If omitted, the server responds with a 411 status.
#### **412 Status Code: Precondition Failed**
The â412 Precondition Failedâ status code indicates that one or more conditions provided by the client in the request headers could not be satisfied by the server. These conditions are often specified using the If-Match, If-None-Match, If-Modified-Since, or If-Unmodified-Since headers. If the condition is not met, the server will return this error.
**Example:** If a client sends a request to update a resource with an If-Match header that contains an outdated version of the resource, the server will return a 412 error, indicating the precondition has failed.
#### **413 Status Code: Payload Too Large**
The â413 Payload Too Largeâ status code occurs when the request is too large for the server to process. This is typically seen when the client is sending a request with a body that exceeds the maximum allowed size configured on the server. Servers often limit the size of the data they can handle to prevent abuse or resource exhaustion.
**Example:** Uploading a file that exceeds the serverâs size limit (e.g., attempting to upload a 100MB file to a server that allows a maximum of 10MB) would result in a 413 error.
#### **414 Status Code: URL Too Long**
The â414 URI Too Longâ status code is returned when the URL of the request exceeds the maximum length the server can process. URLs are subject to length limitations, and if the client sends a request with an excessively long URL, the server will reject it. This error often arises when the URL contains a large number of query parameters or data.
**Example:** A search URL with many parameters or a URL that encodes large amounts of data could exceed the serverâs length restrictions, triggering a 414 error.
#### **415 Status Code: Unsupported Media Type**
The â415 Unsupported Media Typeâ error indicates that the server cannot process the request because the media type (e.g., content type) is not supported. The clientâs request is typically accompanied by a Content-Type header, which specifies the format of the data being sent (e.g., application/json, text/html). If the server doesnât support the specified format, it will return a 415 status code.
**Example:** If you try to upload an image in a format like .webp to a server that only accepts .jpg or .png, the server would return a 415 error due to unsupported media.
#### **416 Status Code: Range Not Satisfiable**
The â416 Range Not Satisfiableâ status code occurs when the Range header sent in the request specifies a range of bytes that is outside the bounds of the file or resource. If the client requests a range that exceeds the file size or is invalid, the server returns this error to indicate it cannot fulfill the request.
**Example:** If a client requests the first 1000 bytes of a file, but the file is only 500 bytes long, the server will return a 416 error because the requested range cannot be satisfied.
#### **417 Status Code: Expectation Failed**
The â417 Expectation Failedâ status code is returned when the server cannot meet the expectations specified by the client in the Expect header. The Expect header allows the client to set certain expectations (e.g., Expect: 100-continue), and if the server is unable to fulfill these expectations, it will return a 417 error.
**Example:** If the client sends a Expect: 100-continue header but the server cannot process the request due to internal issues, it will respond with a 417 error.
#### **418 Status Code: Iâm a teapot**
The â418 Iâm a Teapotâ status code is part of an April Foolsâ joke in the âHyper Text Coffee Pot Control Protocolâ (HTCPCP). It humorously indicates that a teapot cannot brew coffee. While not meant for real-world usage, this status code has become a well-known part of internet culture.
**Example:** Sending a request to a server that supports HTCPCP to brew coffee with a teapot would return a 418 status code.
#### **421 Status Code: Misdirected Request**
The â421 Misdirected Requestâ status code is returned when a request is sent to the wrong server, and the server cannot process it because it is not configured to handle the request. This typically occurs in environments with multiple servers that serve different purposes.
**Example:** If a client sends a request to the wrong server in a load-balanced environment, the server will return a 421 error.
#### **422 Status Code: Unprocessable Entity**
The â422 Unprocessable Entityâ status code is returned when the server understands the content of the request but cannot process it due to semantic errors. This often occurs when data in the request is valid in structure but fails validation rules (e.g., missing required fields or incorrect data format).
**Example:** Submitting a form with incomplete or invalid data (e.g., a date in the wrong format) could result in a 422 error.
#### **423 Status Code: Locked**
The â423 Lockedâ status code indicates that the requested resource is locked and cannot be accessed or modified at the moment. This often occurs when a resource is being edited or is in use by another process.
**Example:** If a user is editing a document and another user tries to access it, the server may return a 423 error indicating that the document is locked.
#### **424 Status Code: Failed Dependency**
The â424 Failed Dependencyâ status code is used when a request fails due to the failure of a preceding request that it depends on. This is often seen in WebDAV or similar protocols where the successful execution of one request depends on the success of another.
**Example:** If a DELETE request fails, a subsequent request that depends on the deleted resource will return a 424 error.
#### **425 Status Code: Too Early**
The â425 Too Earlyâ status code is used to indicate that the server is not ready to process a request because it was received too early. This can help prevent issues like replay attacks or race conditions that could arise if the request is processed prematurely.
**Example:** A client trying to process a request too soon after a previous request, potentially causing unintended consequences, would result in a 425 error.
#### **426 Status Code: Upgrade Required**
The â426 Upgrade Requiredâ status code indicates that the client must upgrade to a different protocol to access the requested resource. This could be to a newer version of HTTP or another protocol entirely (e.g., switching from HTTP/1.1 to HTTP/2).
**Example:** If a server requires HTTP/2 for certain operations, but the client is using HTTP/1.1, the server will return a 426 error.
#### **428 Status Code: Precondition Required**
The â428 Precondition Requiredâ status code indicates that the server requires certain conditions to be met before processing the request. This is typically used in scenarios where operations should only be performed if specific preconditions are met (e.g., ensuring a resource hasnât changed).
**Example:** Before updating a document, the client may need to ensure that the document has not been modified since the last request by including an If-Match header. If this condition is not met, a 428 error is returned.
#### **429 Status Code: Too Many Requests**
The â429 Too Many Requestsâ status code is returned when the client has sent too many requests in a given time period and is being rate-limited. This is often used to prevent abuse or excessive load on the server.
**Example:** If you hit an API rate limit by sending too many requests in a short time, the server will return a 429 error, and you may also receive a Retry-After header with a time when you can retry the request.
#### **431 Status Code: Request Header Fields Too Large**
The â431 Request Header Fields Too Largeâ status code is returned when the requestâs header fields (e.g., cookies or HTTP headers) exceed the serverâs size limits.
**Example:** If a client sends a request with very large cookies or headers, causing the server to exceed its size limit for headers, a 431 error will be returned.
#### **451 Status Code: Unavailable For Legal Reasons**
The â451 Unavailable For Legal Reasonsâ status code indicates that the requested resource cannot be accessed due to legal restrictions. This may occur if the content is blocked in certain jurisdictions due to censorship, legal disputes, or government regulations.
**Example:** A streaming service might block access to a movie in certain countries due to legal issues, returning a 451 error when users attempt to access it from those locations.
### **5xx HTTP response status codes group**
#### **500 Status Code: Internal Server Error**
The â500 Internal Server Errorâ indicates that the server encountered an unexpected condition or issue that prevented it from fulfilling the request. This error does not specify the exact problem but points to an internal issue within the server, such as a misconfiguration or a server-side failure. It typically means the problem lies with the server itself, requiring further investigation by the server administrator or technical team.
**Example:** If a website experiences a sudden software crash or a malfunctioning server-side script, users trying to access the site may see a 500 error. The root cause might be a misconfigured script, insufficient server resources, or an issue with the serverâs infrastructure.
#### **501 Status Code: Not Implemented**
The â501 Not Implementedâ error occurs when the server does not recognize the request method used by the client and is unable to support it. This can happen when a client sends a request using a method (such as PUT, DELETE, or PATCH) that the server is not configured to handle. Essentially, the server cannot process the request using the specified method.
**Example:** A client sends a DELETE request to a server, but the server does not support or allow the DELETE method for the requested resource. As a result, the server responds with a 501 error.
#### **502 Status Code: Bad Gateway**
The â502 Bad Gatewayâ error occurs when a server, acting as a gateway or proxy, receives an invalid response from an upstream server while trying to fulfill a request. This error indicates a communication failure between servers, where the gateway server could not get a valid response from the upstream server it was trying to access.
**Example:** If youâre using a reverse proxy (e.g., Nginx or Apache) that forwards requests to a backend web server, and the backend server returns an invalid or no response, the proxy server will return a 502 error. This is common in server-side failures, like a backend database going down.
#### **503 Status Code: Service unavailable**
The â503 Service Unavailableâ status code is returned when the server is temporarily unable to process the request. This typically happens when the server is overloaded or undergoing maintenance. Itâs a temporary condition, and the server should return to normal operation once the issue is resolved.
**Example:** If a popular website experiences high traffic, it may overload the server, leading to a 503 error. Similarly, during scheduled maintenance or updates, users trying to access the site may encounter this error.
#### **504 Status Code: Gateway Timeout**
The â504 Gateway Timeoutâ error occurs when a server acting as a gateway or proxy does not receive a timely response from another server it is trying to access in order to load a web page or fulfill a request. This often happens when the upstream server takes too long to respond, causing the gateway server to timeout.
**Example:** If a user tries to access a website that requires data from a third-party service, and that third-party service is slow to respond or unavailable, the gateway server will return a 504 error, indicating that the timeout was caused by the upstream service.
#### **505 Status Code: HTTP Version Not Supported**
The â505 HTTP Version Not Supportedâ error occurs when the server does not support the version of the HTTP protocol used in the clientâs request. This error typically arises when the client uses an outdated or unsupported HTTP version that the server cannot process.
**Example:** If a client sends a request using HTTP/1.0 but the server only supports HTTP/1.1 or HTTP/2, the server will return a 505 error because it cannot handle the older version.
#### **506 Status Code: Variant Also Negotiates**
The â506 Variant Also Negotiatesâ status code indicates that the server has an internal configuration error. It typically happens when a server attempts to select a variant of the requested resource but encounters a problem in the content negotiation process. The error occurs when the server cannot determine the appropriate variant resource.
**Example:** A server misconfiguration, such as when multiple resources are set to negotiate content but one of them is also configured to perform content negotiation itself, leading to a conflict that results in a 506 error.
#### **507 Status Code: Insufficient Storage**
The â507 Insufficient Storageâ error indicates that the server does not have enough storage space to complete the request. This typically happens when the server runs out of storage or resources needed to fulfill the operation, such as when the server cannot write to the file system or database.
**Example:** If a server running a file-sharing application runs out of disk space while uploading a new file, it may return a 507 error indicating insufficient storage.
#### **508 Status Code: Loop Detected**
The â508 Loop Detectedâ status code occurs when the server detects an infinite loop while processing a request. This usually happens when a request is repeatedly forwarded between multiple resources without ever reaching its destination, causing the server to detect a processing loop.
**Example:** If a URL is incorrectly configured to redirect to itself or another URL that redirects back to the original, an infinite loop will occur, and the server will return a 508 error.
#### **510 Status Code: Not Extended**
The â510 Not Extendedâ error indicates that the server requires additional extensions or features to fulfill the request. The current request lacks the necessary extensions or features, meaning the server cannot process it successfully without further modifications or additions.
**Example:** If the server requires specific headers or protocols to process a request but the client does not provide them, the server may return a 510 error.
#### **511 Status Code: Network Authentication Required**
The â511 Network Authentication Requiredâ error occurs when the client must authenticate with the network before the server will allow access. This is often seen with captive portals, such as those in public Wi-Fi networks, where the user must authenticate or log in before they can access the internet.
**Example:** A user connects to a public Wi-Fi network and tries to visit a website, but they receive a 511 error indicating they need to complete a login or authentication process before they can proceed.
## **Tools for Checking HTTP Status Codes**
There are several tools available to help you check the HTTP status codes of your websiteâs pages, which is crucial for monitoring site health and optimizing SEO. These tools provide insights into server responses, identifying issues like broken links, redirects, or inaccessible pages. Here are some popular [tools for checking HTTP status codes](https://www.infidigit.com/tools/http-status-checker/):
**1\. Google Search Console**:
**Purpose**: Google Search Console offers a comprehensive view of how Googlebot is interacting with your site. It provides detailed reports on crawl errors, server issues, and HTTP status codes. Using this tool, you can easily identify 404 errors, server unresponsiveness, or any issues preventing Google from indexing your pages.
**How it helps**: Google Search Console will alert you to pages that have issues, such as â404 Not Foundâ errors or â500 Internal Server Errors.â You can use this information to resolve problems that may hinder your siteâs search engine rankings.
**2\. Screaming Frog SEO Spider**:
**Purpose**: Screaming Frog is a powerful desktop tool that crawls your website, similar to how a search engine bot would. It provides a comprehensive analysis of all the HTTP status codes on your website, including 404 errors, redirects, and other issues.
**How it helps**: It not only checks for broken links but also helps you analyze the serverâs response for each URL, allowing you to find and fix server-side issues. You can also export the results into various formats for detailed reporting.
**3\. GTMetrix**:
**Purpose**: GTMetrix is a performance analysis tool that provides insights into your websiteâs loading times, including detailed HTTP status codes and server performance. It offers a comprehensive report on various elements of page speed and response times.
**How it helps**: It gives you an understanding of how your server responds to requests. This is helpful for detecting HTTP errors such as slow server responses, redirects, or server misconfigurations that affect performance. It also provides suggestions for improving your websiteâs speed and server response time.
**4\. Pingdom**:
**Purpose**: Pingdom is a popular website monitoring tool that helps you check your siteâs uptime, performance, and server response. It offers HTTP status code checks along with a detailed performance report from multiple locations worldwide.
**How it helps**: Pingdom allows you to monitor the HTTP status codes returned by your website from different parts of the world, ensuring that users from various locations are experiencing optimal load times and server responses. It can also send you alerts if certain pages return errors or slow down.
**5\. Curl**:
**Purpose**: Curl is a command-line tool that allows you to manually check the HTTP status codes for any website. By entering a URL, you can directly interact with the server and analyze the response.
**How it helps**: Curl is useful for developers or users with technical knowledge who need to check the response from a server for debugging or troubleshooting. By adding flags (e.g., \-I to get header information), you can get detailed server responses, including HTTP status codes, headers, and more.
**6\. Ahrefs**:
Purpose: Ahrefs is a comprehensive SEO toolset that provides detailed audits of your website, including a breakdown of HTTP status codes for each page. It helps you monitor broken links, redirect chains, and other server-side issues that could impact SEO.
How it helps: Ahrefs crawls your entire website, identifies HTTP errors such as 404s or 500s, and generates reports. It can also identify other SEO-related issues, such as slow-loading pages or poor server responses, which can negatively impact your siteâs ranking.
These tools are essential for diagnosing server issues, ensuring a smooth user experience, and maintaining good SEO practices.
Now that you are familiar with the most common HTTP errors, you should have a good basis for troubleshooting issues with your web servers or applications. If you come across any error codes that were not mentioned above, feel free to discuss them in the comments section.
## **FAQs about HTTP Status Codes**
### **What are HTTP Status Codes?**
HTTP status codes are three-digit numbers used in the HTTP protocol to indicate the outcome of a clientâs request to a web server. They help communicate whether the request was successful, encountered an error, or requires further action. Understanding these HTTP protocol status codes is essential for diagnosing website issues and ensuring smooth user experiences.
### **Why are HTTP Status Codes Important?**
HTTP status codes play a crucial role in helping search engines and browsers understand the state of a webpage. These HTTP response codes assist in diagnosing website issues, ensuring proper indexing, and improving user experience. By identifying errors like broken links or redirects, they help maintain website performance and SEO effectiveness.
### **What is the Difference Between 2xx and 3xx Status Codes?**
2xx codes represent successful requests, while 3xx codes indicate redirects. 2xx confirms the server processed the request, and 3xx informs the client that the resource has been moved or redirected.
### **How Do I Fix a 403 Forbidden Error?**
A 403 Forbidden error occurs when a server blocks access to a resource due to insufficient permissions. To fix this, check and adjust file or directory permissions, update your .htaccess file, or modify security settings. If the issue persists, contact your hosting provider for assistance. Understanding web server status codes like 403 helps diagnose and resolve such access issues effectively.
### **How Can I Check HTTP Status Codes for My Website?**
You can check web page status codes using various methods, including browser developer tools, online status checkers, and website crawlers. Tools like Screaming Frog, Google Search Console, and third-party HTTP header checkers help identify status codes, allowing you to diagnose errors and ensure smooth website performance.

Popular Searches
[SEO Services](https://www.infidigit.com/seo-search-engine-optimization/)
[Website SEO Audit Packages](https://www.infidigit.com/seo-audit-pricing-p1/)
[WordPress Development](https://www.infidigit.com/wordpress-development-services/)
[Website Structure](https://www.infidigit.com/blog/website-structure/)
[E-commerce SEO Services](https://www.infidigit.com/e-commerce-seo/)
[SEO For Ecommerce](https://www.infidigit.com/industries/seo-for-ecommerce/)
[SEO Packages](https://www.infidigit.com/seo-pricing-p1/)
[Types of SEO](https://www.infidigit.com/blog/types-of-seo/)
[SEO Audit Services](https://www.infidigit.com/seo-audit/)
[SEO for Education](https://www.infidigit.com/industries/seo-for-educational/)
[Top YouTube Searches](https://www.infidigit.com/blog/top-youtube-searches/)
[Googlebots IP Addresses](https://www.infidigit.com/blog/google-update-googlebots-ip-addresses/)
[SEO Services in Mumbai](https://www.infidigit.com/location/india-mumbai-seo/)
[SEO for Insurance](https://www.infidigit.com/industries/seo-for-insurance/)
[List of Search Engines](https://www.infidigit.com/blog/list-of-search-engines/)
[YouTube SEO Tools](https://www.infidigit.com/blog/youtube-seo-tools/)
[Link Building Services](https://www.infidigit.com/link-building/)
[SEO for OTT Platforms](https://www.infidigit.com/industries/seo-for-ott/)
[Top YT Cooking Channels](https://www.infidigit.com/blog/top-youtube-cooking-channels/)
[308 Permanent Redirect](https://www.infidigit.com/blog/308-permanent-redirect/)
[SEO Services in Bangalore](https://www.infidigit.com/location/india-bangalore-seo/)
[WordPress SEO Services](https://www.infidigit.com/wordpress-seo-services/)
[What is a Blog](https://www.infidigit.com/blog/what-is-a-blog/)
[Import XML Formula](https://www.infidigit.com/blog/import-xml-formula)
How useful was this post?
3\.4 / 5. 14 |
| Shard | 181 (laksa) |
| Root Hash | 15363632932393162581 |
| Unparsed URL | com,infidigit!www,/blog/http-status-codes/ s443 |