HTTP Status Code Reference
A complete reference of all HTTP status codes you may encounter in your dislike404.com scan results, including what each code means and what to do about it.
Understanding your scan results
When dislike404.com scans your website, every crawled URL ends up with a result. Most of the time this is an HTTP status code returned by the server — but sometimes the crawler cannot reach the URL at all, in which case a connection failure is recorded instead. This reference covers all possible results, what they mean, and what to do about them.
💬 1xx — Informational
These codes are informational responses and indicate that the request was received and is being processed. They are not errors and do not require any action. They are rarely seen in scan results as they are typically not the final response from the server.
HTTP 100 Continue
The server has received the request headers and the client should proceed to send the request body. This is part of the HTTP handshake and not relevant for regular web pages. No action needed.
HTTP 101 Switching Protocols
The server is switching to a different protocol as requested by the client, for example from HTTP to WebSockets. No action needed.
HTTP 102 Processing
Used by WebDAV servers to indicate that the request has been received and is being processed, but no response is available yet. Rarely seen outside of WebDAV environments. No action needed.
HTTP 103 Early Hints
A relatively modern status code that allows the server to send preliminary response headers before the final response is ready, typically used to preload resources. No action needed.
✅ 2xx — Success
These codes mean the request was successful. You generally do not need to take any action.
HTTP 200 OK
The page loaded successfully. This is what you want to see for most URLs.
HTTP 201 Created
The request was successful and a new resource was created as a result. Typically returned by APIs, not regular web pages. No action needed.
HTTP 202 Accepted
The request has been accepted for processing, but processing is not yet complete. Rarely seen on regular websites. No action needed.
HTTP 203 Non-Authoritative Information
The request was successful but the response comes from a third-party source rather than the original server, for example a proxy. No action needed.
HTTP 204 No Content
The request was successful but there is no content to return. Common for API endpoints that confirm an action without returning data. No action needed.
HTTP 205 Reset Content
The request was successful and the client should reset the document view. Typically used in form submissions to clear the form after submission. Rarely seen in scan results. No action needed.
HTTP 206 Partial Content
The server delivered only part of the content, usually in response to a range request. Common for media files. No action needed.
HTTP 207 Multi-Status
The response contains multiple status codes for multiple independent operations. Used by WebDAV servers. Rarely seen outside of WebDAV environments. No action needed.
HTTP 208 Already Reported
Used by WebDAV to indicate that the results of a previous request have already been reported. Rarely seen outside of WebDAV environments. No action needed.
HTTP 226 IM Used
The server has fulfilled a request and the response is a representation of the result of one or more instance manipulations applied to the current instance. Rarely seen in practice. No action needed.
↪️ 3xx — Redirects
Redirects mean the URL points to a different location. dislike404.com does not follow redirects — the redirect itself is logged as the result. This means if a link on your website points to a URL that redirects, you will see the redirect code in your results.
HTTP 300 Multiple Choices
The requested URL has multiple possible responses and the client must choose one. Rarely seen on modern websites.
Internal URL: If you encounter this unexpectedly, investigate your server configuration.
External URL: No action needed initially. If the issue persists across multiple scans, consider removing the link or adding it to your blacklist.
HTTP 301 Moved Permanently
The URL has been permanently moved to a new location. Redirects are a normal part of the web — URL shorteners, social media links, and many external services rely on redirects by design.
Internal URL: No action needed. However, updating the link to point directly to the destination is a minor SEO improvement and saves an unnecessary request. Internal links ideally should not redirect.
External URL: No action needed.
HTTP 302 Found
The URL is temporarily redirecting to another location. Temporary redirects are completely normal.
Internal URL: No action needed. If the redirect has been in place for a long time, consider whether it should be made permanent (301) or whether the original URL should be restored.
External URL: No action needed.
HTTP 303 See Other
The server is redirecting the client to a different URL using a GET request, typically after a form submission. Since dislike404.com only performs GET requests, this code is unlikely to appear in your scan results.
Internal URL: If you encounter this unexpectedly, investigate your server or application configuration.
External URL: No action needed.
HTTP 304 Not Modified
The page has not changed since the last request. This is a normal caching response. No action needed.
HTTP 305 Use Proxy
This code is deprecated and should no longer be used on modern websites.
Internal URL: Investigate your server configuration immediately — this code should not appear on any modern website.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 306 Switch Proxy
This code is no longer used and is reserved. It was defined in a previous version of the HTTP specification but has since been deprecated.
Internal URL: Investigate your server configuration immediately — this code should not appear on any modern website.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 307 Temporary Redirect
Similar to 302, but explicitly requires that the HTTP method must not change during the redirect. Functionally identical to 302 for most use cases.
Internal URL: No action needed. If the redirect has been in place for a long time, consider whether it should be made permanent (308) or whether the original URL should be restored.
External URL: No immediate action needed.
HTTP 308 Permanent Redirect
Similar to 301, but explicitly requires that the HTTP method must not change during the redirect. Functionally identical to 301 for most use cases.
Internal URL: No action needed. However, updating the link to point directly to the destination is a minor SEO improvement and saves an unnecessary request.
External URL: No action needed.
⚠️ 4xx — Client Errors
These codes indicate that something went wrong with the request itself. Most 4xx errors require your attention.
HTTP 400 Bad Request
The server could not understand the request. This usually indicates a malformed URL.
Internal URL: Check whether the URL on your website is correctly formatted.
External URL: The external URL may be malformed or the external server may have a bug. If it persists, consider removing the link or adding it to your blacklist.
HTTP 401 Unauthorized
The page requires authentication before it can be accessed.
Internal URL: If this appears unexpectedly on a page that should be public, check your authentication configuration.
External URL: The external page requires a login. If you are linking to a public resource that now requires authentication, update, remove the link or add it to your blacklist.
HTTP 402 Payment Required
Rarely used in practice. Originally intended for payment gateways, now sometimes used to indicate usage limits have been exceeded.
Internal or external: Investigate what the resource is and why it requires payment or has hit a limit. If it persists, consider removing the link or add it to your blacklist.
HTTP 403 Forbidden
The page exists but access is denied.
Internal URL: This may be intentional (e.g. a protected admin area or a page behind a login). If it appears unexpectedly, check your server permissions or access control configuration.
External URL: The external page restricts access. If the link is meant to be publicly accessible, consider removing it. If the restriction is intentional (e.g. a members-only page), no action needed.
HTTP 404 Not Found
The most common error — the page does not exist. The URL was found on your website but the destination is gone.
Internal URL: The page has been deleted or the URL has changed. Either restore the page, set up a redirect to the new location, or update the link on your website.
External URL: The external page no longer exists. Remove or replace the link on your website. Linking to 404 pages is bad for user experience and SEO.
HTTP 405 Method Not Allowed
The HTTP method used is not allowed for this URL. This can happen when a crawler accesses a URL that only accepts POST requests.
Internal URL: If the URL should be accessible via GET, check your server or application configuration.
External URL: The external resource may simply not support GET requests. Consider removing the link or adding it to your blacklist.
HTTP 406 Not Acceptable
The server cannot produce a response matching the criteria given in the request headers. Rarely seen on regular websites.
Internal URL: Check your server or application configuration.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 407 Proxy Authentication Required
The client must authenticate with a proxy before the request can be fulfilled. Unlikely to appear in normal scan results.
Internal URL: Check your proxy configuration.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 408 Request Timeout
The server took too long to respond and timed out.
Internal URL: Your server may be overloaded or a specific page may have a performance issue. Check your server logs.
External URL: The external server is slow or overloaded. No immediate action needed unless it persists. If it persists, consider removing the link or adding it to your blacklist.
HTTP 409 Conflict
The request could not be completed due to a conflict with the current state of the resource. Typically returned by APIs rather than regular web pages.
Internal URL: Investigate your server or application configuration.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 410 Gone
Similar to 404, but the server explicitly confirms the page is permanently gone and will not return.
Internal URL: The page has been intentionally removed. If you still link to it, update or remove the link.
External URL: Remove the link. The destination is permanently gone.
HTTP 411 Length Required
The server requires the request to include a Content-Length header. Since dislike404.com sends standard GET requests, this should not appear in normal scan results.
Internal URL: Check your server configuration.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 412 Precondition Failed
A precondition given in the request headers was not met. Typically used in APIs with conditional requests. Unlikely to appear in normal scan results.
Internal URL: Investigate your server or application configuration.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 413 Payload Too Large
The request body is larger than the server is willing to accept. Since dislike404.com only sends GET requests without a body, this should not appear in normal scan results.
Internal URL: Check your server configuration.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 414 URI Too Long
The URL provided in the request is longer than the server is willing to process.
Internal URL: Check whether any links on your website contain unusually long URLs.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 415 Unsupported Media Type
The server refuses to accept the request because the media type is not supported. Unlikely to appear in normal scan results since dislike404.com does not send a request body.
Internal URL: Check your server or application configuration.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 416 Range Not Satisfiable
The server cannot fulfill the requested range. Typically occurs with media files when a specific byte range is requested.
Internal URL: Check your server configuration for media file handling.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 417 Expectation Failed
The server cannot meet the requirements of the Expect request header. Unlikely to appear in normal scan results.
Internal URL: Check your server configuration.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 418 I'm a Teapot
Yes, this is a real HTTP status code — introduced as an April Fools' joke in 1998 and somehow still part of the standard. If you see this, the server is politely telling the crawler it is a teapot and refuses to brew coffee. In practice, some servers use this code to reject automated requests. If you see it on an external URL, the server is likely blocking crawlers intentionally. Consider adding the domain to your blacklist. 🫖
HTTP 421 Misdirected Request
The request was directed at a server that is not able to produce a response for the given URL. Typically indicates a misconfiguration with SSL/TLS or virtual hosting.
Internal URL: Check your server's virtual host and SSL/TLS configuration.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 422 Unprocessable Entity
The server understands the request but cannot process it due to semantic errors. Commonly used by APIs and WebDAV servers. Unlikely to appear on regular web pages.
Internal URL: Investigate your server or application configuration.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 423 Locked
The resource is locked and cannot be accessed. Used by WebDAV servers.
Internal URL: Check your WebDAV configuration if applicable.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 424 Failed Dependency
The request failed because a previous request it depended on also failed. Used by WebDAV servers.
Internal URL: Check your WebDAV configuration if applicable.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 425 Too Early
The server is unwilling to process the request because it may be replayed. Related to TLS early data.
Internal URL: Check your server's TLS configuration.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 426 Upgrade Required
The server requires the client to upgrade to a different protocol, typically TLS.
Internal URL: Check your server configuration — this may indicate an issue with your HTTPS setup.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 428 Precondition Required
The server requires the request to be conditional. Typically used by APIs to prevent the "lost update" problem.
Internal URL: Investigate your server or application configuration.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 429 Too Many Requests
The server is rate-limiting our crawler. The crawler made too many requests in a short period of time.
Internal URL: Reduce the thread count in your scan settings — setting it to 1 will slow the crawler down significantly and might resolves rate-limiting issues. You can also whitelist the dislike404.com user agent in your rate-limiting configuration.
External URL: The external server is rate-limiting the crawler. This is not something you can fix directly. Consider adding the domain to your blacklist if it consistently triggers this error.
HTTP 431 Request Header Fields Too Large
The server refuses to process the request because the request headers are too large. Can sometimes occur if cookies or other headers have grown very large.
Internal URL: Check your server configuration for header size limits.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 451 Unavailable For Legal Reasons
The page is unavailable due to a legal demand, such as a DMCA takedown or court order.
Internal URL: If this appears unexpectedly, investigate immediately.
External URL: Remove the link. The content has been taken down for legal reasons.
HTTP 444 No Response
A non-standard code used by some servers (notably nginx) to close the connection without sending a response.
Internal URL: Check your server configuration — this may indicate a deliberate block or a misconfiguration.
External URL: The external server is actively refusing connections. Consider adding it to your blacklist.
HTTP 499 Client Closed Request
The client closed the connection before the server finished responding. This can happen if the page is very slow to load.
Internal URL: Investigate slow-loading pages on your website.
External URL: The external server is too slow. No immediate action needed.
HTTP 499 Client Closed Request
A non-standard code used by some servers to indicate that the client closed the connection before the server finished responding. This can happen if a page takes too long to load and the crawler times out waiting for the response.
Internal URL: Investigate slow-loading pages on your website. Check your server logs for performance issues.
External URL: The external server is too slow to respond. No immediate action needed. If it persists, consider adding the domain to your blacklist.
🔴 5xx — Server Errors
These codes mean something went wrong on the server side. Internal 5xx errors always require your attention. External 5xx errors may be temporary.
HTTP 500 Internal Server Error
A generic server-side error. Something went wrong but the server does not give a specific reason.
Internal URL: Check your server logs immediately. This is a serious error that affects your visitors.
External URL: The external server has an issue. Wait and re-scan — if it persists, consider removing the link or adding it to your blacklist.
HTTP 501 Not Implemented
The server does not support the functionality required to fulfill the request. This can occur when the server does not recognize the request method.
Internal URL: Investigate your server configuration — this should not appear on a modern web server.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 502 Bad Gateway
The server received an invalid response from an upstream server (e.g. a reverse proxy or load balancer).
Internal URL: Check your server infrastructure — this often indicates an issue with a proxy, load balancer, or upstream service.
External URL: The external server has an infrastructure issue. Usually temporary — check again later. If it persists, consider removing the link or adding it to your blacklist.
HTTP 503 Service Unavailable
The server is temporarily unavailable, usually due to maintenance or overload.
Internal URL: Your website was down during the scan. Check whether this was planned maintenance. If not, investigate immediately.
External URL: The external server was temporarily down during the scan. Usually resolves on its own — check again on the next scan. If it persists, consider removing the link or adding it to your blacklist.
HTTP 504 Gateway Timeout
The upstream server did not respond in time.
Internal URL: Similar to 502 — check your server infrastructure and logs.
External URL: The external server is slow or has an infrastructure issue. Usually temporary. If it persists, consider removing the link or adding it to your blacklist.
HTTP 505 HTTP Version Not Supported
The server does not support the HTTP version used in the request. Rarely seen on modern web servers.
Internal URL: Check your server configuration — this may indicate an outdated or misconfigured web server.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 506 Variant Also Negotiates
The server has an internal configuration error related to content negotiation. This code indicates a circular reference in the server's configuration.
Internal URL: Investigate your server configuration immediately — this is a server-side misconfiguration.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 507 Insufficient Storage
The server cannot store the representation needed to complete the request. Used by WebDAV servers but can also indicate that the server has run out of disk space.
Internal URL: Check your server's disk space immediately — this is a critical issue that affects your entire website.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 508 Loop Detected
The server detected an infinite loop while processing the request. Used by WebDAV servers when a request would cause an infinite loop.
Internal URL: Investigate your server configuration immediately — this indicates a circular reference or misconfiguration in your WebDAV setup.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 509 Bandwidth Limit Exceeded
The server has exceeded its allocated bandwidth limit. Common with shared hosting providers that enforce bandwidth caps.
Internal URL: Check your hosting plan immediately — your website may be partially or fully unavailable to visitors. Consider upgrading your hosting plan or optimizing your bandwidth usage.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 510 Not Extended
The server requires further extensions to the request before it can fulfill it. Rarely seen in practice.
Internal URL: Investigate your server configuration.
External URL: No action needed. If it persists, consider removing the link or adding it to your blacklist.
HTTP 511 Network Authentication Required
The client needs to authenticate to gain network access (e.g. a captive portal). This should not appear in normal scan results.
🔌Connection Failures
These are not HTTP status codes. They indicate that the crawler was unable to complete the request — either because no connection could be established, or because the URL itself is invalid.
Connection Timeout
The server did not respond within the allowed time. The crawler gave up waiting.
Internal URL: Your server or a specific page is too slow to respond. Check your server performance and logs. This may also happen if your server rate-limits the crawler — see 429 above.
External URL: The external server is slow or unresponsive. If this happens consistently, consider adding the domain to your blacklist.
Invalid URL
The URL found on your page is malformed and cannot be requested.
Internal URL: Check the link on your page — it likely contains a typo or an encoding issue.
External URL: Same — check whether the link on your page is correctly formatted.
Failed (Unknown Reason)
The connection failed for an unspecified reason. This can happen due to network issues, SSL/TLS certificate problems, server misconfigurations, or the server actively refusing the connection.
Internal URL: Check your server's SSL certificate and configuration. If your certificate has expired or is misconfigured, this code will appear.
External URL: The external server has an issue outside your control. If it persists, consider removing the link or adding the domain to your blacklist.
🚫 Skipped URLs
These are not HTTP status codes — they indicate that a URL was intentionally not crawled.
User Blacklist
You have manually excluded this URL pattern in your blacklist settings. No action needed — this is working as intended.
Global Blacklist
This URL is blocked globally by dislike404.com. This typically applies to known third-party services and domains that do not permit automated access. No action needed.
robots.txt Blocked
This URL is excluded because the website's robots.txt file disallows crawling. dislike404.com respects robots.txt rules for both internal and external URLs.
Internal URL: The URL is excluded by your own robots.txt configuration. If you want this URL to be scanned, update your robots.txt to allow access for the dislike404.com crawler.
External URL: The external website has indicated via robots.txt that it does not want to be crawled. No action needed — this is working as intended.