HTTP Status Code Checker Sample Report

This example shows the evidence returned for a direct success, a redirect, and an invalid input. Live reports preserve input order and include rows that were not tested.

Input	Status and destination	Redirect chain	Request evidence	Error or next step
`https://example.com/`	200 OK Final URL: `https://example.com/`	Direct response	Method used: HEADTime: 84 msCache status: miss	None
`http://example.com/`	200 OK Final URL: `https://example.com/`	1. 301 `http://example.com/` → `https://example.com/`	Method used: HEADTime: 122 msCache status: miss	Update internal links to the final HTTPS URL when practical.
`example dot com`	Not tested	None	Method used: —Cache status: not-tested	`invalid_url` Enter a complete URL beginning with `http://` or `https://`.

How to use the evidence

Redirect chain lists each observed hop and status before the final response.
Method used is normally HEAD. A bounded GET fallback is used when a server rejects HEAD or returns an unusable zero-status response.
Cache status distinguishes a fresh check from a recent cached result.
Error code and retry guidance distinguish malformed, duplicate, DNS, TLS, timeout, blocked-target, rate-limit, and network outcomes.

Limitations

This server-side check records the response observed from this tool. A CDN, firewall, geo rule, user-agent rule, or temporary outage can return a different result to another visitor or crawler. It does not determine whether a URL should exist or guarantee indexing.

Illustrative report only. Values above are examples, not a live test.