Bulk HTTP Status Code Checker

Check a list of URLs for 200, 301, 302, 404 and 500 responses at once.

Auditing a batch of URLs at once

Paste up to 50 URLs (one per line) and this tool checks each one's raw HTTP status code - 200 for success, 3xx for redirects, 4xx or 5xx for errors - without following redirects, so you see exactly what status each specific URL returns. Useful after a migration, a bulk link audit, or checking whether old pages have been properly redirected rather than left as broken links. Export the results as a CSV when you are done.

Why this checks each URL's own status rather than following redirects to a final destination

After a site migration, the question usually isn't "where does this old URL eventually lead" but "did this specific old URL actually get redirected at all, or is it a dead link" - showing the raw status each URL itself returns answers that question directly, while silently following every redirect would hide exactly the information a bulk audit is meant to surface.

Why checking many URLs at once matters more after a migration than checking one at a time

A site migration or URL restructuring can affect hundreds of pages at once, and missing even a handful of un-redirected old URLs means real visitors and search crawlers hitting dead links - checking a full batch in one pass makes it practical to audit an entire migration's worth of URLs quickly, rather than checking each one individually and missing the ones you didn't think to check.

Why some URLs come back as an error instead of a status code

A genuine HTTP error (like a 404 or 500) still means the server responded - but this tool distinguishes that from cases where no response was received at all: a DNS lookup failure, a refused connection, or a timeout. Those failures happen before any HTTP status could even be returned, which is why they're reported separately rather than being mislabeled as a specific status code.

Frequently asked questions

Why does this show 301/302 instead of the final destination status?

This tool deliberately does not follow redirects, so you see the exact status each URL itself returns - useful for auditing which URLs redirect versus which are genuinely broken. To trace a full redirect chain for one URL, use the dedicated redirect checker tool.

Why do some URLs show an error instead of a status code?

This usually means the server could not be reached at all (DNS failure, connection refused, or timeout) rather than returning an HTTP response - double-check the URL is correct and the site is online.

Why is checking many URLs at once useful after a site migration?

A migration can affect hundreds of pages, and missing even a few un-redirected URLs leaves dead links for visitors and crawlers - checking a full batch in one pass makes a complete audit practical.

Can I check more than 50 URLs?

This tool caps a single check at 50 URLs - for a larger audit, run it in multiple batches of up to 50 each.

What should I do with a URL that comes back as an error?

Double-check the URL is typed correctly and the site is actually online - an error means no HTTP response was received at all, which is a different problem than a URL returning a 404 or 500 status.

More in Technical SEO & Site Management