Inspect a public website's HTTP redirect chain and response status.
Checks are performed by Roled's server using HTTP HEAD, not by your own browser.
Your complete URL, including query values, is submitted to Roled and used for requests to the target website. Do not enter private URLs, tokens or personal data. Fragments are removed from outbound requests. Results are not saved as a tool history; infrastructure access/security logs may still record request metadata.
Enter a public URL
Include http:// or https://. Public DNS hostnames only, using HTTP port 80 or HTTPS port 443. No credentials, IP literals or internal addresses. Maximum 2,048 ASCII characters; use percent encoding for non-ASCII paths and queries.
Reset or editing ignores old browser results. It does not prove that server-side work was cancelled. Requests are rate limited and are never retried automatically.
Observed redirect results
Full URL query values are visible here. A next destination is not proof of contact: only rows with an observed HTTP response were checked. A blocked or limited chain is incomplete.
Copy omits query and fragment values by default. This does not remove query values from actual server requests. Paths can also contain sensitive information; review before sharing.
What this check can tell you
This is an IPv4-only server snapshot, limited to five redirects and six HEAD responses. HEAD may differ from browser GET; 405 or 501 can indicate that HEAD is restricted. There is no automatic GET retry.
Automated-request policies, firewalls and geographic routing can change observations. Cookies, authenticated sessions, HTML meta refresh and JavaScript navigation are not reproduced. A missing public A record does not prove that a website is offline.
A successful response is not a security, accessibility or SEO assessment, or proof of universal availability. Reset and page exit clear page-held results, without promising secure memory erasure or isolation from other page scripts/extensions.