Public signal checker
Website Redirect Checker
This checker follows a short, validated redirect chain and explains where a public homepage request ends up.
The check uses public live signals and does not make a security, malware, fraud or legal verdict.
Run a public signal check
- HTTP
- DNS
- TLS
- RDAP
- Archive
What this checker analyzes
- HTTP and HTTPS start attempts using standard ports only.
- Up to five redirects with status code, source URL and target URL.
- Whether a redirect leaves the original public host.
Why it matters
- Redirect mistakes can harm user experience, crawling, analytics and certificate expectations.
- External-host redirects are worth reviewing during domain migrations and agency handoffs.
What the results mean
- Final URL is the public URL reached after validated redirects.
- External redirect means the chain moved to a different public host.
- Too many or unsupported redirects are treated as unavailable for that section.
Limits of this check
- Only http and https redirects are followed.
- Redirects to private or local targets are blocked.
- The checker does not follow JavaScript or meta-refresh redirects.
What should also be reviewed manually?
Review notable values in the context of the actual website, its subpages and connected services. A homepage check cannot prove the complete configuration, legal position or security posture.
FAQ
Why only five redirects?
A short limit keeps the API bounded and avoids accidental loops or large network chains.