About HTTP Status Code Checker
Use this HTTP status code checker after a site move, a cleanup or a batch of new pages. Paste the old URLs to confirm they answer 301, check that deleted pages return 404 or 410, or catch pages that suddenly throw a 500. Put one address per line. Visitors can check 20 at a time, free members 50 and VIP 200, and eight are tested at once.
Each row shows the first status, the final status and address, the number of redirects and the time. When there's no answer, the error says why: the name doesn't resolve, the connection timed out or was refused, or TLS failed. Under Visit as, choose a desktop or phone browser, Googlebot, Googlebot smartphone, Baiduspider, Baiduspider mobile or Bingbot, since some servers answer crawlers differently. Addresses link to the Redirect Checker, or to Is It Down? when they fail, and the table exports as CSV.
How to use HTTP Status Code Checker
- 1Paste your URLs
One address per line, up to 20 for visitors, 50 for free members and 200 for VIP.
- 2Choose Visit as
Keep Desktop browser, or switch to a phone, Googlebot, Baiduspider or Bingbot.
- 3Click Check
Our server tests the addresses eight at a time and returns one table.
- 4Read and export
Scan the Final status and Error columns, then copy the table or save it as CSV.
Why use Cubfile for this
- Bulk lists
20, 50 or 200 URLs per run depending on your plan, checked eight at a time.
- Seven user agents
Desktop and phone browsers, Googlebot, Googlebot smartphone, Baiduspider, Baiduspider mobile and Bingbot.
- First and final status
The 301 or 302 a URL starts with, the page it lands on and how many hops it took.
- Errors named
DNS failures, time-outs, refused connections and TLS errors are spelled out, not left blank.