HTTP Status Code Checker

Bulk-check HTTP status codes for up to 25 URLs. Identify broken links, redirects, server errors, and get a site health score with actionable recommendations.

Check Status Codes

Paste up to 25 URLs. Each will be checked for its HTTP status code. Results are cached for 10 minutes.
Quick test:
How the Score Is Calculated

How the Score Is Calculated

The site health score starts at 100 and is reduced based on issues found:

  • -10 points per 4xx Client Error
  • -15 points per 5xx Server Error
  • -3 points per 3xx Redirect (minor — redirects are common)
  • -8 points per Connection Error

Scores above 90 are excellent, 70-89 are good with minor issues, 50-69 need attention, and below 50 is critical.

HTTP Status Code Checker Examples: Valid vs. Broken Inputs

Use these examples before testing your own site so you know what a normal result and a problem result should look like.

Valid example

Test https://example.com/ to see a simple successful HTTP response.

Broken example

Test https://httpstat.us/500 or https://httpstat.us/404 to see how server errors and missing pages appear.

Preview: What the Result Should Show

A screenshot should show the submitted URL, returned status code, response category, and plain-language meaning.

How to Interpret the Result

200-level responses are generally accessible. 300-level responses redirect. 400/500-level responses usually need investigation if the URL should be live.

Common Failure Cases

  • 404 page not found
  • 500 server error
  • 403 blocked request

What warnings mean

A warning means the URL responded, but the status is not ideal for a page that should rank. For example, a 3xx redirect may be normal for HTTP-to-HTTPS cleanup, while a 403 or repeated 5xx pattern usually needs investigation.

What this tool cannot know

  • Whether a temporary outage is affecting real users or only happened during this single check.
  • Whether Googlebot receives the same response as this server-side request if a CDN, WAF, or geo rule changes behavior by user agent or location.
  • Whether the URL should exist at all — that requires site architecture, internal-link, sitemap, and business-context review.

Download sample report

Frequently Asked Questions

The tool returns whatever status code the server sends — 200 (OK), 301/302 (redirects), 404 (not found), 500 (server error), and everything in between. Results are color-coded: green for 2xx success, yellow for 3xx redirects, red for 4xx client errors and 5xx server errors.
You can check up to 25 URLs per batch. If you need more, run multiple batches. Bounded request deadlines plus per-visitor and global concurrency limits keep each batch controlled.
Yes, it follows up to 5 redirects automatically and reports the final URL and status code. Use the Redirect Checker tool for detailed hop-by-hop analysis of each redirect in the chain.
2xx = Success (page loaded correctly), 3xx = Redirection (content has moved), 4xx = Client Error (page not found, access denied, bad request), 5xx = Server Error (the server failed to respond properly). Each range has specific implications for SEO and user experience.
HTTP status codes directly impact search engine crawling and indexing. 2xx pages get indexed normally, 3xx redirects pass ranking signals (301/308 pass most link equity), 4xx pages waste crawl budget and may be deindexed, and 5xx errors can temporarily reduce crawling frequency. Regular status code audits help maintain site health.
A 301 redirect signals a permanent move, while a 302 signals a temporary move. Search engines can interpret and consolidate either over time, but the status should match your intent: use 301 for a permanent move and 302 only when the change is genuinely temporary.
Some 404 errors are normal (deleted pages, mistyped URLs), but excessive 404s waste crawl budget and create a poor user experience. Important pages that return 404 should be restored or redirected to relevant alternatives. Use 301 redirects for pages that have moved, and consider custom 404 pages for deleted content.
500 errors indicate a server-side problem — misconfigured .htaccess, PHP errors, database connection failures, memory limit exhaustion, or issues with plugins/themes. These errors prevent both users and search engines from accessing your content. Monitor 5xx rates and work with your hosting provider to resolve them quickly.
Run a status code check at least monthly for small sites and weekly for larger sites. Also check after major changes like site migrations, redesigns, CMS updates, or server configuration changes. Proactive monitoring prevents SEO issues from going unnoticed.