HTTP Status Checker

A 301 is a 'Permanent Redirect'. It tells browsers and search engines that a page has moved forever, and they should update their links and pass SEO value to the new page. A 302 is a 'Temporary Redirect', meaning the page is just moved for now, and search engines should keep the old URL in their index.

A 404 error means the server is online and responding, but it cannot find the specific page or file you requested. This usually happens when a page is deleted, a URL is typed incorrectly, or a link is broken.

A 500 error means that something has gone wrong on the website's server, but the server cannot be more specific about what the exact problem is. It usually indicates a crash in the website's code, a database failure, or a misconfiguration on the hosting server.

If our tool cannot reach the domain at all (for example, the domain doesn't exist, the DNS is misconfigured, or the server is completely offline), it cannot get an HTTP status code. In this case, the connection simply fails before a code can be generated.

A 403 Forbidden status means the server understands your request, but is actively refusing to authorize it. This usually happens if you are trying to access a private directory, you don't have the right login permissions, or the server has blocked your IP address.

Response headers provide crucial metadata about the server and the webpage. They can tell you what software the server is running (e.g., Nginx, Apache), how long the browser is allowed to cache the page, and enforce security policies (like HSTS or Content Security Policies).

No, if done correctly! A 301 permanent redirect is the SEO best practice for moving a page. Google has confirmed that a 301 redirect passes 100% of the 'link equity' (SEO power) from the old URL to the new URL.

The response time in our tool measures the 'Time to First Byte' (TTFB) from our backend server to the target website. It is the total time it took in milliseconds for the target server to process the request and start sending data back.

A 401 Unauthorized error is similar to a 403 Forbidden, but specifically means that you must log in or provide valid authentication credentials (like a username and password) before the server will grant you access to the requested page.

A 502 Bad Gateway usually occurs when a server (acting as a proxy or gateway, like Cloudflare or a load balancer) receives an invalid response from an inbound backend server. It basically means one server tried to talk to another server, and the second server messed up.

A 503 error means the server is currently unable to handle the request due to a temporary overloading or maintenance of the server. This is the correct status code a website should return when it goes down for scheduled maintenance.

Yes! You can check both HTTP and HTTPS URLs. Often, checking the HTTP version of a site is a great way to verify that the server correctly issues a 301 Permanent Redirect to the secure HTTPS version.

404 errors create a terrible user experience because visitors hit a dead end when trying to navigate your site. Additionally, if other websites link to your 404 pages, you are losing valuable SEO link juice. You should always use 301 redirects to point broken links to relevant, live pages.

A 504 Gateway Timeout happens when a server (acting as a proxy) did not receive a timely response from the upstream server it needed to access in order to complete the request. Basically, a backend server took too long to respond, so the front-facing server gave up.