HTTP Status Checker
Check HTTP status codes, redirect chains, and response headers for multiple URLs at once.
Everything You Need to Audit URLs
A complete HTTP inspection tool for developers, SEOs, and site owners.
Bulk URL Check
Paste up to dozens of URLs at once and get status results for all of them in a single request.
User-Agent Selection
Simulate requests from Google, Bing, Chrome, or a custom user-agent to see how servers respond.
Redirect Chain Detection
See every hop in a redirect sequence — including intermediate 301s and 302s — with timing per hop.
Response Headers
Inspect the full set of HTTP response headers returned by the server for each URL.
CSV Export
Download all results as a CSV file with status code, redirect count, timing, and final URL.
Fast Concurrent Requests
All URLs are checked concurrently on the server side so even large batches return quickly.
How It Works
Check HTTP status codes in three simple steps.
Enter URLs
Type or paste one or more URLs into the input box — one per line. Enable canonical check to test all 4 domain variants.
Click Check
Choose your preferred User-Agent if needed, then click Check Status. All URLs are fetched concurrently.
View Results
See status codes for each hop, expand any row for the full redirect timeline with headers and latency.
HTTP Status Code Quick Reference
The most common status codes you will encounter when checking URLs.
Related Tools
Other tools to help you inspect and debug web requests.
Frequently Asked Questions
Common questions about HTTP status codes and how to use this tool.
What do HTTP status codes mean?
HTTP status codes are three-digit numbers returned by a web server to indicate the result of a request. Codes in the 2xx range (like 200) mean success. 3xx codes indicate redirects. 4xx codes signal client errors such as a missing page (404) or unauthorized access (403). 5xx codes indicate server-side errors.
What is the canonical domain check?
The canonical domain check tests all 4 variants of your domain — http://domain.com, https://domain.com, http://www.domain.com, and https://www.domain.com — to verify they all redirect to a single canonical URL. This is important for SEO because search engines treat each variant as a different page.
How does redirect chain detection work?
When a server responds with a 3xx redirect, the checker follows the Location header to the next URL and records the status, timing, and headers at each step. This continues until a final non-redirect response is received, giving you a complete map of every hop in the chain.
Why does the User-Agent selection matter?
Some servers return different responses depending on the User-Agent of the requester. For example, a site may redirect bot traffic differently than browser traffic, or block certain crawlers entirely. Selecting a specific User-Agent lets you see exactly how the server responds to that client type.