Check the HTTP status code of a URL online free - no login. See its status code, a plain-language meaning, and response time, checked via a third-party proxy - one URL at a time, no batch mode.
If this tool isn’t working as expected, please take a screenshot of the error and report the problem here so we can investigate and improve it.
HTTP status codes tell you whether a URL is working correctly, redirecting somewhere, or returning an error. For SEO, the difference between a 301 (permanent) and 302 (temporary) redirect affects how link equity passes - though see the limitations below for what this specific tool can and can't confirm about that distinction.
For site maintenance, catching 404s and 500s before users do prevents ranking drops.
Enter a URL to see its HTTP status code and how long the check took. This tool fetches the URL through a third-party CORS proxy (api.allorigins.win), which automatically follows any redirects itself - so for a URL that redirects to a working page, you'll typically see the final page's status code (like 200), not the redirect code itself. There's no redirect chain, no final-URL display, and no batch mode.
Paste the single URL you want to check the HTTP status of.
Click check - the URL is fetched via a third-party proxy (api.allorigins.win), which follows any redirects itself.
View the resulting status code, its meaning, and the response time.
A list of common status codes and their meanings is always visible below the checker.
Type or paste a single URL - there's no batch or multi-URL input.
The request goes to api.allorigins.win, a third-party CORS proxy, which fetches the URL on your behalf and follows any redirects itself.
You'll see the resulting status code, its label and description, and the total round-trip time (browser → proxy → target → proxy → browser).
The always-visible "Common Status Codes" list at the bottom covers codes beyond whatever you just checked.
Best For
Input
Checking http://example.com, which 301-redirects to https://example.com (a working page)Result
Status: 200 OK - not 301Because api.allorigins.win follows redirects itself before returning a result, the redirect is invisible to this tool in the typical case - you see the destination's status, not the redirect code.
Input
Any URL, redirecting or notResult
Two fields only: HTTP Status Code and Response Time. "URL Checked" echoes back exactly what you typed (with https:// added if missing) - it is not a resolved or final URL from the response.The tool doesn't read or display any URL data from the proxy's response - only the status code.
Input
Any checkResult
A single millisecond figureThis measures your browser's round trip to api.allorigins.win and back, which includes that service's own time to fetch the target - not a clean, direct measurement of the target server's response time.
Quick spot-check after a deploy or migration, one URL at a time.
Useful for verifying a page was actually taken down or is actually broken.
Use the always-visible reference table even without checking a live URL.
Problem
Solution
The underlying proxy follows redirects automatically - you'll typically see the destination page's status code instead, not the redirect itself.
Problem
Solution
Neither exists - the result is just a status code, a label, and a response time. The "URL Checked" field is your original input, not a resolved URL.
Problem
Solution
There's no multi-URL input - one URL at a time only.
Problem
Solution
It's a GET request to a third-party proxy (api.allorigins.win), which itself fetches your target URL - not a direct HEAD request from your browser or from CoditTools.
Problem
Solution
It includes the proxy's round-trip overhead, not just the target site's response time.
It's fast for "is this one page up and returning what I expect," not for auditing a whole redirect chain.
Since this tool can't show intermediate hops, use a tool built for chain tracing if you need to see every step.
If a redirect resolves successfully, you'll usually see the final page's code, not the redirect code - check your server config or a browser's network tab instead.
It's always visible, independent of whatever URL you check.
The request is proxied through a third-party service (api.allorigins.win) - the target site sees the proxy's request, not a direct one from your browser or from CoditTools.
Only a single status code is shown - there's no per-hop breakdown and no resolved/final URL field.
Because the proxy follows redirects itself, a successfully-redirecting URL typically shows its destination's status code, not 301/302.
One URL at a time only, despite what earlier product copy on this page may have implied.
The tool always makes the same GET-via-proxy request - there's no way to send a HEAD request, choose a different user-agent, or view response headers.
Results are only shown on-screen.
Each check is a fresh request to the third-party proxy, with a generic error message if it fails.
Both report a status code, but only one shows you every hop of a redirect.
| This Tool (Single Code via a Redirect-Following Proxy) | A Redirect-Chain-Aware Checker | |
|---|---|---|
| Shows each redirect hop | No - only the final status | Usually yes |
| Distinguishes 301 vs 302 on a working redirect | Not reliably - the proxy resolves it first | Usually yes |
| Batch checking | Not supported | Often supported |
The most common question is about 301 vs 302 redirects. A 301 (permanent) redirect signals to Google that the original URL has moved permanently - link equity passes to the destination. A 302 (temporary) redirect signals that the move is temporary - Google may continue indexing the original URL. This tool's own check goes through a redirect-following proxy, so it usually can't show you which type of redirect a URL used - only the status of wherever the proxy ends up.
No. It sends a GET request to a third-party CORS proxy (api.allorigins.win), which fetches your URL on its own and returns the result. Your browser never sends a HEAD or GET request directly to the site you're checking.
No. The check is proxied through a third-party service, api.allorigins.win, called directly from your browser. The target site sees a request from that proxy, not from you or from CoditTools.
No. There's a single URL input and a single result - no batch, bulk, or CSV-upload mode exists.
No. Only one status code and a response time are shown. The proxy this tool uses follows redirects automatically before returning a result, so you typically see the destination page's status code rather than the redirect - and there's no field showing the resolved/final URL or the individual hops in between.
HTTP status codes are grouped by their first digit: 2xx means success (200 OK, 201 Created). 3xx means redirect (301 Permanent, 302 Temporary, 304 Not Modified). 4xx means client error (400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found). 5xx means server error (500 Internal Server Error, 503 Service Unavailable). The most important for SEO and debugging are 200, 301, 302, 404, and 500.
A 301 redirect (Moved Permanently) tells search engines that the original URL has moved permanently - Google passes the link equity (PageRank) of the original URL to the destination URL. A 302 redirect (Found / Moved Temporarily) signals a temporary move - Google may continue indexing the original URL and does not pass full link equity to the destination. Use 301 for permanent URL changes; use 302 only when the original URL will return. This is general SEO education - this tool's own check usually can't tell you which type a given URL uses, since the underlying proxy resolves redirects before returning a result.
A 500 Internal Server Error means something went wrong on the server - not a client issue. Common causes: PHP or application code error, database connection failure, memory limit exceeded, corrupted .htaccess file, or a server misconfiguration. Check your hosting control panel for error logs, which will show the specific cause.
A 404 Not Found error means the URL does not exist on the server. If you moved or deleted a page: set up a 301 redirect from the old URL to the replacement URL. If the URL was mistyped in an external link: contact the linking site to correct the URL. In Google Search Console, monitor 404 errors and prioritize fixing those that still receive traffic or have inbound links.
Google's documentation says it follows redirects, but best practice recommends keeping redirect chains to a maximum of 3–5 hops. Each additional hop adds latency and dilutes the link equity passing through the chain. If you have a chain like A→B→C→D, consolidate it to A→D. Google may drop redirect chains with too many hops from its index. This is general SEO education - this tool doesn't show you the individual hops in a chain, only a single resulting status code.
Leave your email so we can prioritize similar tools and updates.
Trending tools will appear as visitors explore the catalog.
Your recently visited tools will show up here.