Free Redirect Checker and HTTP Status Code Checker

Enter a web address and see every redirect step: the status code, where it goes next, how long it took and the headers, ending in a clear verdict. Or check all four http, https, www and non-www versions of a domain. Free, no account needed.

Web addresses to check

Enter up to 10 addresses, one per line. A bare domain such as example.com is fine. A free account checks up to 50 addresses at a time.

What to check Follow each addressShows every redirect step, status code and header for each address. Check all 4 versions of a domainTests http and https, with and without www, and tells you whether all four end on one address. Enter one domain.

What this check can and cannot see

We send one request per step from our server. A site may answer differently by country, device, language or cookies, so your browser can see a different result.
Browsers that already know a site's HSTS policy go straight to https and never send the plain http request this check can show.
No cookies are kept between steps and no JavaScript is run. A redirect that needs a cookie, or one written in a script, is not followed. A meta refresh inside a noscript element is ignored too.
We follow HTTP redirects (301, 302, 303, 307 and 308), the Refresh header and a meta refresh tag, up to 10 redirects.
We say who we are, SEOSiteCheckerBot, and send plain requests. We do not pretend to be a browser or a search engine, and some websites answer bots differently or block them.
We read only the start of each answer: enough to find a meta refresh and to recognize a bot protection page. A 200 OK does not mean a page is indexed.
To protect other people's websites, we check one website about 20 times a minute. A long list from one site pauses for a moment when that limit is reached, then carries on by itself.

About SEOSiteCheckerBot, and how to allow or block it

HTTP status codes this tool explains

A status code is the three digit answer a server gives before it sends anything else. The first digit tells you the group: 2 worked, 3 redirects, 4 the request had a problem, 5 the server failed. These are the ones you meet most when you check redirects.

200 OK: The server found the page and sent it. This is the normal answer for a working page. For search: It is the status you want at the end of a redirect chain. A 200 alone does not mean the page will be indexed.
204 No Content: The request worked, but the server sent no content. For search: There is nothing on the page for a search engine to read.
300 Multiple Choices: The server offers several versions of the page. This tool does not follow a 300. For search: Rare on websites. If one address should lead to one page, use a 301 redirect instead.
301 Moved Permanently: The page has a new permanent address, given in the Location header. Browsers can remember this answer, so a mistake can linger. For search: The usual choice for a page that moved for good. Google's documentation calls a 301 a strong signal that the new address should be the canonical one (the preferred address).
302 Found: The page is at a different address for now, and the original address should still be used later. For search: Meant for short term moves. Google's documentation says it does not use a temporary redirect as a signal that the new address should be canonical (the preferred address), so use a 301 or 308 for a permanent move.
303 See Other: The server sends the browser to a different page to fetch with a plain GET request, often after a form was submitted. For search: Counted as temporary. It is rarely the right choice for moving a page; use a 301 or 308 for a permanent move.
304 Not Modified: The page has not changed since a copy the browser already holds. It only appears for a request that asks "only if changed". For search: This tool does not send a conditional request, so a 304 here is unusual. The server may be set up in an unexpected way.
307 Temporary Redirect: The page is at a different address for now. Unlike a 302, the browser must repeat the request with the same method, so a form post stays a post. For search: Temporary, like a 302. Use a 308 or 301 for a permanent move.
308 Permanent Redirect: The page has a new permanent address. Like a 301, but the browser must repeat the request with the same method. For search: Google's documentation treats a 308 like a 301, as a strong signal that the new address should be the canonical one (the preferred address).
400 Bad Request: The server could not understand the request. For search: Google's documentation treats 4xx errors other than 429 alike: the page counts as missing, and it is dropped from search if it was indexed. For a normal address, check it for odd characters.
401 Unauthorized: The page needs a login, and none was given. For search: A crawler cannot log in, so a page behind a login cannot be read by search engines. That is a mistake for a public page and expected for a members area.
403 Forbidden: The server understood the request but refuses to allow it. For search: A 403 on a public page can keep it out of search. Some sites also answer 403 to automated tools, so a browser may see a different answer than this check did.
404 Not Found: The server has no page at this address. For search: Google's documentation says a 404 counts as a page that does not exist, and it is removed from the index if it was indexed. If a replacement exists, redirect the old address to it with a 301.
410 Gone: The page was removed on purpose and is not coming back. For search: A clear sign that the page is gone for good. Google's documentation handles a 410 like other 4xx errors, so it is dropped from search like a 404.
429 Too Many Requests: The server says too many requests came in a short time. For search: Google's documentation treats a 429 as a sign the server is overloaded and slows its crawling. This check may itself have been rate limited, so try again later.
451 Unavailable For Legal Reasons: The page is withheld for a legal reason, such as a court order. For search: There is nothing to fix in the page itself.
500 Internal Server Error: Something went wrong on the server while it built the page. For search: A server error. Google's documentation says 5xx errors make its crawlers slow down, and URLs that keep returning them are eventually dropped from the index.
501 Not Implemented: The server does not support what the request needs. For search: Counted as a server error, like a 500.
502 Bad Gateway: A gateway or proxy in front of the site got a bad answer from the server behind it. For search: A server error, like a 500. Look at the server or service behind the gateway.
503 Service Unavailable: The server is overloaded or down for maintenance. It may say when to try again in a Retry-After header. For search: The right status for planned downtime, because it tells crawlers to come back later. If it lasts, URLs can be dropped from the index.
504 Gateway Timeout: A gateway or proxy in front of the site waited too long for the server behind it. For search: A server error, like a 500. The server behind the gateway is slow or not answering.

