How to use HTTP Status and Redirect Checker
- Enter a public HTTP or HTTPS URL without login details or a custom port.
- Complete the challenge and select Check status and redirects.
- Inspect each HEAD status, validated destination and allowed headers; query strings are redacted.
Example: HTTP Status and Redirect Checker
Follow checked public redirects and inspect response metadata.
Supported inputs and limits
- Your entered URL is sent to this site and its isolated metadata worker.
- Only public HTTP port 80 or HTTPS port 443 is supported, without URL credentials, cookies or custom headers.
- Every hop is freshly resolved through Cloudflare DNS over HTTPS; all resolved addresses must be public and actual connections are pinned to a validated address while retaining Host/SNI and TLS verification.
- At most five redirects, 16 KiB response headers per hop and 15 seconds per task.
- HEAD is used; response bodies and Set-Cookie are not retained.
More details
Query strings are redacted in reports.
Human verification, session ownership, queue bounds and 15 minute private metadata expiry apply.
Results describe this worker’s vantage point, not every visitor’s browser.
Where your input is processed
The entered public target is sent to this site and a separate restricted metadata worker after human verification. DNS uses the disclosed Cloudflare resolver. The checked service receives only the fixed metadata probe, with no browser cookies or custom headers. Job access expires after 15 minutes. The worker and an independent scheduled app cleanup remove expired metadata; if both are offline, deletion waits for recovery.
Questions about HTTP Status and Redirect Checker
Why might a browser GET show another HTTP status?
This worker uses HEAD with fixed harmless headers and no cookies. Some servers handle HEAD differently, and authenticated browser visits can also differ.
How are redirect destinations checked?
Each hop is parsed and freshly resolved. Every resolved address must pass the public-address policy, and the connection is pinned to a validated address.
Are response pages or cookies retained?
The check collects only bounded response metadata. It discards bodies and Set-Cookie values, and redacts URL query strings from the report.