Digizap

Jouw digitale zakmes.

Redirect chain

Our server follows the address's redirects hop by hop and hands over the whole chain: every status code, every jump from http to https, every host change — and the other spelling (bare and www) alongside, separately. Your browser reads, judges and draws the chain.

The findings are measurement, not taste: a chain longer than two hops is a warning, temporary redirects (302, 303, 307) are a warning because search engines keep the old URL, and a final page on http is a failure. A chain that stalls is reported as incomplete — we do not guess what could have stood after it.

Use this tool after a move, when turning on https, and wherever bare and www exist side by side: the question is not whether something redirects, but whether everything ends on one base.

Follow every redirect of one address hop by hop: which status code, where http becomes https, whether bare and www end on the same address, and how long the chain is.