What Is a Redirect Checker?

Quick answer: A redirect checker follows a web address one step at a time and shows every status code, where each step points and where the chain ends. To check a redirect now, paste a URL into the tool above and read the verdict.

An HTTP (Hypertext Transfer Protocol) redirect is a 3xx reply with a Location header saying where to ask next. The redirect trace lists each step's status code, time and response headers, with a one line verdict on top: OK, Warning or Problem. The final status code sits on every card that got an answer, so this free redirect checker doubles as an HTTP status code checker. It runs on our server, no account needed.

How to Check Redirects With This Tool

Enter the addresses. Fill in "Web addresses to check", one per line, up to 10 at a time or 50 with a free account. A bare domain such as example.com is checked as https, so type http:// first for the plain http step.
Choose what to check. "Follow each address" is the default. "Check all 4 versions of a domain" tests http and https, with and without www.
Run the check. Press "Check redirects" and the page scrolls to the results. "Stop" ends a run early.
Read the cards. The verdict comes first. One address has its steps open; a list gets a closed "Steps (N)" disclosure per card.

Try this: Paste an old link from an email into the tool above and count the steps.

HTTP Status Code Checker: How to Read the Verdict and Steps

Every step shows the status code with its name, where it goes next and the time. Three badges sum up the chain.

OK. No redirect, or up to two permanent ones (301 or 308), ending on a working https page.
Warning. The chain ends on a working page but has a temporary redirect (302, 303 See Other or 307), a meta refresh, a Refresh header, three or more redirects or a plain http ending. A refusal (401, 403 or 429) or a bot protection page counts too.
Problem. The chain broke or ended on an error: 404 Not Found, 410 Gone, a 5xx such as 503 Service Unavailable, a loop, an unknown domain name, a request timeout, a certificate error or more than 10 redirects.

Each step's meaning and "For search" line paraphrase the RFC 9110 redirection status codes and Google's documentation, as read on November 2, 2026. The "HTTP status codes this tool explains" panel lists 21 codes.

OK says only that the chain looks clean to this tool. We lead with the verdict because it is quickest to act on; a badge flattens detail.

A Real Redirect Check: The Four Versions of Our Own Domain

Checked on November 2, 2026 with "Check all 4 versions of a domain", our own seositechecker.pro looked like this.

Start address	Steps	Final address
http://seositechecker.pro/	One 301, then 200 OK	https://seositechecker.pro/
http://www.seositechecker.pro/	One 301, then 200 OK	https://seositechecker.pro/
https://seositechecker.pro/	200 OK, no redirect	https://seositechecker.pro/
https://www.seositechecker.pro/	One 301, then 200 OK	https://seositechecker.pro/

