Check HTTP status codes in bulk
Find successful 2xx responses, redirect chains, 4xx client errors and 5xx server errors. Filter the completed results to isolate broken URLs and inspect the response at each step.
FREE HTTP RESPONSE TOOL No signup
Free HTTP status code checker.
Check HTTP responses, inspect headers, and find failing URLs.
Test up to 1,000 URLs from the main server or a country you choose.
✓ Status codes & response headers◷ Last-Modified & ETag↓ CSV & JSON export
Check your URLs
01 / INPUT02 / RESULTS
Your HTTP status report
Preparing your checks…
Checked0
With redirects0
Need attention0
Profile differences0
| URL & destination | Status chain | Redirects | Time | Findings | Details |
|---|
Your first results will appear here. Large batches continue in the background.
Timings measure server-side HTTP requests, not browser page load. User-agent profiles do not reproduce a verified Googlebot visit. Exports include all results, including pending or cancelled checks.
STATUS CODES. HEADERS. EVIDENCE.
See what your server actually returns.
Inspect HTTP response headers
Search and copy headers including Content-Type, Location, Cache-Control, Last-Modified, ETag and X-Robots-Tag. Review DNS, connection and first-byte timing alongside each response.
Verify conditional responses
Test whether a successful response supports If-Modified-Since and If-None-Match. See when the server returns 304 Not Modified, resends unchanged content or returns a changed representation.
FROM ONE URL TO A BULK REPORT
Check a release.
Find broken pages.
Investigate a response.
Use the HTTP status checker after a deployment, during a site migration or when a page responds differently across devices or countries. A successful HTTP status is one signal; inspect the headers and final destination before deciding what to fix.
Investigating a redirect chain? →- Paste up to 1,000 URLs
Enter one URL per line. The checker normalizes addresses, removes fragments and checks each duplicate URL once. Optional HTTP/HTTPS and www variants count toward the same limit.
- Choose where the request runs
Main server is selected by default. Choose a country to use its probe server for the entire batch, including redirect hops and cache checks. Select a desktop, mobile or Googlebot user-agent profile, or compare desktop and mobile.
- Inspect the evidence and export
Sort by response status, redirect count or time. Open a result for its headers and findings, then download CSV for spreadsheets or JSON for the complete stored trace. Each result identifies its device profile and chosen probe location.
HTTP status checker questions, answered.
What is an HTTP status code checker?
It sends an HTTP request to a URL and reports the server's response status and headers. This tool uses GET requests, follows supported redirects and shows the intermediate responses as well as the final status. It can check up to 1,000 URLs in one batch without an account.
What do 200, 301, 404 and 500 mean?
200 OK indicates a successful request. 301 Moved Permanently points to a new URL. 404 Not Found means the server did not find the requested resource, while 500 Internal Server Error indicates an unexpected server failure. The checker also reports other returned statuses, including 302, 307, 308, 403, 429, 502 and 503.
Does HTTP 200 prove that a page is healthy?
No. A server can return 200 for a page that contains an error message, a login screen or the wrong content. A page can also have noindex directives or point its canonical elsewhere. This checker surfaces available evidence but does not determine every soft 404, content error or indexing issue.
How are HTTP headers and cache validators checked?
The report includes response headers for every collected hop. When a final response is 200 and caching validation is enabled, Last-Modified and ETag are tested with separate conditional GET requests. A 304 validates the cached representation. A 200 can mean the content changed or the validator was ignored; the report distinguishes these outcomes where the collected evidence allows.
Can I check responses from another country?
Yes. The Check from selector offers the main server and the available countries. Selecting a country pins the batch to its probe server. To compare countries, run the same URLs again with another selection and export both reports. Geographic routing, CDNs and access rules can affect responses.
Does it work exactly like a browser or Googlebot?
No. The checker sends HTTP GET requests with the selected user agent. It does not execute JavaScript, load page assets or reproduce a verified Googlebot visit. It follows HTTP redirects, HTTP Refresh and HTML meta refresh, and reports possible JavaScript navigation as an unconfirmed hint. Timings measure server-side HTTP requests, not full page load.
Can I download all HTTP status results?
Yes. CSV includes URLs, device profiles, probe countries and cities, status chains, timings, cache headers and findings. JSON includes the full stored trace. Both exports cover the whole batch, including pending or cancelled rows, regardless of the current table filter.
Are checks free and reports private?
Checks are free without signup, subject to batch and request limits. Reports are accessible only to the browser session that created them and expire after 24 hours. Only public HTTP/HTTPS URLs on standard ports are accepted; private addresses and unsafe redirect destinations are blocked. The checker inspects a bounded HTML sample and does not retain the raw page body.