HTTP Status Checker

Check HTTP status codes and redirects

Every time a browser or search engine asks for a page, the server answers with a three-digit status code before anything else. That code decides whether the page is shown, moved, missing or broken. This checker requests your URL the way a browser does, follows every redirect one hop at a time and shows the status, the target and the time of each step, plus the response headers of the final page.

Status code families

• 2xx success: 200 OK is what a working page should return.
• 3xx redirects: 301 and 308 are permanent, 302 and 307 are temporary, 304 means "not modified".
• 4xx client errors: 404 not found, 410 gone, 403 forbidden, 429 too many requests.
• 5xx server errors: 500 internal error, 502 bad gateway, 503 unavailable, 504 timeout. Codes 520 to 530 come from Cloudflare when it cannot reach the origin server.

Why redirect chains matter for SEO

When you move a page or switch to HTTPS, old links should reach the new address with a single permanent redirect. Chains such as http to https to www to the final page slow visitors down and make search engines spend more time crawling. Temporary redirects on moved content can stop rankings from passing to the new URL. The checker warns about chains longer than one hop, temporary redirects and loops.

Checking many URLs

After a site migration, paste up to 10 old URLs at a time to confirm each one lands on the right page with a 200. Copy the result as text or download it as CSV for your migration sheet. Use the HEAD method for a lighter check, or turn off "Follow redirects" to see only the first answer.