HTTP Status Checker
Paste up to 100 URLs to check their status codes, redirect counts, and final destinations.
One URL per line
What this tool checks
Paste a list of URLs and the checker will fetch each one, follow any redirects, and report back the final HTTP status code, hop count, and response time.
HTTP status codes
Checks the final status code for each URL after following any redirect chains. 2xx means OK, 3xx means redirect, 4xx and 5xx mean client or server errors.
Redirect chains
Follows redirects automatically (up to 10 hops) and reports how many redirects occurred and what the final destination URL is.
Response time
Records the total time taken to reach a final response for each URL so you can spot slow-responding pages.
Bulk checking
Check up to 100 URLs in a single run, with 20 concurrent workers processing results in parallel and streaming them back as they complete.
Error detection
Network errors and timeouts are captured and flagged separately from HTTP errors so you can distinguish a DNS failure from a 404.
CSV export
Export the full results or the active filtered view to a CSV file. Useful for sharing with a client or importing into a spreadsheet.
How to use the HTTP status checker
A bulk status check takes about 30 seconds for 100 URLs. Here is how to get the most out of it.
Paste your URLs
Add one URL per line in the text box. You can include or omit the protocol - the tool will add https:// automatically if it is missing. The input is capped at 100 URLs per run.
Click Check and watch the results stream in
Results appear one by one as each URL is checked. The progress counter shows how many have completed. You can filter and search while checking is still in progress.
Filter and act on the results
Use the filter tabs to focus on a specific status category - for example, 4xx errors or redirect chains. Use the search box to find a specific URL. Export the filtered view to CSV for reporting.
Frequently asked questions
What HTTP status codes does the tool check?
The tool follows redirects and reports the final status code for each URL. 200 means the page loaded successfully. 301 and 302 are redirects. 404 means the page was not found. 500 means a server error. Status 0 in the results means the request failed before a response was received - usually a DNS error, connection refused, or timeout.
Does the tool follow redirects?
Yes. The checker follows redirect chains of up to 10 hops and reports the final destination URL alongside the hop count. If a redirect loop is detected or the chain exceeds 10 hops, it stops and reports the last status code seen.
What is the timeout per URL?
Each URL has a 6-second timeout. If no response is received within that time, the result is recorded as a network error with status 0.
How many URLs can I check at once?
You can check up to 100 URLs per run. The checker processes 20 at a time in parallel and streams results back as they complete, so you do not have to wait for all 100 to finish before you see data.
What user agent does the checker use?
You can choose from five user agents: Default (Crawly), Googlebot, Google Smartphone, Bingbot, and Chrome. Some servers return different status codes or redirect differently depending on the requesting bot or browser, so switching user agents lets you see exactly what each one gets back.
Is this tool free?
Yes. The HTTP status checker is completely free to use with no login required and no page limits.
When to use a bulk HTTP status checker
HTTP status monitoring is a routine part of technical SEO. Here are the most common situations where a bulk checker saves time.
Site migrations
After a redesign or domain change, verify that all old URLs redirect correctly to their new equivalents.
Broken link audits
Paste a list of internal or external links exported from a crawl tool to find which ones are returning 404 or 5xx errors.
Redirect audits
Check whether redirects are single-hop 301s or chained through multiple steps, which wastes crawl budget and slows users down.
For teams doing regular technical SEO audits, a bulk status checker is one of the first tools to reach for. Crawl the site, export a list of URLs, and run them through the checker to get a fast health snapshot before diving into the detail.
During a site migration, the status checker is invaluable for verifying that every redirect is in place. Paste the old URL list, check them all, and confirm that each one returns a 301 pointing to the correct new URL - not a 302, not a chain, and not a 404.
For deeper analysis - crawling an entire site, detecting redirect chains at scale, auditing hreflang, or comparing two crawls - the Crawly desktop app handles all of that natively on Mac.
Crawly
Audit your entire site, not just one page
Crawly crawls every URL on your site and surfaces issues automatically. Free to download for Mac.
Download free