Free tool Bulk URL status checker: HTTP codes for 50 URLs at once
Paste a list of addresses — from a migration sheet, a crawl export or a spreadsheet of campaign links — and get one row per URL: the status code, every redirect on the way, where it finally lands and how long it took. Filter to the 404s and 5xx errors, then download the table as CSV.
- Up to 50 URLs per run
- Redirect chains included
- CSV export
Check the status of many URLs
One URL per line. Lines without http:// get https://; duplicates and lines that are not URLs are reported, not checked. The table below is a dated sample until you click Check status.
check.tapcub.com, which requests the pages from Cloudflare’s network with a From: tools@tapcub.com header and returns status codes and the parts of the page this tool needs. The service keeps only host names, status codes and timings for rate limiting, not paths, queries or page content, and stores no results. Batch checks go out 8 addresses per request. The first one may ask for a quick human check (Cloudflare Turnstile); after that you have a 15-minute pass. Limits per IP address: 30 batch requests a minute and 150 a day.Copy a column from a spreadsheet as it is. Lines starting with # are ignored.
Some sites answer bots differently. The request still comes from Cloudflare’s network, not from Google’s or OpenAI’s addresses.
Only changes the table; the CSV always has every checked URL.
URLs
8
After removing duplicates and invalid lines.
2xx
4
Answered directly.
Redirected
2
Ended somewhere else.
4xx
1
Not found, gone, forbidden…
5xx
1
Server errors.
No response
0
Timeout, DNS or connection.
Summary
- WarningLine 9Not a URL: “not a url”.
- Note1 duplicate URL(s) removed (compared after adding https:// and ignoring #fragments).
- Error2 URL(s) return a 4xx or 5xx error.
- Warning2 URL(s) redirect. Update links and sitemaps to point to the final URL.
Results
Hover a long URL to see all of it. Times include every redirect.
| # | URL | Status | Final URL | Redirects | Time |
|---|---|---|---|---|---|
| 1 | https://www.wikipedia.org/ | 200 | Same | 0 | 1.2 s |
| 2 | http://wikipedia.org/ | 301 → 301 → 200 | https://www.wikipedia.org/ | 2 | 4.4 s |
| 3 | https://en.wikipedia.org/wiki/HTTP_404 | 200 | Same | 0 | 1.3 s |
| 4 | https://en.wikipedia.org/wiki/This_page_does_not_exist_2026 | 404 | Same | 0 | 1.6 s |
| 5 | https://httpbin.org/status/500 | 500 | Same | 0 | 1.0 s |
| 6 | https://httpbin.org/redirect/2 | 302 → 302 → 200 | https://httpbin.org/get | 2 | 1.5 s |
| 7 | https://example.com/ | 200 | Same | 0 | 1.1 s |
| 8 | https://github.com/ | 200 | Same | 0 | 2.1 s |
url,status,class,chain,final_url,redirects,time_ms,content_type,error
https://www.wikipedia.org/,200,ok,200,https://www.wikipedia.org/,0,1185,text/html,
http://wikipedia.org/,200,ok,301 → 301 → 200,https://www.wikipedia.org/,2,4415,text/html,
https://en.wikipedia.org/wiki/HTTP_404,200,ok,200,https://en.wikipedia.org/wiki/HTTP_404,0,1327,text/html; charset=UTF-8,
https://en.wikipedia.org/wiki/This_page_does_not_exist_2026,404,4xx,404,https://en.wikipedia.org/wiki/This_page_does_not_exist_2026,0,1570,text/html; charset=UTF-8,
https://httpbin.org/status/500,500,5xx,500,https://httpbin.org/status/500,0,1016,text/html; charset=utf-8,
https://httpbin.org/redirect/2,200,ok,302 → 302 → 200,https://httpbin.org/get,2,1542,application/json,
https://example.com/,200,ok,200,https://example.com/,0,1089,text/html; charset=utf-8,
https://github.com/,200,ok,200,https://github.com/,0,2056,text/html; charset=utf-8,One row per checked URL, including the full redirect chain.
Version v1.0Updated Update history
What each status class means
The first digit tells you who has to act: nobody, your redirects, your links, or your server.
2xx: fine
The server answered with the page. 200 is the normal case; 204 or 206 are rare for web pages and worth a second look.
3xx: redirected
The “Status” column shows the whole chain, such as 301 → 200, and “Final URL” where it ends. Redirects work, but every link and sitemap entry pointing at the old address costs a hop. Two or more hops are worth flattening.
4xx: the address is wrong
404 Not Found and 410 Gone mean the page is not there. 401 and 403 mean it exists but refuses this request — often a login wall or a firewall rule for unknown clients. 429 means you were rate limited.
5xx and no response: the server
500, 502, 503 and 504 are server-side failures; Google slows crawling when it sees them repeatedly. “No response” means the request never got an HTTP answer: unknown domain, timeout after 8 seconds or a refused connection.
This tool asks with HEAD first (just the headers) and retries with GET when a server rejects HEAD with 405 or 501. A few servers answer HEAD and GET differently; if one result looks wrong, open that URL in a browser or check it with the redirect checker.
Three steps
No sign-up. Each run checks up to 50 URLs.
-
1
Paste the list
One URL per line: a column from a spreadsheet, a sitemap export or the old URLs of a migration. Invalid lines and duplicates are listed above the table.
-
2
Choose how to ask
Keep Chrome for the normal view. Switch to Googlebot or Bingbot to spot sites that treat crawlers differently, or turn off redirects to see the first response only.
-
3
Check, filter, export
Click Check status. Use “Show” to focus on errors or redirects, and download the CSV for your migration sheet or ticket.
One request per URL, from Cloudflare’s network
Your browser cannot read another site’s status codes (cross-origin rules hide them), so the list goes to TapCub’s checking service, which asks each server and reports back.
- Lines are cleaned: list markers and quotes removed, https:// added when missing, #fragments dropped, duplicates merged
- The list is sent in groups of 8; each URL is requested with HEAD, and with GET if the server answers 405 or 501
- Redirects are followed up to 3 hops per URL; a redirect to a raw IP address or a local host name is not followed
- Timeout is 8 seconds per request. “Time” is the total for the URL, redirects included, measured from Cloudflare’s network rather than your connection
- Addresses that resolve to private or reserved networks, raw IP addresses and TapCub’s own service hosts are not requested
| Code | Meaning | What to do |
|---|---|---|
| 200 | OK | Nothing |
| 301 / 308 | Moved permanently | Update links and sitemaps to the final URL |
| 302 / 307 | Moved temporarily | Fine for short-term moves; use 301 if it is permanent |
| 403 | Forbidden | Often a bot firewall; open it in a browser to confirm |
| 404 / 410 | Not found / gone | Restore the page, redirect it, or remove the links |
| 429 | Too many requests | Rate limited; check again later |
| 500 / 502 / 503 | Server error | Look at server logs; repeated errors slow crawling |
The sample list, checked on 2026-11-17
Ten lines, of which eight are checked: “not a url” is rejected and example.com/ is the same address as https://example.com once normalised.
| URL | Status | Reading |
|---|---|---|
http://wikipedia.org | 301 → 301 → 200 | Two hops: http → https, then the bare domain → www |
…/wiki/HTTP_404 | 200 | An article about 404 errors is itself a normal page |
…/wiki/This_page_does_not_exist_2026 | 404 | Missing article: a real 404, not a soft 404 |
httpbin.org/status/500 | 500 | A test endpoint that always fails on purpose |
httpbin.org/redirect/2 | 302 → 302 → 200 | Temporary redirects ending at /get |
example.com, github.com, www.wikipedia.org | 200 | Answer directly |
Totals: 4 direct 200s, 2 redirected, one 404 and one 500. Times depend on where Cloudflare’s network reached each server from, so they vary between runs.
Where bulk checks mislead
A status code is the server’s answer to one request, not the whole truth about a page.
Reading 403 as “broken”
Many sites block unknown clients or data-centre addresses. If a 403 page opens fine in your browser, the page is not broken; the firewall is just strict.
Trusting a 200 blindly
A “soft 404” shows “page not found” text with a 200 status. Google treats it as an error anyway. Open suspicious 200s, or check titles with the sitemap checker.
Stopping at “it redirects”
A redirect that ends in a 404 is still broken. Keep “Follow redirects” on and read the last code in the chain.
Checking the wrong variant
http and https, www and bare domain, with and without a trailing slash are different URLs. Check the exact form your links and sitemap use.
Find broken pages from real visits, not just lists
A bulk check covers the URLs you already know about. Analytics shows the ones people actually hit.
404s with their source
Broken internal links show up as 404 visits together with the page that sent people there.
Learn moreCrawlers kept apart
Search engines and AI crawlers are counted separately from people, so a crawl spike does not look like traffic.
Learn moreSearch performance
Google Search Console and Bing Webmaster data next to your pages, to see whether a broken redirect cost clicks.
Learn moreBulk status check questions
Still have a question?
Chat with the team behind TapCub — we usually reply within a few hours on business days.
How do I check the HTTP status of many URLs at once?
Paste them above, one per line (up to 50), and click Check status. Each row shows the status code, the redirect chain, the final URL and the time taken; the CSV download has the same data for a spreadsheet.
Why does a page show 403 here but open in my browser?
The site is blocking automated requests or requests from cloud networks. That is a firewall decision, not a missing page. Try “Request as” Chrome (the default), and confirm in a browser.
Does this tool follow redirects?
Yes, up to 3 hops per URL, and the Status column lists every code on the way (for example 301 → 200). Turn off “Follow redirects” to see only the first response. Google’s own crawler follows up to 10 hops, but long chains are worth fixing anyway.
Why HEAD and not GET?
HEAD returns only headers, so a check is fast and does not download the page. Servers that do not support HEAD (405 or 501) are asked again with GET automatically.
Can I check more than 50 URLs?
Not in one run. Split the list into parts of 50; each run uses about 7 batch requests, and the daily limit is 150 batch requests per IP address. To check every URL in a sitemap, use the sitemap checker, which reads the file for you.
Is “Googlebot” here the real Googlebot?
No. Only the user-agent text changes; the request comes from Cloudflare’s network and says it is from tools@tapcub.com. Sites that verify Googlebot by IP address will treat it as an impostor, which is itself useful to know.
Are my URLs stored?
No. The service logs only host names, status codes and timings for rate limiting. Results stay in your browser tab, and this tool has no share link.
Update history
New features, fixes and data refreshes for this tool, newest first.
-
· v1.0
LaunchedFirst release.
Data this tool relies on
- Sample batch, sitemap, link and tracking checks — checked 2026-11-17, reviewed every 6 months (next review by 2027-05-17)
Missing something or found an error? Tell us — requests that come up often go into the next update. All tool updates
Catch the broken links people actually click
TapCub records 404 visits with the page that linked to them, so you fix what visitors hit first.