What to prepare
The public URL, domain, IP address, record type, or audit option requested by the checker.
Redirect tracing follows the sequence from an entered URL to its final destination and records each HTTP hop. Long chains add latency and can reveal outdated protocol, hostname or path migrations.
The public URL, domain, IP address, record type, or audit option requested by the checker.
A point-in-time observation from the public target and the checks available on this page.
One useful scenario is to run a fresh diagnostic after a hosting, DNS, certificate, redirect, content or performance change. Start with a representative input, inspect the first result, then adjust one setting at a time if you need a different outcome.
The checker uses the public target you enter to make a diagnostic request. Do not place credentials or private access tokens in a URL.
Check domain registration and expiry dates.
CheckScan a page and find broken internal or external links.
ScanGenerate a clean robots.txt file for your website.
GenerateGenerate a simple XML sitemap from your URLs.
GenerateGenerate title, description and social meta tags.
GenerateEnter the website URL you want to check.
We follow each redirect step by step.
We collect status codes, protocols, and timings.
View the full redirect chain and final destination.
A redirect sends visitors and search engines from one URL to another — used when content moves or for tracking.
301 (permanent), 302 (temporary), 303 (see other), 307 (temporary preserve method), 308 (permanent preserve method).
Too many redirects slow page loads and can confuse search engines. Direct links are always best.
Browsers usually follow up to 10-20 redirects. SEO best practice is to keep chains to 1-2 hops maximum.
No — only server-side HTTP redirects (3xx status codes) are traced.