Website
Redirect Checker
Follow redirect chains and find loops.
Results appear here. Enter a URL with http:// or https://, then select Follow redirects.
Domain Health Report
This page checks one thing. The report checks thirteen — and tells you what to fix first.
A one-off €14.90 report, delivered by email in minutes. Every finding comes with a concrete fix, prioritized.
- DNS records (A/AAAA)
- Nameservers (NS)
- Mail servers (MX)
- SPF record and policy
- DMARC record and policy
- DKIM record (common selectors)
- HTTPS availability
- HTTP to HTTPS redirect
- TLS certificate (issuer, validity, expiry)
- Security headers (HSTS, CSP…)
- CAA records
- robots.txt availability
- sitemap.xml availability
How the redirect checker works
- Enter a full URL, such as http://example.com, and submit the form.
- The FKINFAST server requests the URL without executing it, following each redirect up to 5 hops, and records every step.
- The result shows the full chain — status code and target for each hop — the final URL, total time and a PASS, WARNING, FAIL or UNKNOWN classification.
The check runs from FKINFAST's server, not from your browser. The URL is not stored and no page content, response header or resolved IP address is returned to this page.
Result states
- PASS
- The chain completed and the final destination answered with a 2xx success status.
- WARNING
- The chain could not be completed: it exceeded 5 hops, or a server returned a 3xx without a usable redirect target.
- FAIL
- The final destination answered with a 4xx client error or 5xx server error status.
- UNKNOWN
- No HTTP status was confirmed: the check timed out, the connection or TLS handshake failed, or a destination was rejected.
Page-level errors are separate from these results. A validation error, rate limit, busy response, unavailable service or network failure is shown as an error, not as a FAIL result.
URL rules and limits
- Only http:// and https:// URLs are accepted.
- Only the default ports are allowed: 80 for http and 443 for https.
- URLs containing credentials (user:password@) are rejected.
- Loopback, private, link-local, multicast and cloud metadata addresses are blocked before any connection is made.
- Up to 5 redirect hops are followed, with a 15-second deadline for the whole chain.
- One URL per request, limited to 10 checks per 60 seconds per client IP.
What the checker does not return
The checker follows redirects like a diagnostic client, not a browser: it never returns the response body or headers, does not execute JavaScript or cookies, and never displays resolved IP addresses. Query strings are omitted from every URL shown in the chain.
Redirect checker FAQ
What do 301, 302, 307 and 308 mean?
301 and 308 are permanent redirects; 302 and 307 are temporary. The difference matters for SEO: permanent redirects pass ranking signals, temporary ones do not.
Can I check that http:// redirects to https://?
Yes. Enter the http:// version of your site: the chain shows whether it redirects to https:// and whether the final page answers successfully.
What happens with a redirect loop?
A loop cannot run forever: after 5 hops the check stops and returns WARNING with the chain collected so far, so you can see exactly where the loop starts.
Why do the shown URLs lose their query strings?
Query strings often contain tokens, emails or tracking values. They are stripped from every URL displayed in the result so nothing sensitive is echoed back to your screen.