Bulk URL Checker
Check up to 20 URLs at once.
Checked from our server. One location, so results show reachability from there only.
What the bulk URL checker does
Checking a list of sites one at a time is slow. The bulk URL checker takes up to 20 addresses at once, runs a full reachability check on each from our server and gathers the answers in one table.
It suits anyone who looks after several websites: an agency confirming every client site is back after a hosting incident, a developer checking all the domains on a server after renewing certificates, or anyone tidying up a list of old links. Each result links to a detailed page you can share with a colleague or your host.
How to use the bulk URL checker
- Paste up to 20 addresses, one per line. Blank lines and duplicates are ignored.
- Press Check all. They are checked a few at a time and the table fills in as results arrive.
- Open Full result on any row for the layer-by-layer details and a shareable link.
Understanding the results
Each row gets a result. Reachable means the server answered with a working page, or refused our automated request with a code such as 403, which still shows it’s online. Problems means it answered but something is wrong: an error code, a failing certificate, a reply that took more than three seconds to start or too many redirects. Unreachable means the name didn’t resolve, the connection failed or the server didn’t answer in time. Blocked means the site or one of its redirects points at a private network, so we stopped. Unclear covers unusual responses.
The HTTP column shows the final status code, and Time shows how long the request took in milliseconds. Details repeats the summary for that site. When the run finishes, the line above the table tells you how many sites were reachable from our server.
Questions
How is each site checked?
With the same layered check as the Website Down Checker: DNS, connection, certificate, HTTP, redirects and page content. Checks run from our server, in one location, so results show what that location sees.
Why does a result say “Not checked”?
The address was refused before any request was made. It may not be a valid web address, it may use a port other than 80 or 443, or it may point at a private network.
Why does a row say “Error”?
That check couldn’t be completed. It failed on our side, the request ran out of time before reaching that address, or our server was busy with many checks from your network. Run the list again to retry.
Are results saved?
Yes. Each check is stored so you can share its result page. If a site’s home address was checked moments earlier – within 60 seconds when it was reachable, or 30 seconds when it wasn’t – you get that saved result rather than a new check. An address with a path, such as example.com/shop, is checked on its own, and that result isn’t reused for anyone else.