Toolsky

Free Online Tools & Utilities for Every Task.

HTTP Status Code Checker

Check HTTP Status Codes from URLs

Before a page's content loads — before any text, images or design — the server answers with a three-digit number that summarises the whole transaction: 200 for success, 301 for "moved permanently", 404 for "not here", 500 for "something broke". That number decides what browsers show, what search engines index and what visitors experience. An HTTP status code checker fetches a URL and reports its code plainly, so when a link misbehaves or a migration is underway, you are working from the server's actual answer instead of a guess.

The Five Families of Status Codes

Codes are grouped by their first digit, and each family tells a different story. 1xx codes are provisional — the server is still working — and rarely seen outside technical contexts. 2xx means success, with 200 the standard answer for a page that exists and loaded. 3xx codes are redirections: 301 for a permanent move, 302 and 307 for temporary ones, 304 when the visitor's cached copy is still valid. 4xx codes blame the request: 404 for a resource that is not there, 403 for one that exists but refuses you, 410 for content deliberately and permanently removed. 5xx codes blame the server: 500 for a general internal failure, 502 and 503 for gateway trouble and temporary unavailability. The MDN status code reference defines each code precisely. Knowing the families turns a bare number into a diagnosis: a 4xx tells you to fix your links or your content, a 5xx tells you to call your host.

What This Checker Tells You

  • The exact code for any URL: enter an address and learn whether it answers 200, redirects, or fails — no browser guesswork, no developer console required.
  • Redirect behaviour: whether a URL forwards elsewhere, which matters when old addresses, shortened links and http-to-https upgrades are in play.
  • Per-URL precision: every path is checked on its own, because a homepage returning 200 says nothing about the product page, PDF or old blog post you actually care about.
  • A migration safety net: run the old URLs after a redesign and confirm each one lands on a live page with the right code instead of quietly expiring into a 404.
  • Evidence for support tickets: when a host or developer insists a page works, a status code is a fact both sides can see.

Status codes are the headline; the rest of the response tells the supporting story, and the HTTP headers parser reads it. For chains of forwards specifically, the redirect checker follows each hop in turn.

How to Check a URL's Status Code

  1. Copy the complete URL you want to test, exactly as a visitor or search engine would encounter it.
  2. Paste it into the checker and run the request.
  3. Read the returned code and note which family it belongs to.
  4. If the code is a redirect, check the destination URL as well to see the final answer at the end of the chain.
  5. If the code is an error, decide whose problem it is: 4xx points to the address or permissions, 5xx to the server.
  6. Record the result if you are working through a list — migrations and audits go better with the before-and-after written down.

A Migration Scenario, Worked Through

A photography studio redesigns its site and moves its portfolio from /gallery.html to /portfolio. The owner checks three addresses the morning after launch. The homepage returns 200 — healthy. The old gallery address returns 301 and lands on the new portfolio page — the redirect was configured correctly, so years of shared links and search results keep their value. Then she checks an old blog post she had decided to retire, expecting a clean 404, and instead gets 200: the redesign accidentally kept a duplicate of it live, thin and outdated, where search engines can still find it. Three checks, three different stories, and one real problem caught on day one instead of month six. That is the whole case for checking codes deliberately — the failures that matter are rarely on the pages you are looking at.

Tips, Limits and Misleading Answers

Beware the soft 404. Some sites display a "page not found" message while returning a 200 code, because a template catches the error. Search engines treat that as a live page that happens to say nothing useful, which is worse than an honest 404 — the checker reveals the lie instantly. One check is a snapshot. A 503 during a five-minute maintenance window is not a crisis; a 503 every morning is. Repeat surprising results at another time before acting on them, and for continuous watching use the website status checker alongside one-off checks. Redirects deserve counting. A single 301 is healthy; a chain of four or five slows visitors and sometimes breaks entirely on old devices, so follow important URLs to their final destination. Codes do not explain themselves. A 500 tells you the server failed, not why — the cause lives in server logs, which is the next stop after the checker identifies which URLs are affected. And a 403 is sometimes intentional: protected, geographic or hotlink-blocked content refuses by design, which is a policy, not a fault.

Frequently Asked Questions About Status Codes

What does a 200 status code actually confirm?

That the server accepted the request and returned the resource successfully. It confirms availability, not quality — a page can return 200 and still contain wrong information, a "not found" message, or a design error.

What is the difference between a 301 and a 302 redirect?

A 301 declares the move permanent, so search engines transfer the old address's ranking signals to the new one and browsers cache the instruction. A 302 (and 307) declares it temporary: the original address remains the canonical one. Using 302 for a permanent move is a classic migration mistake.

Is a 404 always bad?

No. A 404 is the correct, honest answer for an address that never existed or content removed without a replacement. It becomes a problem when URLs that should work — linked pages, bookmarked resources, addresses in your sitemap — return it.

What should I do about a 500 error?

Treat it as a server-side fault: note which URLs produce it and when, then check server error logs or contact your host with that evidence. It is not something a visitor or a link change can fix.

What is a soft 404?

A page that tells the visitor "not found" while returning a 200 status code. Search engines dislike them because they pollute the index with empty pages, and the fix is to return a genuine 404 (or 410) for missing content.

My page works in my browser but the checker reports a redirect. Why?

Your browser silently follows redirects and may have cached the destination, so the hop is invisible to you. The checker reports the first answer the server gives, which is exactly what a search engine crawler sees.

What does 410 mean, and when is it better than 404?

410 Gone states the content was deliberately removed and will not return. For permanently retired pages with no replacement, it tells crawlers to drop the address sooner than a 404 does.

The Three Digits That Decide Everything

Every visit, crawl and click on your site is preceded by this one small number. Checking it deliberately — after launches, migrations and redesigns, and whenever a link smells wrong — catches the quiet failures that cost traffic, and it takes less time than reading this page did.