The verdict was OK: "All four versions end on https://seositechecker.pro/. Every version that redirects uses a permanent redirect (301 or 308)." The http www row reaches the final destination in one redirect, not two. In this run each check took under half a second from our server.

For contrast, example.com is a reserved demo domain, so a Problem is expected there: all four versions answer with no redirect, which leaves one site reachable at four addresses. Run the same check on your own domain.

301, 302, 307 and 308 Redirects: Which Status Code to Use

A 301 redirect checker answers one question: did the page move for good, or only for now?

Code	Type	What it tells a browser	What Google's documentation says
301 Moved Permanently	Permanent	New address; may be remembered	A canonical signal
308 Permanent Redirect	Permanent	New address; request method kept	A canonical signal
302 Found	Temporary	Original address stays in use	Not a canonical signal
307 Temporary Redirect	Temporary	Same method, for now	Not a canonical signal

The last column paraphrases Google's documentation on redirects, a Google Search Central page last updated April 14, 2026. A permanent redirect signals that the target should be the canonical URL, the preferred address. A temporary one does not, though its target might still be indexed if other canonicalization signals are present.

For a move you will not undo, use a 301, or a 308 when the request method must stay the same. Google says a server-side redirect is likeliest to be read correctly, so a meta refresh of 30 seconds or less and the Refresh header get a Warning, though we follow both. The full guide to URL redirects covers setup.

Check All 4 Versions: http, https, www and non-www

Choose "Check all 4 versions of a domain" and enter one domain. The tool makes four plain checks and compares where the four versions of a domain end, which settles the www vs non-www question and the http to https redirect test.

OK: all four end on one https address, by permanent redirects only, with no chain of three or more.
Warning: one final address, but a temporary redirect, meta refresh or Refresh header on the way.
Problem: plain http at the end, different final addresses, all four answering directly, or a failure other than a missing www name.
Warning again: a bot protection page or refusal gives "We could not compare the four versions."

A www name that does not exist is only a Warning, since many sites skip www. The versions that do work are then not compared, though each row shows where its version ends.

This mode refuses an IP address, another subdomain, a port or a list; use "Follow each address" instead. Unsure which preferred domain should win? Read how to choose one preferred address.

Redirect Chains, Loops and Errors: What to Fix First

Every hop is another request, and a redirect chain checker has to count them all. In one run on November 2, 2026, two redirects and the final page took about 0.8 seconds from our server. Three or more raise a Warning, which is our own rule, not Google's. Point the first address straight at the final URL.

The tool stops after 10 redirects with "Too many redirects." Google's HTTP status code documentation, last updated February 4, 2026, says its crawlers follow up to 10 hops by default and other Google products may differ.

A redirect loop names the step that sends the request back to an address already requested.

Fix the end first: a tidy chain into a 404 is still a 404. A 401, 403 or 429 is only a Warning, since the server may be refusing our check. For "Website not found", find the DNS record; for "Certificate problem", read how HTTPS and certificates work.

HTTP Header Checker: Read the Headers at Every Step

Each step has a "Headers (N)" disclosure. It opens with "Most useful headers" (Location, Refresh, Cache-Control, Expires, X-Robots-Tag, Link, Strict-Transport-Security, Set-Cookie, Retry-After, Server, Via, Content-Type), then "All headers, in the order received". Repeated headers stay repeated: two Set-Cookie lines show as two.

Cache-Control on a 301 hints at how long a browser may keep the redirect. Strict-Transport-Security, when an https step sends it, explains why a browser may skip the http step later. Retry-After goes with a 429 or 503. X-Robots-Tag is printed as sent, not interpreted.

The "Time split" lists "Name lookup", "Connect", "Secure setup", "First byte" and "Time". "Name lookup" is our own resolver, not your visitors' DNS speed. "First byte" (time to first byte) and "Time" run from the start of the step, so don't add the five up.

Why a Browser Can Show a Different Result

We send one plain GET request per step from our server, with the user agent SEOSiteCheckerBot, instead of posing as a browser. A site that answers by user agent, country, device, language or address can show us something other than what a visitor sees.

