WEB & TLS
HTTP Status Check
Request a public website safely and report status code, final URL, redirect chain and connection timing.
39DExternal testRuns from the toolbox server
RUN TEST
HTTP Status Check
HOW IT WORKS
About the HTTP Status Check
The request follows a small number of redirects manually. Every destination is revalidated and pinned to a public resolved address to reduce server-side request forgery and DNS-rebinding risks.
How to use this result
- Run the test from this server.Use a public hostname, address, prefix or ASN in the format requested above.
- Compare with another observation point.Run a local command or use a second provider to identify location-specific behaviour.
- Correlate related evidence.Use the related tools below to compare DNS, routes, ports, TLS and application responses.
- Keep the time and context.Routing, DNS caches and reputation data change, so record when the result was collected.
Common interpretation issues
- A server may return different content based on location or user agent.
- A successful TCP connection does not guarantee a useful application response.
- Redirect loops and certificate failures are reported as errors.
NEED HELP INTERPRETING THE RESULT?
39D supports business networks, cyber security and managed IT.
For ongoing support or a larger infrastructure project, speak to the 39D team.
Frequently asked questions
Does the check download the whole page?
The status tool uses a lightweight request where possible and enforces strict limits.
Can it test private dashboards?
No. Public installations block private, loopback, reserved and link-local destinations.