−50%

50% off your first month on any paid plan · code WELCOME50 · until Nov 30

Start free →

Free tool · HTTP

HTTP Status Checker

Check one URL or bulk-test up to 20 at once. See status codes, response times, and redirects.

Check free · no sign-up

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

CodeNameWhat it means
100ContinueServer received the request headers. The client should send the body. Used for large uploads.
101Switching ProtocolsServer is switching to the protocol the client requested (usually WebSocket).
102ProcessingServer received the request and is working on it, but no response yet. Prevents timeout on slow operations.
103Early HintsServer sends preliminary headers (like preload links) while still preparing the full response. Speeds up page loads.

2xx Success

CodeNameWhat it means
200OKThe request succeeded. This is the normal response for a working page.
201CreatedA new resource was created. Typical response after a successful POST to an API.
202AcceptedRequest received but not yet processed. Used for async operations like queued jobs.
204No ContentRequest succeeded, but there's nothing to send back. Common for DELETE requests.
206Partial ContentServer is sending part of the resource. Used for resumable downloads and video streaming.
207Multi-StatusResponse contains multiple status codes for different sub-requests (WebDAV).

3xx Redirection

CodeNameWhat it means
301Moved PermanentlyThe URL moved permanently. Search engines transfer ranking to the new URL. Use for domain migrations and permanent URL changes.
302FoundTemporary redirect. The original URL keeps its ranking. Use when the redirect is genuinely short-term.
303See OtherRedirects to a different URL using GET. Used after form submissions to prevent duplicate POSTs on refresh.
304Not ModifiedBrowser cache is still valid. The server didn't send new content, saving bandwidth.
307Temporary RedirectLike 302, but guarantees the HTTP method stays the same. POST stays POST.
308Permanent RedirectLike 301, but guarantees the HTTP method stays the same. Important for API endpoints.

4xx Client Error

CodeNameWhat it means
400Bad RequestThe server can't process the request due to malformed syntax. Check your query parameters or request body.
401UnauthorizedAuthentication required. The request lacks valid credentials. Not the same as 403.
403ForbiddenServer understood the request but refuses it. You're authenticated but don't have permission. Check IP restrictions or file permissions.
404Not FoundThe URL doesn't exist. Check for typos, deleted pages, or broken links. Persistent 404s get dropped from search indexes.
405Method Not AllowedThe HTTP method isn't supported for this URL. Sending POST to a GET-only endpoint, for example.
408Request TimeoutThe server timed out waiting for the client to finish sending the request.
409ConflictThe request conflicts with the current state of the resource. Common when two users edit the same record simultaneously.
410GoneThe resource is permanently deleted. Unlike 404, this tells search engines to remove it from the index immediately.
413Content Too LargeThe request body exceeds the server's size limit. Increase the upload limit in Nginx or your app config.
418I'm a TeapotAn April Fools' joke from 1998 (RFC 2324) that stuck around. Some APIs use it for rate limiting or easter eggs.
422Unprocessable EntityThe syntax is valid but the content makes no sense. Laravel and Rails return this for validation errors.
429Too Many RequestsRate limited. You're sending requests too fast. Check the Retry-After header for when to try again.
451Unavailable For Legal ReasonsBlocked due to legal demands (court order, DMCA). The number references Fahrenheit 451.

5xx Server Error

CodeNameWhat it means
500Internal Server ErrorSomething crashed on the server. Check server logs. The most generic and most common server error.
501Not ImplementedThe server doesn't support the functionality required. Rare in practice.
502Bad GatewayA reverse proxy (Nginx, Cloudflare) couldn't reach the backend. Usually means your app process crashed or isn't running.
503Service UnavailableServer overloaded or in maintenance. Usually temporary. Check if your app is actually running.
504Gateway TimeoutThe reverse proxy didn't get a response from the backend in time. Your app is too slow or stuck.
507Insufficient StorageServer ran out of disk space. Check disk usage and log rotation.
508Loop DetectedThe server found an infinite loop while processing a WebDAV request. Also shows up with misconfigured reverse proxies.
522Connection Timed OutCloudflare-specific. Cloudflare couldn't reach the origin server. Check firewall rules and origin server health.
524A Timeout OccurredCloudflare-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.

Frequently asked questions

Enter the URL above. The tool sends a request and shows the status code (200, 301, 404, 500, etc.), response headers, and redirect chain if any.

Switch to Bulk Check mode, paste up to 20 URLs (one per line), and click Check All. The tool runs five requests in parallel and streams results into a table with status codes, response times, and redirect targets. You can export the results as CSV.

200 OK means the server successfully processed the request and returned the page. It's the normal response for a working web page.

301 is a permanent redirect — search engines transfer ranking to the new URL. 302 is temporary — the original URL keeps its ranking. Use 301 when the move is permanent.

Status codes 502 (Bad Gateway), 503 (Service Unavailable), and 504 (Gateway Timeout) all indicate server-side problems. A 503 means the server is temporarily overloaded or in maintenance. If your site returns any 5xx code, it's effectively down for visitors.

Enter the old URL in the checker. If the redirect is working, you'll see a 301 status code and the Location header pointing to the new URL. For multiple redirects, the tool shows the full redirect chain so you can verify each hop lands where expected.

Check your application logs first. The most common causes are a syntax error in a config file, a dropped database connection, or an unhandled exception. If the error started right after a deploy, roll back and check what changed. The 500 response itself won't tell you anything useful.

More free tools

All 20 tools →

Turn a one-off check into a monitor.

feature
Pricing Docs
Log in Start free →