No cookies, no JavaScript. A script redirect is not seen, a refresh inside noscript is ignored, and a consent wall that sets a cookie first can look like a loop.
HSTS. A browser that already knows a site's HTTP Strict Transport Security (HSTS) policy goes straight to https, skipping the plain http request this check shows.
Browser memory. Browsers can remember a 301, since RFC 9110 (HTTP Semantics) calls it heuristically cacheable, so a changed rule can look unchanged in a normal tab.
Bot protection. A bot protection page we recognize is reported as such; others can pass for a normal answer.
Out of scope. A 200 OK does not mean a page is indexed, and robots rules and canonical tags are not tested.

Tip: When two results disagree, test the exact address in a private window and read the Server header of the step that differs.

Check a List of Addresses and Export a CSV

To check multiple URLs, paste up to 10 addresses per run, or 50 with a free account; duplicates count once. The "Check the remaining addresses" button resumes after a Stop or a lost connection. One website is checked about 20 times a minute, so a long list from one site pauses, then carries on.

The "Download CSV" button appears when a run ends: a CSV export with one row per step, 13 columns and a UTF-8 byte order mark for Excel. After a site migration, paste old URLs from your redirect map and read the Result column, filled on each address's last row.

Who Sends the Requests to the Site You Check

The site you check sees SEOSiteCheckerBot as the user agent, with no browser or search engine disguise. No result is cached, so every run is live.

Addresses and results are plain text, never links, so you can trace a short link without opening it. Our server does request each address, so a one-time link can be used up. It does not judge where a link leads.

Related Free Tools

Try these after your first check.

Website SEO Score Checker: the SEO audit with a URL Redirects row.
Technical SEO Checklist: 35 points, redirects among them.
all website management tools: the rest of this category.

Frequently Asked Questions

Frequently Asked Questions (FAQs) is a list of common questions and answers provided to quickly address common concerns or inquiries.

What is a redirect checker?

A redirect checker, also called a URL redirect checker, website redirect checker or redirect tester, follows an address one step at a time and reports each status code and where the chain ends. It checks the addresses you enter, not a whole site.

How do I check the HTTP status code and redirect path of a URL?

Type the address into 'Web addresses to check' in the tool above and press 'Check redirects'. The card shows the 'Final status', and 'Steps' lists each hop. A bare domain starts at https, so type http:// first for the plain http step.

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

A 301 is permanent and a 302 is temporary; 308 and 307 are the same pair, with the request method kept. Use 301 or 308 for a move you will not undo. Google's redirects page, updated April 14, 2026, says only a permanent redirect signals the canonical target.

How many redirects are too many?

There is no cutoff, but every redirect is one more request, so aim for one hop. This tool warns at three or more, its own rule, and stops after 10. Google's HTTP status codes page, updated February 4, 2026, says its crawlers follow up to 10 hops by default.

What is a redirect chain, and what is a redirect loop?

A chain is two or more redirects in a row before the final page. A loop sends the request back to an address already requested, so it never ends. A redirect that needs a cookie can look like a loop here.

Do redirects hurt SEO?

One permanent redirect is the normal way to move a page, so it is not a problem, but each extra hop adds a request. Google's redirects page, updated April 14, 2026, says a temporary redirect is not the canonical signal. This tool tests redirects, not rankings.

Why does the redirect checker show a different result than my browser?

We send one plain GET from our server, with no cookies and no JavaScript, and a site can answer by country, device, language or user agent. Browsers can also remember a 301 and apply HSTS. Test in a private window and compare the Server header.

Does the tool follow JavaScript or meta refresh redirects?

It follows HTTP 301, 302, 303, 307 and 308, the Refresh header and a meta refresh of 30 seconds or less, marking the last two Warning. It does not follow JavaScript redirects, because no scripts run, and a refresh inside noscript is ignored.

How do I check the http, https, www and non-www versions of my website?

Choose 'Check all 4 versions of a domain' in the tool above, enter one domain and press 'Check redirects'. A good result is one https address reached by permanent redirects. A missing www name is only a Warning, and the working versions are then not compared.

Can I check more than one URL at a time, and are there limits?

Yes. You can check up to 10 addresses per run, one per line, or 50 with a free account. One website is checked about 20 times a minute, so a long list pauses, then continues, with a CSV download at the end.