Network & Domain

URL Status Checker

Check an HTTP or HTTPS URL’s status, content type, and size.

Read the guide

Run the tool

JVR Software’s server processes the public target you enter. The diagnostic is rate-limited. Use a system you own or are authorised to check.

More information

Back to the tool

What it is and when to use it

URL Status Checker reports how a public HTTP or HTTPS resource responded to a request from JVR Software. Use it to verify a moved document, confirm a public endpoint's reachability, or work out whether a suspected page failure is a 404, a permissions response or a server error.

How it works

The tool performs a bounded GET request with a small redirect limit and no account credentials. It reports the returned HTTP status, content type, elapsed time and a response length. If no Content-Length header is present, that length comes from the response bytes the tool was able to read.

How to use it

  1. Paste the full public URL including https:// and the exact path.
  2. Run the check and note both the status and content type.
  3. Use Redirect Trace if you need to see intermediate redirects, or inspect the rendered page if the response is 200 but content appears wrong.

Worked example

A document's URL might report 200 with text/html when you expected application/pdf. The address is reachable, but the file endpoint could be returning an HTML error, landing page or login prompt. Check the content before linking it publicly.

Reading the result

Status 2xx normally means the HTTP request was fulfilled. A 403 can be a permission or traffic rule, and 404 means the requested resource was not found by the responding server. A 5xx indicates a failure while handling the request or reaching an upstream service.

For a moved article, record the old response and final destination as separate facts. If the result reaches a 200 page with the wrong title or a soft error message, fix the routing or page itself. An HTTP success status confirms that an endpoint responded successfully at the protocol level.

Common mistakes and limits

The elapsed time is from JVR Software and does not include browser rendering or JavaScript. WAFs can respond differently to automated requests. A 200 alone says nothing about correct content, indexability or the health of a logged-in experience. Check those separately.