How to use it
- 1
Paste a full page address or a domain.
- 2
Run the check and wait for the WebDiag API response.
- 3
Review the final URL, response status, and unnecessary hops in the chain.
What the tool can do
- Final HTTP status after safe redirect handling.
- Each redirect hop: source URL, target URL, and status code.
- A compact summary of content-type, content-length, cache-control, and server header when present.
Common use cases
- Check whether an important landing page goes through unnecessary 301/302 hops.
- Find 404, 500, or temporary redirects in URLs that affect SEO and paid traffic.
- Verify the final URL after a domain, HTTPS, trailing-slash, or canonical redirect change.
How it works inside
The request runs through the WebDiag backend with SSRF protection, DNS/IP policy, and redirect limits.
The final response body is not downloaded for the tool result; status, headers, and redirect metadata are used.
Questions and answers
Why does this check run through the server instead of locally in the browser?
Browsers are limited by CORS and cannot reliably read another site's redirect chain and headers. The check therefore runs through the safe WebDiag backend.
Is this a bulk status checker?
No. This tool inspects one URL in detail. Use the separate bulk checker for a prepared list of up to 50 addresses.