Bulk check HTTP status codes and redirect chains for up to 50 URLs at a time. Each URL is checked one by one with live progress, so problems surface while you watch.
Every HTTP status code tells you something about the health of a URL. A 200 means the page is reachable and serving content. A 301 or 302 signals a permanent or temporary move. A 404 means the page is gone. A 5xx code points to a server side problem. Checking URLs in bulk lets you catch patterns: a site section returning 404s, a batch of pages stuck in long redirect chains, or DNS misconfigurations affecting multiple URLs.
Redirects are a normal part of running a website, but every extra hop costs something. Each redirect adds a new round trip between the browser and your server, increasing the total time before a page becomes interactive. When a chain runs three or four hops deep, users wait longer and search engine crawlers spend more of their crawl budget on redirects instead of content.
Loops are the most dangerous failure mode. A redirect that points back to itself, or to another URL in the chain, creates an infinite loop that browsers eventually abandon. The page never loads, the user sees an error, and any ranking signal attached to that URL is lost. This tool catches loops before they reach production by watching for URLs that repeat within a chain.
DNS resolution is the quiet predecessor to every redirect. A slow or misconfigured DNS record makes the first hop expensive regardless of how clean the rest of the chain is. By surfacing the A, AAAA, and CNAME records for your host, this tool connects the redirect path back to the infrastructure that serves it.
Paste up to 50 URLs into the text area, one per line. Click "Check All" and the tool processes each URL one at a time, sending a HEAD request and following any redirect chain until it reaches a final destination or hits a loop. Progress is shown in real time.
The results table shows each URL with its final HTTP status code, the number of redirect hops, total response time, and any issues found. Click "Details" on any row to expand the full redirect chain with status codes and timing for each hop, plus DNS records for the host.
Keep redirects to a single hop whenever possible, and prefer server level redirects over meta refresh or JavaScript based redirects. Run this check after migrations, certificate changes, or CDN configuration updates to confirm your paths stay short and correct.