How to use it
- Enter the complete non-www URL you want to test.
- Press Check to follow its redirects on the server.
- Verify the starting address shown as Target Evaluated.
- Compare the redirect count and final URL with the intended www destination.
- Inspect the final response details and use Copy Result.
The tool does not remove www automatically. Its synthetic browser fallback also cannot prove that the host redirect exists.
What is the purpose of the tool
Non-WWW Redirect Checker follows a root hostname to the effective destination returned by the server request. It can reveal whether the non-www variant reaches an intended www URL.
The report summarizes the final response rather than each hop. It does not parse the page for canonical markup.
What parameters it generates in output
| Field | Meaning | Healthy result |
|---|---|---|
| Target Evaluated | The normalized non-www starting URL. | It uses the intended root host. |
| Status badge | The final code with OK or Error text. | The destination returns the planned status. |
| Latency | Total request time in milliseconds. | It is acceptable for the redirect route. |
| Redirects | The number of followed responses. | It matches the intended host change. |
| Final Destination URL | The effective address after redirects. | It contains the correct www hostname. |
| Header | A parsed name from the final header block. | Required headers appear. |
| Value | The content paired with a final header. | It contains the expected directive. |
FAQs related to that specific tool
Does this checker remove www from my input?
No. Enter the non-www host explicitly because URL cleanup preserves the submitted hostname.
How can I confirm a redirect to www?
The report should show at least one redirect and a Final Destination URL containing the intended www hostname.
Does it display every intermediate URL?
No. Only the total redirect count and final destination are visible.
How many redirects can the server follow?
The request is limited to five redirects.
Why can the fallback appear successful?
The browser fallback generates a synthetic 200 and HTTPS report, so it cannot verify a real non-www to www redirect.
Does the tool inspect rel=canonical?
No. It requests response headers and does not parse HTML elements.