HTTP Status Checker
Check HTTP status codes, redirect chains and server responses for multiple URLs.
Based on: RFC 9110 — HTTP Semantics · RFC 9111 — HTTP Caching
About this validation
Checks HTTP responses, redirects, and response metadata using standard HTTP semantics.
- Protocol / standard:
- Rules reviewed:
- Aug 31, 2026
Standards and vendor-documented behavior can change. This reflects the source as last reviewed above, not a permanent guarantee.
Enter one URL per line.
What is an HTTP Status Code Checker?
An HTTP status code checker sends real requests to one or more URLs and reports the status code, redirect chain, and key response headers the server returns. It's used to confirm a page resolves correctly, trace how redirects behave, and spot differences in how a server responds to different clients.
HTTP Status Code Categories
1xx — Informational
The request was received and the server is continuing the process.
2xx — Success
The request was successfully received, understood, and accepted.
3xx — Redirect
Further action is needed to complete the request, usually a redirect to another URL.
4xx — Client Error
The request contains bad syntax or cannot otherwise be fulfilled by the client.
5xx — Server Error
The server failed to fulfill an apparently valid request.
Common HTTP Status Codes
OK
The request succeeded and the server returned the requested content.
Moved Permanently
The resource has permanently moved to a new URL given in the Location header.
Found
The resource is temporarily at a different URL. The original URL should keep being used for future requests.
Temporary Redirect
The resource is temporarily at a different URL. Unlike 302, the request method must not change.
Permanent Redirect
The resource has permanently moved. Unlike 301, the request method must not change.
Not Found
The server could not find the requested resource.
Gone
The resource previously existed but has been permanently removed, with no forwarding address.
Too Many Requests
The client has sent too many requests in a given amount of time (rate limiting).
Internal Server Error
The server encountered an unexpected condition that prevented it from fulfilling the request.
Bad Gateway
The server, acting as a gateway or proxy, received an invalid response from an upstream server.
Service Unavailable
The server is currently unable to handle the request, often due to maintenance or overload.
HTTP Redirect Checker
When a URL redirects, this tool follows the chain hop by hop instead of only reporting the final response. Each result can be expanded to see every intermediate URL, its status code, and the Location header that pointed to the next hop — useful for spotting unnecessarily long chains, protocol downgrades, or loops.
Check URLs as Googlebot
Selecting a Googlebot User-Agent sends the request with Google's published crawler identifier string. This changes what the destination server sees in the User-Agent header — it does not make the request originate from Google's infrastructure, and it is not a way to verify genuine Googlebot traffic.
Check AI Crawler User-Agents
GPTBot, ChatGPT-User, ClaudeBot, and PerplexityBot serve different purposes for their respective companies and are not equivalent to each other. This tool only tests how a server responds when one of these User-Agent strings is supplied — it does not verify that a request actually originates from OpenAI, Anthropic, or Perplexity infrastructure.
FAQ
What is an HTTP status code?
An HTTP status code is a three-digit number a server returns with every response, indicating whether the request succeeded, was redirected, or failed.
Can I check multiple URLs?
Yes. Paste up to 50 URLs, one per line, and they are checked with limited concurrency so results come back progressively.
Does the checker follow redirects?
Yes, by default. You can turn this off in Options to see only the first response, or adjust the maximum number of redirects followed.
Can I check a URL as Googlebot?
Yes. Selecting Googlebot Smartphone or Googlebot Desktop sends the request with Google's published crawler User-Agent string. This does not verify the request as genuine Googlebot traffic — it only tests how the server responds to that header.
Why does Googlebot receive a different status code?
Servers, CDNs, and WAFs can be configured to respond differently based on the User-Agent header. This can be intentional (e.g. mobile-specific rendering) or a sign of bot-blocking rules worth reviewing.
What does 301 → 200 mean?
The requested URL responded with a 301 permanent redirect, and the destination it pointed to returned a 200 OK. The chain shows every hop between the original URL and the final response.
What is the difference between 301 and 302?
301 (Moved Permanently) signals a permanent move; 302 (Found) signals a temporary one. Clients and crawlers may treat cache and link-equity handling differently for each.
What does HTTP 403 mean?
403 Forbidden means the server understood the request but refuses to authorize it — often due to permissions, IP blocking, or bot protection rules.
What does HTTP 429 mean?
429 Too Many Requests means the server is rate-limiting the client. Repeated automated requests are a common cause.