Free tool · HTTP
HTTP Status Checker
Check one URL or bulk-test up to 20 at once. See status codes, response times, and redirects.
| URL | Status | Time | Redirect |
|---|
How to check HTTP status codes online
Enter a URL above and this HTTP status code checker sends a request from our server, not yours. You get back the status code, response headers, redirect chain, and timing breakdown. A 200 means it worked. A 301 or 302 means the URL forwards somewhere else. A 404 means gone. A 500 means something broke server-side. That three-digit number is where every debugging session starts.
These response codes shape how search engines crawl your pages and whether API integrations hold together. Persistent 404s signal Google to drop pages from the index. Redirect chains slow down page loads and bleed link equity with each hop. Need to test more than one URL? Switch to Bulk Check and run up to 20 at once.
Bulk HTTP status checker for SEO audits
After you migrate a site, checking one URL at a time doesn't cut it. You've got hundreds of old URLs that need to 301-redirect to new locations, and any that return 404 or 302 instead of 301 will cost you rankings within days. The bulk mode takes up to 20 URLs, checks them in parallel, and shows status codes, response times, and redirect targets in a single table. Export the results as CSV for your spreadsheet.
We built the bulk checker because the question kept coming up: "how do I verify all my redirects after a migration?" The curl one-liner works (curl -o /dev/null -s -w "%{http_code}" URL), but it runs sequentially and doesn't capture the redirect target. Our bulk HTTP status checker fires five requests in parallel, streams results as they arrive, and logs where each redirect actually lands. For sites with hundreds of URLs to check, pair this with the redirect chain checker to trace every hop in the chain.
301 vs 302 redirects: when to use which
More sites get this wrong than any other redirect decision. The short version: 301 is permanent, 302 is temporary. But the SEO implications run deeper.
A 301 tells search engines to transfer all ranking signals to the new URL. The old URL gets dropped from the index. Use 301 when you've permanently moved a page: when you move domains, restructure URLs, or merge duplicate content. Google processes 301s within days and the new URL inherits the old one's rankings. Usually.
With a 302, search engines keep the original URL's ranking intact. The problem: many sites use 302 when they mean 301. We see this constantly in our monitoring data. A "temporary" redirect that's been in place for two years. Google eventually figures it out, but "eventually" can mean months of split ranking signals. If the move is permanent, use 301. Period.
There's also 307 (temporary, preserves HTTP method) and 308 (permanent, preserves method). These matter for API endpoints where POST requests need to stay POST after the redirect. For regular web pages, 301 and 302 cover almost every case.
When to check URL status codes
Deployments break things. A quick status check right after a push confirms your endpoints return 200 instead of 502 or 503. If a third-party service starts returning errors, this tool confirms the issue is on their end before you spend an hour debugging your own code. Developers working with webhooks use it to verify callback URLs are reachable and returning the expected response codes.
The tool also shows response time and headers, useful for diagnosing slow responses, bad caching, or missing security headers without opening dev tools. For deeper latency breakdown, try the response time tester. To inspect all headers in detail, use the HTTP headers checker.
HTTP status code list: complete reference
Every HTTP response code you're likely to encounter, grouped by category. These are defined in RFC 9110 (HTTP Semantics) and the Cloudflare-specific codes at the end. Click any code to jump to its description.
1xx Informational
| Code | Name | What it means |
|---|---|---|
100 | Continue | Server received the request headers. The client should send the body. Used for large uploads. |
101 | Switching Protocols | Server is switching to the protocol the client requested (usually WebSocket). |
102 | Processing | Server received the request and is working on it, but no response yet. Prevents timeout on slow operations. |
103 | Early Hints | Server sends preliminary headers (like preload links) while still preparing the full response. Speeds up page loads. |
2xx Success
| Code | Name | What it means |
|---|---|---|
200 | OK | The request succeeded. This is the normal response for a working page. |
201 | Created | A new resource was created. Typical response after a successful POST to an API. |
202 | Accepted | Request received but not yet processed. Used for async operations like queued jobs. |
204 | No Content | Request succeeded, but there's nothing to send back. Common for DELETE requests. |
206 | Partial Content | Server is sending part of the resource. Used for resumable downloads and video streaming. |
207 | Multi-Status | Response contains multiple status codes for different sub-requests (WebDAV). |
3xx Redirection
| Code | Name | What it means |
|---|---|---|
301 | Moved Permanently | The URL moved permanently. Search engines transfer ranking to the new URL. Use for domain migrations and permanent URL changes. |
302 | Found | Temporary redirect. The original URL keeps its ranking. Use when the redirect is genuinely short-term. |
303 | See Other | Redirects to a different URL using GET. Used after form submissions to prevent duplicate POSTs on refresh. |
304 | Not Modified | Browser cache is still valid. The server didn't send new content, saving bandwidth. |
307 | Temporary Redirect | Like 302, but guarantees the HTTP method stays the same. POST stays POST. |
308 | Permanent Redirect | Like 301, but guarantees the HTTP method stays the same. Important for API endpoints. |
4xx Client Error
| Code | Name | What it means |
|---|---|---|
400 | Bad Request | The server can't process the request due to malformed syntax. Check your query parameters or request body. |
401 | Unauthorized | Authentication required. The request lacks valid credentials. Not the same as 403. |
403 | Forbidden | Server understood the request but refuses it. You're authenticated but don't have permission. Check IP restrictions or file permissions. |
404 | Not Found | The URL doesn't exist. Check for typos, deleted pages, or broken links. Persistent 404s get dropped from search indexes. |
405 | Method Not Allowed | The HTTP method isn't supported for this URL. Sending POST to a GET-only endpoint, for example. |
408 | Request Timeout | The server timed out waiting for the client to finish sending the request. |
409 | Conflict | The request conflicts with the current state of the resource. Common when two users edit the same record simultaneously. |
410 | Gone | The resource is permanently deleted. Unlike 404, this tells search engines to remove it from the index immediately. |
413 | Content Too Large | The request body exceeds the server's size limit. Increase the upload limit in Nginx or your app config. |
418 | I'm a Teapot | An April Fools' joke from 1998 (RFC 2324) that stuck around. Some APIs use it for rate limiting or easter eggs. |
422 | Unprocessable Entity | The syntax is valid but the content makes no sense. Laravel and Rails return this for validation errors. |
429 | Too Many Requests | Rate limited. You're sending requests too fast. Check the Retry-After header for when to try again. |
451 | Unavailable For Legal Reasons | Blocked due to legal demands (court order, DMCA). The number references Fahrenheit 451. |
5xx Server Error
| Code | Name | What it means |
|---|---|---|
500 | Internal Server Error | Something crashed on the server. Check server logs. The most generic and most common server error. |
501 | Not Implemented | The server doesn't support the functionality required. Rare in practice. |
502 | Bad Gateway | A reverse proxy (Nginx, Cloudflare) couldn't reach the backend. Usually means your app process crashed or isn't running. |
503 | Service Unavailable | Server overloaded or in maintenance. Usually temporary. Check if your app is actually running. |
504 | Gateway Timeout | The reverse proxy didn't get a response from the backend in time. Your app is too slow or stuck. |
507 | Insufficient Storage | Server ran out of disk space. Check disk usage and log rotation. |
508 | Loop Detected | The server found an infinite loop while processing a WebDAV request. Also shows up with misconfigured reverse proxies. |
522 | Connection Timed Out | Cloudflare-specific. Cloudflare couldn't reach the origin server. Check firewall rules and origin server health. |
524 | A Timeout Occurred | Cloudflare-specific. The origin server responded but took too long. Increase timeout or optimize the endpoint. |
How to fix common HTTP errors
Knowing what a status code means is half the job. Fixing it is the other half. Here are the codes that generate the most support tickets, based on what we see in our monitoring alerts.
403 Forbidden. Nine times out of ten it's a Cloudflare WAF rule, an IP block, or wrong file permissions. Check your .htaccess, verify the requesting IP isn't on a blocklist, and make sure directory permissions are 755 (not 777, not 700). If a CDN sits in front, check its firewall rules before touching the origin server.
404 Not Found. Either the page never existed or someone renamed the URL without adding a redirect. Run the status code checker on the old URL to confirm it's a real 404 and not a soft 404 (page returns 200 but shows "not found" content). If the page moved, add a 301. If it's genuinely gone, return 410 so search engines stop trying.
500 Internal Server Error. The server crashed but won't tell you why in the response. Check your application logs first. Common culprits: a syntax error in a config file pushed during deploy, a database connection that dropped, or an unhandled exception in production code that passed just fine in staging. We've debugged 500s that turned out to be a single missing environment variable.
502 Bad Gateway. Nginx or your load balancer can reach the network but not your app process. Is PHP-FPM running? Did Node crash after the last deploy? Check systemctl status for your app service. If it shows "dead" or "failed," there's your answer.
503 Service Unavailable. The server is alive but overwhelmed or in maintenance mode. If it's a traffic spike, scale up or enable a queue. If you just deployed, check whether maintenance mode got toggled on and never toggled back. It happens more than you'd think.
Why does status code monitoring matter for SEO?
Googlebot treats a 200 and a soft 404 very differently. Pages that silently flip from 200 to 302 or 404 lose ranking within days, sometimes before you've even noticed the change. A staging server that returns 500 during a deploy can make Googlebot crawl you less often if it happens to hit that error at the wrong moment. You can't schedule around when Google crawls.
Checking once tells you the current state. Uptime monitoring checks every minute and alerts you when a page flips from 200 to anything else, before Google notices and before users see an error page. If the problem turns out to be a redirect gone wrong, the redirect chain checker traces every hop so you can find where the chain breaks. For SSL-related failures that masquerade as generic errors, SSL certificate monitoring catches expiry before it causes problems.
Spot-checking status codes after you deploy
Your first post-deploy task: check critical pages. Homepage, top landing pages, checkout flow, API health endpoint. A 500 on a page with 10K monthly visits costs more than a 500 on a terms-of-service page nobody reads. The bulk checker handles 20 URLs per batch, which covers most critical-path testing. The CSV export feeds directly into your CI/CD pipeline.
If you want to confirm the site is fully reachable beyond just the response code, the website down checker tests connectivity from an external server. The uptime calculator shows how much downtime your SLA actually allows. And uptime monitoring handles all of this on a schedule, so you're not running manual checks at 3 AM when something inevitably breaks. Alerts go out through Slack, email, SMS, or whatever channel your on-call team actually watches.