FREE BROWSER TOOL
Check a small list of URLs for HTTP responses. Requests run directly from your browser; sites that block cross-origin access are reported as unknown, not assumed to be dead.
Paste up to 25 full http or https URLs, one per line.
Checks run from your browser. Sites that block cross-origin requests may show as unknown; URLs are not sent to a proxy.
A successful browser response is alive; HTTP errors are dead.
Results will appear here.
Enter up to 25 full HTTP or HTTPS URLs, one per line. Include the scheme so each address can be parsed correctly.
Select Check URLs. The tool sends a direct HEAD request from your browser to each address; the page does not relay the list through a proxy.
Review the HTTP response code and result label. Use unknown as a prompt to verify the URL with another method rather than treating it as a failure.
Alive means the browser could read a 2xx or 3xx HTTP response. Dead means it could read an HTTP response outside that range. Invalid means the line is not a valid HTTP or HTTPS URL. Unknown means the browser could not read a response, for example because the destination blocks cross-origin requests, the connection failed, or the request timed out.
Because browsers enforce cross-origin rules, a site may be reachable in a normal browser tab yet still appear unknown here. Some servers also do not support HEAD requests consistently. A browser-only checker cannot reliably determine availability for every host, and an unknown result is not evidence that a link is broken.
Use this tool for a quick spot check of a small list, then open surprising results directly or check them with a server-side monitoring tool you trust. Before changing a published link, confirm the target URL, redirect behavior, and whether access requires a login or special headers.
The checker processes up to 25 URLs per run and does not use a third-party proxy. This avoids handing your list to a proxy service, but means cross-origin restrictions can limit the results.
A browser can block JavaScript from reading a cross-origin response unless the destination allows it with CORS headers. The page may still open normally in a browser tab; unknown means the checker could not inspect the response.
It sends a HEAD request, which asks for response headers without downloading the page body. Some sites do not handle HEAD like GET, so verify unexpected results with another check.
No. Unknown means no readable HTTP response was available to this browser check. Network restrictions, CORS, timeouts, or server behavior can all cause it.
No. Requests are made directly by your browser to the URLs you enter. The destination site receives the request as it would for a browser-originated request.