広告が嫌いですか? 行く広告なし今日 

Redirect Checker

開発者安全

広告・取り除く？

入力

出力

サーバー側

広告・取り除く？

ガイド

Redirect Checker

Trace the full redirect chain for any URL and see every hop along the way. This tool follows redirects from start to finish, showing the HTTP status code, URL, and response time at each step. Essential for debugging redirect chains, verifying SEO migrations, and finding redirect loops before they cause problems.

使い方

Enter any URL and click Check. The tool follows the redirect chain server-side, recording each hop with its HTTP status code, destination URL, and response time. The results display the complete chain from the original URL to the final destination, making it easy to spot unnecessary redirects, loops, or incorrect status codes.

特徴

Full Chain Tracing – Follows every redirect from start to final destination, showing the complete path
Status Codes Per Hop – Displays the HTTP status code (301, 302, 307, 308, etc.) at each redirect step
Response Timing – Shows how long each hop takes, helping identify slow redirects in the chain
Loop Detection – Detects and alerts you to redirect loops that would otherwise hang a browser
Final Destination – Clearly highlights where the URL ultimately resolves to
Server-Side Fetching – Traces redirects from the server for accurate results, unaffected by browser caching

広告・取り除く？

 よくある質問

What is the difference between a 301 and 302 redirect?

A 301 redirect is permanent, telling search engines the page has moved permanently and to transfer SEO value to the new URL. A 302 redirect is temporary, indicating the page has moved temporarily and search engines should keep indexing the original URL. Using the wrong type can hurt your SEO — permanent moves should use 301 and temporary redirects should use 302 or 307.
How many redirects are too many?

Google recommends keeping redirect chains to a maximum of 3 hops, though most browsers will follow up to 20 before giving up. Each redirect adds latency and can dilute SEO value. Ideally every URL should reach its final destination in one redirect or none at all. Long chains often indicate accumulated technical debt from site migrations.
What is a redirect loop and how do I fix it?

A redirect loop occurs when URL A redirects to URL B, which redirects back to URL A, creating an infinite cycle. Browsers detect this and show an error like ERR_TOO_MANY_REDIRECTS. Common causes include misconfigured server rules, conflicting CMS settings (like forcing both www and non-www), or SSL redirect rules that conflict with other redirects. Fix them by reviewing your .htaccess, nginx config, or CDN redirect rules for conflicting patterns.