HTTP Status Code Checker
Paste up to 15 URLs to check their HTTP status codes in parallel and see where redirecting URLs point.
About this tool
Checking links one by one is tedious; this tool sends up to fifteen requests in parallel through the APIVoid URL Status API and lists the status code, message and redirect target of each, plus a plain-text summary you can paste into a ticket. It is handy after a site migration, when cleaning up a sitemap, or when auditing links in a newsletter.
For a single URL with full response headers and body use the Web Sniffer; to expand short links safely use the Unshorten URL tool to reveal the destination before visiting.
How to use it — quick steps
- 01
Enter the urls to check
Type or paste the urls to check in the field above, one item per line. The lookup runs from our servers.
- 02
Press "Check URLs"
Press "Check URLs" or Ctrl + Enter. The result appears below in a few seconds. Results can be copied.
- 03
Read the result
It appears in the dark panel under the form in a few seconds. Every block has [copy] and other actions.
Key features of this tool
External lookups
The lookup runs from our infrastructure, so you see what the public internet sees without exposing your own IP address or network.
Fast and cached
Results come back in seconds; identical lookups are cached for a few minutes to keep the service fast and responsive for everyone.
Easy to reuse
Every result block can be copied with one click or downloaded as a text file, and tables can also be saved as CSV for your reports.
Frequently asked questions
What do the status codes mean?
2xx success, 3xx redirect (the target is shown), 4xx client error such as 404 not found or 403 forbidden, 5xx server error. "No response" means the connection failed or timed out.
Are redirects followed?
No: each URL is requested once so you see its own code and the Location it redirects to. Use Unshorten URL to follow a whole chain.
Why does a URL return 403 here but works in my browser?
Some sites block automated clients or require cookies. The check uses a regular desktop user agent, but bot protection can still refuse it.