How browser-based status checks work
This check runs straight from the browser, so it is quick but limited by whatever cross-origin rules the target sets.
If the server blocks browser access, the page points that out and gives you a curl fallback.
Send a lightweight browser request to a public URL and inspect status, headers, redirect target, or CORS limitations.
Requests run from the browser. Some URLs block cross-origin access, so a curl fallback is included when that happens.
Yes.
Many servers block cross-origin browser requests. When that happens, the page gives you a curl fallback instead.
Not reliably. It works best with public URLs that allow browser access.
No. The page does not send your input to a custom backend.
This check runs straight from the browser, so it is quick but limited by whatever cross-origin rules the target sets.
If the server blocks browser access, the page points that out and gives you a curl fallback.
For private APIs, authenticated endpoints, or real monitoring, you will eventually want something server-side.
This version stays lightweight on purpose so you can do a quick public check without setting up anything heavier.
These pages are meant to stay direct: input at the top, results immediately below, then the FAQ and related guides if you need more context.