Checking Whether a List of URLs Is Up
Paste up to 20 URLs, one per line, and each one is requested from our server right now. For every URL you get the HTTP status code, the total response time, and a plain up or down verdict. Nothing is cached, so the result reflects the moment you pressed the button.
It is a snapshot, not monitoring. It answers “is this working now?” for a batch of URLs at once — after a deployment, during a migration, or when someone says the site is down and you want to know whether it is down for everyone.
How to Use This Tool
Paste your URLs
One per line, up to 20. Include https:// so the check requests exactly the address you mean.
Run the check
Each URL is requested in turn, following redirects to its final destination.
Read the results
Status code, response time and up or down for each URL. Anything that did not respond at all shows the reason instead of a code.
What Counts as Up and Down
A URL counts as up when the final response has a status code from 200 to 399 — the page loaded, or it redirected somewhere that answered. It counts as down when the server returned an error code, or when it could not be reached at all within the time limit.
Redirects are followed, so an old URL that 301s to a working page shows as up. If you need to see each hop in the chain, run that URL through the Redirect Checker.
HTTP Status Codes You Will See
- 200 OK — the page loaded normally.
- 301 and 308 — permanent redirects; the result shown is for wherever they lead.
- 302 and 307 — temporary redirects, fine for short-term moves but not for permanent URL changes.
- 403 Forbidden — the server refused the request. Often a firewall or bot protection rather than a broken page.
- 404 Not Found — the URL does not exist. Expected for deleted pages; a problem for anything linked or in your sitemap.
- 410 Gone — the page was removed on purpose; search engines drop it faster than a 404.
- 429 Too Many Requests — the server is rate-limiting. Wait and try again.
- 500 Internal Server Error — the application crashed while building the page.
- 502 Bad Gateway and 504 Gateway Timeout — a proxy or CDN could not get an answer from the server behind it.
- 503 Service Unavailable — overloaded or in maintenance mode. Temporary by definition.
Is It Down for Everyone or Just Me?
If a site will not load for you but shows as up here, the problem is almost certainly on your side: your connection, your DNS resolver, a browser extension, a corporate firewall or a cached error page. Try another network — mobile data is the quickest test — or flush your DNS cache.
If it shows as down here as well, the site has a genuine problem, or it blocks requests from data centres. This check runs from one server location, so it cannot tell you whether a site is down in one country and up in another; for that you need a service that tests from many regions.
Reading Response Times
The response time is the total time to receive the response headers, including any redirects. It is measured from our server, so it reflects the distance between our server and the site as well as how fast the site is.
Use it for comparisons within one check rather than as an absolute figure. A page that takes three seconds while the rest take 300 milliseconds is worth investigating. For real-world speed as users experience it, the Core Web Vitals Checker reports field data from Chrome visitors.
When a Bulk Status Check Is Useful
- After a deployment — spot-check your most important URLs still resolve.
- Before and after a migration — confirm old URLs redirect and new URLs are live.
- Auditing a sitemap or backlink export for dead URLs.
- Confirming a fix — rerun the list after the server is back to make sure everything recovered.
- Comparing response times across a handful of templates.
A Status Check Is Not Uptime Monitoring
Monitoring means checking on a schedule, from several locations, and alerting someone when a URL fails. This tool does none of that: it checks once, when you ask. If an outage would cost you money, set up a monitoring service that checks every minute or so and notifies you, and use this tool for ad-hoc checks and investigations.
Frequently Asked Questions
Why does a URL show as down when it works in my browser?
Most often the site blocks automated or data-centre traffic, which shows up as a 403 or a timeout here while real visitors get through. Sites that need cookies or JavaScript before serving a page can also fail a plain server-side request.
How many URLs can I check at once?
Up to 20 per check, which keeps each run fast. For a longer list, split it into batches of 20.
Does it follow redirects?
Yes. The status and response time shown are for the final destination, and a URL that redirects to a working page counts as up. The Redirect Checker shows every hop if you need them.
Is a 403 or 429 a sign my site is broken?
Not necessarily. Both usually mean the server chose not to answer an automated request — a firewall, bot protection or rate limit. Check the same URL in a normal browser before treating it as an outage.
Does this check the site from multiple countries?
No. Every request comes from one server location, so it cannot detect a regional outage or a CDN problem that only affects some countries.